Driver IRQL not less or equal - 0x000000D1

[sparks72]

Hi,

I've had around 5 random BSOD on this machine since I re-installed Windows7 yesterday. Nothing harsh, just browsing the web. I also put together an old (5 years old) Asus P4 system the other day and had exactly the same BSOD 'Driver IRQL not less or equal - 0x000000D1' I found that odd as I'd never experienced BSOD on either machine in the past!
I got thinking if new windows updates had anything to do with it!....Hmmmmm..

Many thanks for your help

 

[x BlueRobot]

[COLOR="Red"]BugCheck D1[/COLOR], {fffffa800a126004, 2, 0, fffffa800904922f}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Usual causes:  Device driver

It seems there is most likely a problem with the drivers, a driver has attempted to access a memory address which isn't yet present, the current IRQL level (DISPATCH_LEVEL) means that other threads will need to be scheduled to run, although a driver has tried to interrupt the CPU when it shouldn't have, and this has caused the bugcheck.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Remove:

Start Menu\Programs\Driver Genius

These third-party driver updating programs are not needed and can cause problems, it is best to search for driver updates manually and then install these drivers through the Windows Device Manager.

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

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

 

[sparks72]

Thanks x BlueRobot. I Will give it a whirl and post the results.......Driver Genius has been binned.

 

[sparks72]

Hi,

Before running Driver Verifier, Windows crashed once last night while I was browsing the web using Firefox.
When I ran the Driver Verifier all ran well without any BSOD! verifier.exe is still running in the background, I'll switch it off a little later. Question, could a failing hard drive cause BSOD?
SFC / SCANNOW gave clean results........Speak of the devil, I just had a BSOD!

Here's the results.
Thanks


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>verifier /query
27/01/2013, 18:10:44
Level: 00000FBB
RaiseIrqls: 0
AcquireSpinLocks: 176180
SynchronizeExecutions: 5379
AllocationsAttempted: 642006
AllocationsSucceeded: 642006
AllocationsSucceededSpecialPool: 642006
AllocationsWithNoTag: 36
AllocationsFailed: 0
AllocationsFailedDeliberately: 0
Trims: 160502
UnTrackedPool: 473572

Verified drivers:

Name: amdxata.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: asupio.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: asio.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: nvlddmkm.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 62
CurrentNonPagedPoolAllocations: 6084
PeakPagedPoolAllocations: 80
PeakNonPagedPoolAllocations: 6147
PagedPoolUsageInBytes: 756172
NonPagedPoolUsageInBytes: 3552124
PeakPagedPoolUsageInBytes: 1866364
PeakNonPagedPoolUsageInBytes: 3561660

Name: hecix64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 2
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 5
PagedPoolUsageInBytes: 112
NonPagedPoolUsageInBytes: 212
PeakPagedPoolUsageInBytes: 112
PeakNonPagedPoolUsageInBytes: 708

Name: rt64win7.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 4105
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 4105
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 572588
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 572588

Name: ndis.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 6
CurrentNonPagedPoolAllocations: 8923
PeakPagedPoolAllocations: 8
PeakNonPagedPoolAllocations: 8996
PagedPoolUsageInBytes: 984
NonPagedPoolUsageInBytes: 2696748
PeakPagedPoolUsageInBytes: 1296
PeakNonPagedPoolUsageInBytes: 2723076

Name: nusb3xhc.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 2
CurrentNonPagedPoolAllocations: 30
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 32
PagedPoolUsageInBytes: 212
NonPagedPoolUsageInBytes: 518836
PeakPagedPoolUsageInBytes: 256
PeakNonPagedPoolUsageInBytes: 519160

Name: tapstrong.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 2
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 172
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 276
PeakNonPagedPoolUsageInBytes: 0

Name: nvhda64v.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 8
CurrentNonPagedPoolAllocations: 22
PeakPagedPoolAllocations: 9
PeakNonPagedPoolAllocations: 22
PagedPoolUsageInBytes: 5024
NonPagedPoolUsageInBytes: 14208
PeakPagedPoolUsageInBytes: 5044
PeakNonPagedPoolUsageInBytes: 14208

Name: nusb3hub.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 19
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 20
PagedPoolUsageInBytes: 116
NonPagedPoolUsageInBytes: 2240
PeakPagedPoolUsageInBytes: 156
PeakNonPagedPoolUsageInBytes: 2652

Name: rtkvhd64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 993
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 995
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 719496
PeakPagedPoolUsageInBytes: 408128
PeakNonPagedPoolUsageInBytes: 720488

