Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL + bugcheck 0x000000d1


12 Mar 2014   #1

Windows 8 Pro x64
 
 
Random BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL + bugcheck 0x000000d1

Hello,

I actually looked around using the BlueScreenView tool and I'm not getting a whole lot except that ntoskrnl.exe is crashing in certain memory locations. I'm not sure if it's a memory error or possibly something else. I'd like to get a second opinion before I potentially have to take down my media server for several hours using memtest.

I've attached all the requested logs. Anyone see anything I missed?




Attached Files
File Type: zip debug-SHAGOHOD-Wed_03_12_2014_142506_52.zip (666.8 KB, 1 views)
My System SpecsSystem Spec
.

12 Mar 2014   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Hello webhead and welcome to the forum,

Have you checked for BIOS updates.
Code:
BIOS Version/Date	Phoenix Technologies, LTD ASUS P5N32-E SLI ACPI BIOS Revision 1404, 2/25/2008
Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Please uninstall AVAST for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

ASACPI.sys Mon Mar 28 08:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Windows 7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

nvm62x64.sys Sat Oct 18 03:01:06 2008 (48F8FD12)
nVidia Ethernet Networking Driver (nForce chipset driver)
Driver Reference Table - nvm62x64.sys

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Run Disk Check on your Hard Drive(s): Disk Check

If this does not provide stability. Test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.


BSOD DUMP OUTPUT:
Code:
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar 11 06:38:10.136 2014 (UTC + 6:00)
System Uptime: 0 days 10:18:04.182
BugCheck D1, {fffff80012493f32, 2, 8, fffff80012493f32}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  PlexDlnaServer
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar 10 20:18:47.273 2014 (UTC + 6:00)
System Uptime: 0 days 0:27:17.303
BugCheck 1A, {41790, fffffa800091af70, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  DUEngine.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar 10 19:50:04.077 2014 (UTC + 6:00)
System Uptime: 0 days 3:07:03.717
BugCheck 1A, {41790, fffffa800091af40, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+360e8 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SABnzbd-servic
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar 10 16:41:24.501 2014 (UTC + 6:00)
System Uptime: 6 days 7:37:35.818
BugCheck D1, {fffff8001349ff32, 2, 8, fffff8001349ff32}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  deluge.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Mar  4 09:02:40.091 2014 (UTC + 6:00)
System Uptime: 1 days 6:04:43.135
BugCheck D1, {fffff8001348bf32, 2, 8, fffff8001348bf32}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  PlexDlnaServer
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Let us know the results.
My System SpecsSystem Spec
Reply

 Random BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL + bugcheck 0x000000d1




Thread Tools



Similar help and support threads for2: Random BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL + bugcheck 0x000000d1
Thread Forum
BSOD code: 0x000000d1 DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD Help and Support
BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 BSOD Help and Support
BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000D1 BSOD Help and Support
Solved BSOD bugcheck 0x000000d1 BSOD Help and Support
BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL: error 0x000000d1 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 07:05 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33