Recurring IRQL_NOT_LESS_OR_EQUAL-BSODs only when i leave my pc on over night

[SerialK]

Hi, Im using Win7 Professional 64bit
lately I got a problem with BSODs welcoming me in the morning when I go and look after my pc, which I left running over night.
Actually I use a little gadget named "AutoShutdown Restyled" to turn my pc of at a predefined time, which worked fine for years - but lately it seems it never reaches that time but crashes to an IRQL_NOT_LESS_OR_EQUAL BSOD at some point before..
I have never encountered BSODs when I'm actively using the PC so it seems to have something to do with the idle-time.

The BSODs show varying error codes. One time it was:
0x0000000A (0xFFFFF980000207C6, 0x0000000000000002, 0x0000000000000000, 0xFFFFF8000359D3E4
And one time:
0x0000000A (0xFFFFF980000207A4, 0x0000000000000002, 0x0000000000000000, 0xFFFFF800035A43E4
And one time:
0x0000000A (0xFFFFF980000206E6, 0x0000000000000002, 0x0000000000000000, 0xFFFFF8000359E3E4

I attached the minidumps and hope you can give me a hint how to solve the issue!

 

[terry5880]

i had that prob last year was something to do with a driver i think , grr not sure if it just went away or if i refformatted but i got help from here on it so i know someone will help

 

[terry5880]

hi m8 by going back on my posts it was route44 that helped alot with my prob i had a dodgy driver somewhere which needed upodating and also ram was bad but yours could be different error code to mine so await the experts m8

 

[terry5880]

hi m8 by going back on my posts it was route44 that helped alot with my prob i had a dodgy driver somewhere which needed upodating and also ram was bad but yours could be different error code to mine so await the experts m8

I couldn’t find any valuable information from the mini dump file which you uploaded. Probably because the file is broken down into two parts.

You may try to investigate the dump file on your own by downloading the Windows debugging tool.
Here’s where you can download the debugging tool from.

Debugging Tools for Windows - Overview
http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

Please choose whichever is appropriate for your system environment.
Once you install the debugging tool, follow the instructions given in the Microsoft Knowledge base article below on how to analyze the memory dump files generated by Windows for debugging.

How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

Alternatively, you may perform these basic troubleshooting steps as per your convenience.

Put your system in clean boot and perform the search. Check whether the error recur when in searching in clean boot state.

Steps to perform clean boot and check if you have the issue.

1. Click Start, type msconfig in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
2. On the General tab, click Selective Startup.
3. Under Selective Startup, click to clear the Load Startup Items check box.
4. Click the Services tab, click to select the Hide All Microsoft Services check box, and then click Disable All.
5. Click OK.
6. When you are prompted, click Restart.
7. After the computer starts, perform the file search test.

If the problem doesn’t recur, it means a third party software is conflicting with Windows process. Follow the method of elimination from this article to determine the root cause of the application crash.

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
http://support.microsoft.com/kb/929135

Note: Ensure to put the computer to normal state by following Step 7 in the above link

1) Click start, type msconfig.exe in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

2) On the General tab, click the Normal Startup option, and then click OK.
3) When you are prompted to restart the computer, click Restart.
More often than not, since BSOD is related to incompatible driver removing that particular fixes the issue.
Please check the device list in Device Manager and verify if there’s any error reported by device manager.

To go to device manager:
1) Go to start and type device manager.
2) Select device manager from the control panel list.
3) From the device list, see if there’s any exclamation mark or error reported. If so, you can remove the driver related to the device and install a new one.
4) If there’s no error reported, you can try disabling one device at a time and test until the problem appears. This will verify which driver is causing the conflict.
5) To disable a driver, right-click on the device and select properties. Go to driver tab and select disable.

Disable the following devices (if present).

a. Video Cards
b. Sound Card
c. Network Card
d. USB Devices and controller (Please don’t do this if you are using USB keyboard or Mouse or Wireless Keyboard or mouse)
e. CD and DVD
f. Modems
g. Ports (serial and parallel)

6) Once verified which device is causing the crash, remove the corresponding driver by double-clicking on the device, going to driver tab and clicking on “uninstall”.

Now go to the device manufacturer’s website and download the latest driver for the device that is compatible with Windows 7.

For driver updates, refer this link:

Update a driver for hardware that isn't working properly
http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly

You may also want to check this discussion on the same issue.
http://social.answers.microsoft.com.../thread/b89656f9-0c57-42cd-9076-719f19e193de/

 

[SerialK]

I couldn’t find any valuable information from the mini dump file which you uploaded. Probably because the file is broken down into two parts.

You may try to investigate the dump file on your own by downloading the Windows debugging tool.

WHat do you mean by the file being broken into two parts? Shall i re-upload the files? It's minidumps of different dates with the same crash..

I already tried around with the SDK Debgging tools but when i try to open the minidumps i get the following:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Eigene Dateien\Eigene Downloads\BSOD - dmp\102411-12402-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03250000 PsLoadedModuleList = 0xfffff800`03495670
Debug session time: Sun Oct 23 23:46:42.508 2011 (UTC + 1:00)
System Uptime: 0 days 3:17:14.134
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff980000207a4, 2, 0, fffff800035a43e4}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+3543e4 )

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

 

[SerialK]

Another incident this morning..
pc kept running fine through the night, until I switched on the shutdown tool this morning and half an hour later I saw the BSOD..

See anything about the shutdown tool in the minidump?

 

[Tmagic650]

What is a "shut down tool"? The power switch?

 

[SerialK]

What is a "shut down tool"? The power switch?

very funny.. i'm talking about a gadget called "Auto-Shutdown Restyled Pierre"
h**p://7thspace.com/sidebar_gadgets/465241/auto_shutdown_restyled_pierre.html

 

[Tmagic650]

Remove the shutdown tool and see if the BSOD's stop

 

[SerialK]

Remove the shutdown tool and see if the BSOD's stop

i used that tool without problems for years.. It seems there is a conflict between the tool and some other software.
I would like to find out what that OTHER software is and remove THAT..

 

[Tmagic650]

Good luck

 

[techfiend4]

last couple times ive had that error on several computers i have its been bad ram, run memtest

Sent from my SAMSUNG-SGH-I777 using Tapatalk