Name: dump_dumpata.sys, loads: 0, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: dump_atapi.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: dump_dumpfve.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 16400
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 16400

Name: secdrv.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 72
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 316
PeakNonPagedPoolUsageInBytes: 0

C:\Windows\system32>

 

[x BlueRobot]

Could you upload the BSOD, and yes a failing hard-drive can cause problems including BSODs.

 

[sparks72]

Could you upload the BSOD, and yes a failing hard-drive can cause problems including BSODs.

Sure, Minidump or screenshot?
(Will have to wait for both as I accidentally cleared everything with CCleaner )

I asked about the hard drive as I had reinstalled Windows7 twice in 3 days.
1st time around the hard drive was working overtime and seemed to be spinning faster than I'd heard it before, images were taking long to load while browsing the web, overall the machine seemed sluggish.

The 2nd time (what's installed now) is better but I still feel the hard drive is playing up a little, although it's less active than the first re installation.

I scanned the hard drive using HDDScan, all came back clear. Will post again if BSOD occurs.

Thanks.

 

[x BlueRobot]

When it was 'sluggish' was Driver Verifier enabled? If the case, then Driver Verifier would have caused this slow down, since it is designed to stress all the drivers and hopefully point out a buggy or corrupted driver with a BSOD being produced.

A Minidump would be great, thanks!

 

[sparks72]

When it was 'sluggish' was Driver Verifier enabled?

No it was a fresh install. As I was installing Windows updates the HD was working overtime.
Whenever I reinstall windows I do all the updates first then install 3rd party software.

Just remembered, while installing Windows updates early yesterday many failed to install, around 90% to be exact. after going through the process again they installed with success (bar a couple)
The same thing happened on the second lot of MS updates!!!!

 

[x BlueRobot]

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

:info: Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system.

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

 

[sparks72]

Thanks,

I have paid for Eset smart Security 6, into it's 5th year now. I usually use and run a Malware bytes scan when I suspect something isn't right, just did a full scan, all clean. I've not had one BSOD since my last post..........

 

[x BlueRobot]

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

:info: Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

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

It's good to know, no other BSODs have occurred as of yet.

 

[sparks72]

Hi,

OK, got a BSOD on first PC boot of the day, as soon as desktop appeared it crashed!
I've tried most of the above and have posted the results in a zip file. The Hitachi disk health app failed to work at all so I ditched it in favour of CrystalDiskInfo. According to CrystalDiskInfo my hard drive is good!
Another thing I've noticed, in the top left corner of the boot screen their is a 'flashing line' similar to command prompt!

Thanks.

 

[x BlueRobot]

[COLOR="Red"]BugCheck D1[/COLOR], {fffffa800812c002, 2, 0, fffffa8009e2122f}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Have you tested with Seagate Tools, there is a Windows version also available to use.

Memory:

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

Run Memtest86+ for least 9-10 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.

If you are still running Driver Verifier, then I suggest you disable it.

 

[sparks72]

Thanks,

I'll give it a go and report my finding.

 

[sparks72]

Right.

I had 4 more BSOD this evening. BUT.......during boot up the final BSOD showed this info on the possible problem.

'A device driver attempting to corrupt the system has been caught.
The faulty driver currently on the Kernel stack must be replaced with a working version...................
..........................*** AsupIo.sys...................

It looks like it might have been the Asus AI suite II software that came with the motherboard. I removed it, all running well for now, I'll see what happens.

 

[x BlueRobot]

Yes, it linked to the Asus Hardware Monitoring software, and is best to completely removed; let's see what happens.

 

[sparks72]

No BSOD since my last post and the removal of Asus AI suite II, although the hard drive still doesn't sound healthy at times. I'm going to purchase a new HD. Funny, the Asus AI suite II worked fine when I first installed the motherboard back in July, then decided to start playing up during a clean installation.

 

[sparks72]

Still no BSOD. (New HD arriving this week)

Thanks for your help x BlueRobot

 

[x BlueRobot]

That's great news

 

[sparks72]

It seems I spoke too soon. Got BSOD Driver IRQL not less or equal again

Hmmmm, the machines been running like a dream all day and then this happens again!
I Installed a new Samsung Hard hard drive today, it's working a lot quieter than the other HD.
I removed the graphics card, I'm using the on board graphics to test for problems. I did install Asus AI Suite II
again, I've read that others have had problems with it, It was running fine on my PC till the hard drive started playing up.

Thanks.