Storage driver giving me the blue screen of death?

[Grubish360]

My computer has been freezing lately, and giving me a blue sreen of death. When it doesn't and I can actually use it, I have windows scan for problems. When Windows finds the problem it says that it is a storage driver problem. I don't know what to do from here.

 

[richc46]

Try going to device manager, look for any yellow warnings, that drivers are not working properly. If that turns out OK, make sure that you have updated drivers especially for audio and graphics.

 

[Grubish360]

Try going to device manager, look for any yellow warnings, that drivers are not working properly. If that turns out OK, make sure that you have updated drivers especially for audio and graphics.

If there is a yellow triangle with an "!" mark in it, is that the problem driver?

 

[richc46]

Very likely. Good luck

 

[Grubish360]

Ok, because it was a driver for a removable Lexar 2GB SD card. I clicked find update for driver, but it said it was up to date.

 

[richc46]

If there is the yellow triangle, it has to be changed. It may be up to date but corrupt. Make a system restore point in case of problems and try this:

Fix Corrupt Drivers - PCWorld

 

[Jonathan_King]

Please upload your dmps for analysis, and we'll take a look.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[Grubish360]

Thanks for all the help.

 

[Grubish360]

Please upload your dmps for analysis, and we'll take a look.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

I placed all of them in one zip.

 

[richc46]

While wating for the analyis, try to fix the driver. It must be replaced, anyway, if it has the yellow warning.

 

[Jonathan_King]

Thank you very much, I'll take a look for you. Give me a few minutes, this many dmps will take a while.

 

[Jonathan_King]

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.

Usual causes: System service, Device driver, graphics driver, ?memory

That's for your bugcheck 3B.

Please enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 20:18:05.610 2010 (GMT-4)
System Uptime: 0 days 4:47:31.608
BugCheck 3B, {c000001d, fffff88000000000, fffff8800236d160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 20:38:00.062 2010 (GMT-4)
System Uptime: 0 days 0:04:03.059
BugCheck 3B, {c000001d, fffff88000000000, fffff88008153020, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 20:33:30.028 2010 (GMT-4)
System Uptime: 0 days 0:01:39.652
BugCheck 3B, {c000001d, fffff88000000000, fffff880042d7160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 31 20:31:14.327 2010 (GMT-4)
System Uptime: 0 days 0:04:08.325
BugCheck 3B, {c000001d, fffff88000000000, fffff88007225160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 18:24:03.370 2010 (GMT-4)
System Uptime: 2 days 0:31:47.367
BugCheck 3B, {c000001d, fffff88000000000, fffff88002825160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 18:29:05.112 2010 (GMT-4)
System Uptime: 0 days 0:04:31.110
BugCheck 3B, {c000001d, fffff88000000000, fffff88008728160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 23:22:29.662 2010 (GMT-4)
System Uptime: 2 days 9:16:56.660
BugCheck 3B, {c000001d, fffff88000000000, fffff88008867160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Apr 30 08:19:45.774 2010 (GMT-4)
System Uptime: 1 days 13:06:52.771
BugCheck 3B, {c000001d, fffff88000000000, fffff880096b8160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Apr 25 22:12:13.619 2010 (GMT-4)
System Uptime: 0 days 0:03:19.616
BugCheck 3B, {c000001d, fffff88000000000, fffff8800639a160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Apr 25 22:08:18.513 2010 (GMT-4)
System Uptime: 5 days 1:22:12.370
BugCheck 3B, {c000001d, fffff88000000000, fffff88002475160, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoCancelIrp+64 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
[/FONT]

These old drivers or their respective programs should be updated:

000.fcl      Fri Sep 26 09:11:22 2008- Powerlink DVD
adfs.SYS     Thu Jun 26 16:52:37 2008- Adobe Drive File System Driver
PxHlpa64.sys Wed Oct 17 14:25:02 2007- DVD drivers

 

[Grubish360]

I checked, and don't have any of those programs listed at the end of your post. Also I noticed that when ever the freezing, or BSoD occurs, is when there is a "popping", or "clicking" noise. Any ideas?

EDIT: The noise only happens once, I can still move the mouse arrow, but everything else is frozen.

 

[Jonathan_King]

Please update anything related to Adobe on your system.

As for the other drivers, go to C:\Windows\System32 and rename them to 000.fcl.old and PxHlpa64.sys.old, respectively.

 

[Grubish360]

I searched in system32. i could only find PxHlpa64.sys, and changed that. I couldn't find 000.fcl. About adobe, whenever it prompts me for an update it can't install.

 

[Jonathan_King]

Try removing Adobe with Revo Uninstaller, and then installing the latest version.

 

[Grubish360]

So I installed the latest version of Adobe Reader, it prompted me for an update, so I clicked install. i got about half way, and heard the click or pop noise, and my laptop froze.

I'm running a CHKDSK now.

 

[squall leonhart]

PxHlpa64 is installed by Roxio, Sony, and Sonic products. Its a known cause of bsods.

 

[Grubish360]

I think I fixed the problem, I used DSKCHK, and that took about 2 hours. It now works like a charm. Thanks for all the help!