« previous next »
Pages:  [1]     Go Down

Author Topic: Help: BSOD on start up  (Read 2117 times)

0 Members and 1 Guest are viewing this topic.

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Help: BSOD on start up
« on: Thu, 25 July 2013, 01:52:30 »
Kinda embarassing that i am having problems with a computer that ive had for around 4 years so I'll try to keep this kinda short. Don't want to confuse people with my newbieness and what not. I was getting a BSOD on start up then a robot 9n my Windows 7. I read on pc mag forum and it said something about RAM issues. I spammed F8 and selected the option that says "disable reboot on system error". My computer seemingly boots up fine now. It also said to test out the ram one at a time I am currently doing that. Did I solve my issue or is there something else that I should do?
If that is the only problem, what can I do to prevent it next time?

I will update with more information and possibly questions in a little.

Thanks. :)
Logged
SmallFry! <3

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: Help: BSOD on start up
« Reply #1 on: Thu, 25 July 2013, 01:55:57 »
If you do suspect memory problems, try this: http://www.memtest.org/

It performs a really intensive test of all memory locations over and over again - should reveal if that is your problem.
Logged
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Re: Help: BSOD on start up
« Reply #2 on: Thu, 25 July 2013, 02:10:31 »
Do I need a CD or could I use Deomon tools or something?

If I burn it onto a CD all I gotta do is toss it in and reboot my computer and itll auto run?
Logged
SmallFry! <3

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: Help: BSOD on start up
« Reply #3 on: Thu, 25 July 2013, 02:19:45 »
That's how I last used it, or you can writ it to floppy (if you still have one heh).  I imagine you could even boot it from USB stick.
Logged
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Re: Help: BSOD on start up
« Reply #4 on: Thu, 25 July 2013, 03:03:36 »
K starting test now. Should I do on RAM stick at a time?
I did all four :D

From what I read it should only take about an hour.
Logged
SmallFry! <3

Offline godly_music

  • Posts: 255
Re: Help: BSOD on start up
« Reply #5 on: Thu, 25 July 2013, 04:08:08 »
With BSODs it's really crucial that you look at the important bits. The error message at the top (like IRQL_NOT_LESS_OR_EQUAL). And the filename / code somewhere near the bottom (like disp.sys). You can disregard the remainder of the text.

BSODs can be caused by any number of things, basically everything hardware and software related that's serious enough to **** up proper operation of the OS (but can just as often be easily fixed, drivers especially). Without the error message / filename / code, it can't be pin-pointed, and unless you KNOW it's your memory, that's all just guesswork. Not that it hurts to check it.
Logged

Offline rowdy

  • HHKB Hapster
  • * Erudite Elder
  • Posts: 21175
  • Location: melbourne.vic.au
  • Missed another sale.
Re: Help: BSOD on start up
« Reply #6 on: Thu, 25 July 2013, 05:40:49 »
Quote from: TheQsanity on Thu, 25 July 2013, 03:03:36
K starting test now. Should I do on RAM stick at a time?
I did all four :D

From what I read it should only take about an hour.

The one time I used it, I just left it running overnight, came in (to work) the next morning and no errors.
Logged
"Because keyboards are accessories to PC makers, they focus on minimizing the manufacturing costs. But that’s incorrect. It’s in HHKB’s slogan, but when America’s cowboys were in the middle of a trip and their horse died, they would leave the horse there. But even if they were in the middle of a desert, they would take their saddle with them. The horse was a consumable good, but the saddle was an interface that their bodies had gotten used to. In the same vein, PCs are consumable goods, while keyboards are important interfaces." - Eiiti Wada

NEC APC-H4100E | Ducky DK9008 Shine MX blue LED red | Ducky DK9008 Shine MX blue LED green | Link 900243-08 | CM QFR MX black | KeyCool 87 white MX reds | HHKB 2 Pro | Model M 02-Mar-1993 | Model M 29-Nov-1995 | CM Trigger (broken) | CM QFS MX green | Ducky DK9087 Shine 3 TKL Yellow Edition MX black | Lexmark SSK 21-Apr-1994 | IBM SSK 13-Oct-1987 | CODE TKL MX clear | Model M 122 01-Jun-1988

Ị̸͚̯̲́ͤ̃͑̇̑ͯ̊̂͟ͅs̞͚̩͉̝̪̲͗͊ͪ̽̚̚ ̭̦͖͕̑́͌ͬͩ͟t̷̻͔̙̑͟h̹̠̼͋ͤ͋i̤̜̣̦̱̫͈͔̞ͭ͑ͥ̌̔s̬͔͎̍̈ͥͫ̐̾ͣ̔̇͘ͅ ̩̘̼͆̐̕e̞̰͓̲̺̎͐̏ͬ̓̅̾͠͝ͅv̶̰͕̱̞̥̍ͣ̄̕e͕͙͖̬̜͓͎̤̊ͭ͐͝ṇ̰͎̱̤̟̭ͫ͌̌͢͠ͅ ̳̥̦ͮ̐ͤ̎̊ͣ͡͡n̤̜̙̺̪̒͜e̶̻̦̿ͮ̂̀c̝̘̝͖̠̖͐ͨͪ̈̐͌ͩ̀e̷̥͇̋ͦs̢̡̤ͤͤͯ͜s͈̠̉̑͘a̱͕̗͖̳̥̺ͬͦͧ͆̌̑͡r̶̟̖̈͘ỷ̮̦̩͙͔ͫ̾ͬ̔ͬͮ̌?̵̘͇͔͙ͥͪ͞ͅ

