STOP 0x0000000A at every boot

[ClickRight]

(solved) STOP 0x0000000A at every boot

I have a Toshiba Satellite M30 in. It came in because it needed a new hard drive and memory upgrade. I replace the hard drive and upgraded the memory, and everything was working great. I had rebooted the computer several times and everything was ready to go. This computer was done, and ready to deliver to the customer; I even phoned to tell them it was ready.

I had it on and walked away from it and came back to a nice big blue screen: STOP 0x00000000A. Rebooted in safe mode, no problem. For whatever reason, the computer was set up to do a kernel memory dump, I checked it with debugging tools for windows, but all i got were strings of ".Image path too long, possible corrupt data."

I set the computer to do small memory dumps, but it's not saving them. I ran memtest thinking the new memory could be the culprit. Did a complete pass and no errors, but I removed the module just to be safe. I still have the same problem.

Does anybody have ANY suggestions? I'm just pulling my hair out on this one!

EDIT: I should mention that the very last thing I did was run MyDefrag on the hard drive, that's it.
EDIT2: I'm trying to get a kernel dump, but it's not saving that either.

 

[NYJimbo]

You are saying you downgraded the ram to the old modules and its still doing an 0A ?. Is that correct.

What make/model/size is the new hard drive. Do you know the exact drive model number ?.

 

[ClickRight]

You are saying you downgraded the ram to the old modules and its still doing an 0A ?. Is that correct.

What make/model/size is the new hard drive. Do you know the exact drive model number ?.

Yes, using original module only and getting 0A.

The new hard drive is: Samsung Spinpoint M5 HM160HC 2.5in 160GB IDE 5400RPM. I'm testing it now.

 

[JRDtechnet]

Try throwing in UBCD and run Registry Restore Wizard to a point when you know it was booting correctly.

 

[ClickRight]

Try throwing in UBCD and run Registry Restore Wizard to a point when you know it was booting correctly.

Would love to, but I just wiped out all the restore points once I was done as I also had to remove some spyware from the machine.

 

[NYJimbo]

This is an older machine, just not sure if it can handle the new drive geometry. If its still running the original bios revision you could try to flash it. I know that BIOS has been updated quite a few times.

Do you have the old drive, if you put it back does the 0A go away?.

Just cant be sure of machines ability to handle the 160gb due to bios or if you need newer drivers for the controller. Could also be the drive is now hosed due to the defrag (bios/controller/new ram issues).

 

[JRDtechnet]

Would love to, but I just wiped out all the restore points once I was done as I also had to remove some spyware from the machine.

Perhaps a new snapshot was created after you wiped it...I would check. Also did you use Combofix...that usually backs up the registry automatically using ERUNT. Worse case you can load the repair registry x:\windows\repair that's the registry created right after windows is installed....not really much use but you can load it to diagnosis whether your error is being caused by a registry error or something else.

 

[14049752]

Would love to, but I just wiped out all the restore points once I was done as I also had to remove some spyware from the machine.

Any chance that you missed a rootkit? That could do it.

Could also be the drive is now hosed due to the defrag (bios/controller/new ram issues).

Maybe, except that it still boots safe mode, right? Maybe a controller driver issue, but I'd expect safe mode to be fubar, too.

 

[ClickRight]

SOLVED: I was fooling around and tried safe mode with networking, which also BSODed. I figured I might as well update the wireless drivers (Intel 2200BG) and see if that helps. I updated the drives, rebooted, and no more BSOD.

I will never know why it decided to BSOD. I'll leave it running overnight and let you know what happens.

 

[14049752]

Cool!
Yeah, those Intel Wireless drivers really gave me headaches for a while.... Now we make sure to update them as a matter of course. Too many systems running fine in the shop, customer gets it home and it crashes...

 

[JRDtechnet]

SOLVED: I was fooling around and tried safe mode with networking, which also BSODed. I figured I might as well update the wireless drivers (Intel 2200BG) and see if that helps. I updated the drives, rebooted, and no more BSOD.

I will never know why it decided to BSOD. I'll leave it running overnight and let you know what happens.

Ah I was going to suggest you check if any new drivers were installed...I just re-read your original post...I missed the part where you were getting into safe mode. Glad you found the issue!

 

[NYJimbo]

SOLVED: I was fooling around and tried safe mode with networking, which also BSODed. I figured I might as well update the wireless drivers (Intel 2200BG) and see if that helps. I updated the drives, rebooted, and no more BSOD.

I will never know why it decided to BSOD. I'll leave it running overnight and let you know what happens.

Wow, I mean it was working after you did the upgrade and all the boots but then the WIRELESS drivers started causing trouble?. Weird.

 

[NYJimbo]

I'm still perplexed as to why you needed to reinstall wireless drivers.

This was a cloned drive, right ?. So everything should have been copied precisely, there shouldnt be a reason why only the wireless drivers would fail.

Since the machine didnt start to mess up until after your defrag I am still thinking that either the new ram or the new drive introduced some kind of instability and THAT corrupted the drivers (maybe other stuff too?) during the defrag or something else you did around that time.

You might want to run a defrag again or some other disk checks or scans to see if another issues pops up before releasing the machine back to the client.

 

[14049752]

This was a cloned drive, right ?. So everything should have been copied precisely, there shouldnt be a reason why only the wireless drivers would fail.

If it was updated to SP3, too. He didn't say, but that's a common thing I've noticed. At least three or four systems come to mind in the past couple of months that had issues with the intel wireless. Updated the driver and the bsod's went away.

 

[ClickRight]

As a matter of fact, I updated it to SP3 on the 22nd, when it came in (It previously had SP2.) However, I'm still curious myself as to why it started BSODing suddenly, only after the defrag. I have the machine till tomorrow so I'll try and figure it out.

 

[ClickRight]

Totally figured it out. This morning, I remembered I set up a new new wireless N router yesterday afternoon (shortly before the problem started.) I previously had a G router set up. I guess the wireless card drivers didn't like the new router.

 

[riggs578]

Its not crazy to have the wireless drivers do that. It happened to me twice. both times i went nuts trying everything and finally figured it out.

I think i may have fixed it with windows updates drivers section and it was a dell 9100.

 

[studiot]

I find it worth to automatically remove the wifi card, memory cards etc from non starting laptops.

Suprising how often this helps.

 

[NYJimbo]

Totally figured it out. This morning, I remembered I set up a new new wireless N router yesterday afternoon (shortly before the problem started.) I previously had a G router set up. I guess the wireless card drivers didn't like the new router.

Maybe, but shouldnt the drivers/WIFI in the computer be oblivious to the N router?. "N" is a new protocol and I cant imagine how a negotiation of a new protocol to an old card would cause a blue screen. But if that fixed it................

 

[ClickRight]

Maybe, but shouldnt the drivers/WIFI in the computer be oblivious to the N router?. "N" is a new protocol and I cant imagine how a negotiation of a new protocol to an old card would cause a blue screen. But if that fixed it................

Yeah, that's what I thought as well. Yesterday I rolled back the drivers and did two tests:

• New router on, boot computer: 0x0000000A
• New router off, boot computer: everything was fine.