BSOD followed by near paralysis of the system.

mlpvolt · 03 Oct 2013

My main home office desktop seems to have had a "stroke" - While doing nothing special it BSOD'd and then BSOD'd again on reboot. I'd love to provide more diagnostic info but, while it now is booted and seems stable, the system is nearly paralysed. I have a desktop but any action makes it hang. I want to figure out if it is hardware or software and move my OS to new hardware if that is necessary. My files have backups but some of the software would be a pain to replace. I did uninstall a couple (known) programs before the BSOD.

The BSOD (which i was able to take a picture of) was of type

DRIVER_IRQL_NOT_LESS_OR_EQUAL

technical details:

** STOP: 0x00........(long strings of mostly zeros)

** storport.sys - Address.......

I think it was the same info both times but cant be sure.

Intial steps taken.

tried to reboot the system froze up early and often in the boot cycle. POST is very slow.

powered down and moved the SSD (operating system) to a different PC - doesn't seem to be an issue with the disk itself, the disk was accessible without issue and the folder tree looks normal.

Booted with a win 7 pro disk. paaaaiinfully slow but eventually i let it chug through a startup repair and all it seems to do was try a restore point. I let it do the restore point and the system eventually (15 minutes) boots to the login screen. to get an idea of how slow i mean, it takes over a minute to get from the select user screen to the next screen where you enter your windows password.

It seems stable, at least it hasn't crashed but getting anything done will take a long time at this rate. I can see resource monitor now and CPU keeps spiking to max (but not for long), memory uses is stable at about 2gb.

Any suggestions? I'll check device manager next i suppose but it might be 20 min before i get any answers.

Arc · 03 Oct 2013

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

mlpvolt · 03 Oct 2013

overnight it seemed to re-index the file system, and i was able to check eventviewer. a string of errors pointed to a failing data drive. accessing that drive hung it again. will post the diagnostic tool results if i can get them.

mlpvolt · 03 Oct 2013

disconnecting the data drive indicated as failing (G: ) allowed windows to boot more or less normally, still investigating to see if that was the root of the problem. SF diagnostic files attached.

Arc · 03 Oct 2013

The BSOD is caused on the storage driver.

Code:

BugCheck D1, {a, 2, 0, fffff880010b44c5}

Probably caused by : storport.sys ( storport! ?? ::FNODOBFM::`string'+b85 )

Followup: MachineOwner
---------

Your storage driver is NVIDIA nForce Serial ATA Controller. Which is very old.

Code:

fffff880`010f2000 fffff880`01131000   nvstor64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvstor64.sys
    Image name: nvstor64.sys
    Timestamp:        Wed Aug 05 06:01:07 2009 (4A78D2CB)
    CheckSum:         00048878
    ImageSize:        0003F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Even no feasible update available in ASUSTeK M2N68-AM Plus.

If you have any alternative way to update nforce chipset to your motherboard, go for it. That is the problem with nforce that the drivers are not available at all.