Offline Xenderwind

  • Posts: 585
  • Location: chesapeake, virginia
Re: Help: BSOD on start up
« Reply #7 on: Thu, 25 July 2013, 10:08:24 »
There's certain tests that detect memory errors faster than others (as in in runs like 20 different tests) and you can pick which ones to run.  Im sure if you google it you can find which those are, I believe one was like 5 or 7.  I always ran it off a usb stick/flash drive.
Logged
GON NS 87 62g clears, QFR 62g clears, Pure 65g blues, HHKB Pro II

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Re: Help: BSOD on start up
« Reply #8 on: Thu, 25 July 2013, 10:17:04 »
No errors... The search continues...

I'll remember to check out the error message nxt time it blue screens. It seems to stop for the time being.

Do you guys think de fragging the disc would help any? Maybe a tuneup utility software?
Logged
SmallFry! <3

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Re: Help: BSOD on start up
« Reply #9 on: Thu, 25 July 2013, 10:57:38 »
Quote from: godly_music on Thu, 25 July 2013, 04:08:08
With BSODs it's really crucial that you look at the important bits. The error message at the top (like IRQL_NOT_LESS_OR_EQUAL). And the filename / code somewhere near the bottom (like disp.sys). You can disregard the remainder of the text.

BSODs can be caused by any number of things, basically everything hardware and software related that's serious enough to **** up proper operation of the OS (but can just as often be easily fixed, drivers especially). Without the error message / filename / code, it can't be pin-pointed, and unless you KNOW it's your memory, that's all just guesswork. Not that it hurts to check it.

"Ndis.sys"

Whatever that means.

I can't catch the location. It's too long. ><


Further read and it seems to be my wireless network card drivers... that sounds correct to me. All of a sudden it stopped working but not right before being really choppy. I tried reinstalling the drivers from the CD but couldn't connect to a network after a restart. Once I got it working again I downloaded newer drivers from the D-link website. It was the correct driver for my model...

Anyone have any suggestions? I assume this is a software only problem what about you guys?
« Last Edit: Thu, 25 July 2013, 11:05:47 by TheQsanity »
Logged
SmallFry! <3

Offline godly_music

  • Posts: 255
Re: Help: BSOD on start up
« Reply #10 on: Thu, 25 July 2013, 11:04:38 »
Ndis.sys means that you're looking at a driver issue, most likely your ethernet driver is not up-to-date. That happens a lot when you use Microsoft Update (or outdated install CD) drivers instead of 'proper' ones from a manufacturer's website.

Your hardware is fine. And don't worry about defragging and ****-ware like tune-up tools. That's like throwing some goodwill and sparkles at a problem with a very specific solution process. ;)
« Last Edit: Thu, 25 July 2013, 11:10:44 by godly_music »
Logged

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Re: Help: BSOD on start up
« Reply #11 on: Thu, 25 July 2013, 11:07:41 »
I have a cracked version of windows and haven't been getting updates for a few years. Could that be the cause of a lot of my issues?
Logged
SmallFry! <3

Offline godly_music

  • Posts: 255
Re: Help: BSOD on start up
« Reply #12 on: Thu, 25 July 2013, 11:13:26 »
If the crack you used is decent, Windows Update should not raise any flags and update your OS without a fuss. But that's not how you update drivers. Windows Update is notorious for delivering bad or outdated drivers.

Go to Control Panel > System > Device Manager and write down the name of your ethernet hardware listed under Network Adapters. Then google for the manufacturer's website and grab the latest driver from there.
Logged

Offline TheQsanity

  • Thread Starter
  • Posts: 1165
  • SmallFry Lovin'
Re: Help: BSOD on start up
« Reply #13 on: Thu, 25 July 2013, 11:29:06 »
Hmm, is it under Network adapters?
Ive got three things three things there which are:
D-Link DWA 556 Xtreme N PCIe Desktop Adapter
Intel(R) 82578DC Gigabit Network Connection
Microsoft Virtual WiFi Miniport Adapter #3

My guess would be something with the microsoft virtual WiFi...

And nevermind about the Network card. It doesn't seem like that is the case. My internet is working but I am not sure why I have a red "X" in the notifications bar
Logged
SmallFry! <3

Offline godly_music

  • Posts: 255
Re: Help: BSOD on start up
« Reply #14 on: Thu, 25 July 2013, 11:58:37 »
The internet can work just fine even if the driver is dodgy. And I would guess either the D-Link or the Intel to be the culprit here.
Logged

Offline dorkvader

  • Posts: 6289
  • Location: Boston area
  • all about the "hack" in "geekhack"
Re: Help: BSOD on start up
« Reply #15 on: Thu, 25 July 2013, 12:48:58 »
what's the stop code? can you provide a picture? if it creates a minidump file, you can view these with an applicaiton (like nirsoft bluescreenviewer)

I have do diagnose BSOD's at work, and they can be caused by all sorts of things. Specifically I think its a driver failure (but that "Driver" can by ntfs.sys (hdd error or data corruption likely) to ntkrnl (windows nt kernel panic) to even a USB device timing out) and it should generate a "Stop code" "such as STOP:0000000a or similar. you can look up online what the stop code corresponds to, as well as the parameters.
Logged
Pages:  [1]     Go Up
« previous next »