Solved Random BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL" ntoskrnl.exe

[ImpetuousRacer]

I keep getting a random BSOD.
I also have certain programs that will freeze with "Not Responding" and will not close and cant be closed with End Task. This effects ShutDown as it will not shutdown.

Below is an excerpt from Using WhoCrashed:
On Thu 3/28/2013 3:22:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032813-22343-01.dmp
uptime: 00:16:50
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF8800125D4C5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


This doesn't really help me much
I have uploaded my dump files from C:\Windows\MiniDump to here: https://www.dropbox.com/s/zlj1vkjjc2ucwxe/Minidump.zip for analysis.

Any help to point me in the right direction would be much appreciated. Thanks!

 

[Dsprague]

All of your dump fiels are Identical and all point to the same thing:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
[COLOR=Red]Probably caused by : sptd.sys[/COLOR] ( sptd+47044 )

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

Driver Reference Table - sptd.sys

Remove Daemon tools/ alcohol 120% and then download and run this tool:

DuplexSecure - Downloads

If the uninstall button is grayed out your done and can close the window, if not click the uninstall button and let the tool do its job. DO NOT click the install button it will instal la driver known to cause BSODs.

 

[ImpetuousRacer]

All of your dump fiels are Identical and all point to the same thing:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
[COLOR=Red]Probably caused by : sptd.sys[/COLOR] ( sptd+47044 )

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

Driver Reference Table - sptd.sys

Remove Daemon tools/ alcohol 120% and then download and run this tool:

DuplexSecure - Downloads

If the uninstall button is grayed out your done and can close the window, if not click the uninstall button and let the tool do its job. DO NOT click the install button it will instal la driver known to cause BSODs.

Thanks! Alcohol and Daemon did not show up in the Add/Remove, and I didn't see them in the Program Files folder either. I was able to use the link you provided to DuplexSecure to remove the driver.

After removing the driver, and rebooting, checking that it was unistalled, I got another blue screen.
Ill get the latest dump file shortly.

 

[Dsprague]

Glad to be of assistance.

 

[ImpetuousRacer]

Link for latest BSOD after SPTD.sys removed:
https://www.dropbox.com/s/c9i5ior5lscaziz/032813-23828-01.zip

 

[Dsprague]

Looking at some of your system information it come to my attention that you are overclocking:

[Processor Information (Type 4) - Length 35 - Handle 0004h]
  Socket Designation            CPUSocket
  Processor Type                Central Processor
  Processor Family              edh - Specification Reserved
  Processor Manufacturer        AMD              
  Processor ID                  620f1000fffb8b17
  Processor Version             AMD Athlon(tm) II X2 245 Processor                  
  Processor Voltage             8fh - 1.5V
  External Clock                200MHz
[B][COLOR=Red]  Max Speed                     2900MHz
  Current Speed                 3336MHz[/COLOR][/B]
  Status                        Enabled Populated
  Processor Upgrade             Socket 940
  L1 Cache Handle               0005h
  L2 Cache Handle               0006h
  L3 Cache Handle               [Not Present]
  Serial Number                                       
  Asset Tag Number                                    
  Part Number                   To Be Filled By O.E.M.

For the time being stop over clocking and see if it stops the BSOD.

 

[ImpetuousRacer]

Looking at some of your system information it come to my attention that you are overclocking:

[Processor Information (Type 4) - Length 35 - Handle 0004h]
  Socket Designation            CPUSocket
  Processor Type                Central Processor
  Processor Family              edh - Specification Reserved
  Processor Manufacturer        AMD              
  Processor ID                  620f1000fffb8b17
  Processor Version             AMD Athlon(tm) II X2 245 Processor                  
  Processor Voltage             8fh - 1.5V
  External Clock                200MHz
[B][COLOR=Red]  Max Speed                     2900MHz
  Current Speed                 3336MHz[/COLOR][/B]
  Status                        Enabled Populated
  Processor Upgrade             Socket 940
  L1 Cache Handle               0005h
  L2 Cache Handle               0006h
  L3 Cache Handle               [Not Present]
  Serial Number                                       
  Asset Tag Number                                    
  Part Number                   To Be Filled By O.E.M.

For the time being stop over clocking and see if it stops the BSOD.

I built the computer a year ago, did the OC settings, burn in test, etc. Has been working fine, so I dont think its the OC. Regardless, I put the clock settings to stock, still BSOD now pointing at storport.sys.

At this point Im going to run a memory test and harddrive test to see what's going on. Ill report back after that. Thanks.

 

[Dsprague]

I look forward to your results.

 

[ImpetuousRacer]

Western Digital Hard Drive test passed, Memtest 4.20 ran 2 passes and no errors.
Here is my latest dump files: https://www.dropbox.com/s/2whwdslqrzn4ae9/LatestDump.zip

They all appear to point to storport.sys
Ive updated nvdia sata drivers, but the latest available arent that new. Not sure what uses storport.sys.
Any ideas? Thanks for the help!

 

[x BlueRobot]

storport.sys is a Microsoft Storage Driver, it's unlikely to be the problem.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[ImpetuousRacer]

storport.sys is a Microsoft Storage Driver, it's unlikely to be the problem.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

The drives are western digital, I used data lifeguard diagnostics and ran an extended test on each drive without any errors.

Screenshot from Crystal disk: https://www.dropbox.com/s/j43r7jnzw1e0v0e/Screen.jpg

I ran chkdsk /r, here were the results: https://www.dropbox.com/s/q8b2l8bheopo0le/chkdsk.jpg

I did the SFC Scannow "Did not find any integrity violations"

 

[x BlueRobot]

That's good to know, and best to perform some memory diagnostics fully:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

 

[ImpetuousRacer]

The computer is for a business that is open 6 days a week, so I only had one day with it to do a multitude of things. I wanted it longer to run a more extended test, but didn't have the leisure.

In the sake of making things easier with less down time, I replaced every component on the computer but the PSU. Got a random BSOD, replaced the PSU, no more randoms so far. (Knock on wood). So I believe there was something flaky in the PSU. Thanks for helping with this problem. Can close this thread out now.Thanks guys!

 

[x BlueRobot]

That's good to know, mark this thread as solved if you feel you have no problems.