BSOD's appearing casualy: IRQL_NOT_LESS_OR_EQUAL

Hello, my problem is that BSOD's are appearing. I dug up some information from similiar topics, but with no luck. I installed the Microsoft patch also.


Minidumps : Look from privatepaste or scroll down.
1. http://privatepaste.com/540e2gL089
2. http://privatepaste.com/1500eUpjQu

I have no experience on minidumps, only thing that I found out was that "steam.exe" is causing error?
I'll try reinstalling Steam.



Thank you, Wesku.

 

Ok. I'm sorry for the double-topic, I thought I closed the other one accidently, so I made new topic.

First Dump :


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini012708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b0c0
Debug session time: Sun Jan 27 15:51:55.687 2008 (GMT+2)
System Uptime: 0 days 0:23:17.244
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*** WARNING: Unable to verify timestamp for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {fffe8080, 2, 1, 806ef2dc}



Probably caused by : ntoskrnl.exe ( nt!NtWaitForMultipleObjects+112 )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffe8080, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 806ef2dc, address which referenced memory

Debugging Details:
------------------




WRITE_ADDRESS: fffe8080

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpStopOhciInterrupt+5c
806ef2dc 890d8000feff mov dword ptr ds:[0FFFE0080h],ecx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: steam.exe

LAST_CONTROL_TRANSFER: from 80566374 to 806ef2dc

STACK_TEXT:
edf62cf0 80566374 00000000 00000001 00000000 hal!HalpStopOhciInterrupt+0x5c
edf62d54 804de7ec 00000368 00000000 1111fe14 nt!NtWaitForMultipleObjects+0x112
edf62d64 7c90eb94 badb0d00 1111fe0c 10e1fd84 nt!KiUnexpectedInterrupt65+0x2
WARNING: Frame IP not in any known module. Following frames may be wrong.
edf62d68 badb0d00 1111fe0c 10e1fd84 00000000 0x7c90eb94
edf62d6c 1111fe0c 10e1fd84 00000000 00000000 0xbadb0d00
edf62d70 10e1fd84 00000000 00000000 00000000 0x1111fe0c
edf62d74 00000000 00000000 00000000 00000000 0x10e1fd84


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+112
80566374 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!NtWaitForMultipleObjects+112

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 469f609b

FAILURE_BUCKET_ID: 0xA_W_nt!NtWaitForMultipleObjects+112

BUCKET_ID: 0xA_W_nt!NtWaitForMultipleObjects+112

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

 

Second Dump :

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini012708-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b0c0
Debug session time: Sun Jan 27 15:57:28.671 2008 (GMT+2)
System Uptime: 0 days 0:03:05.221
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*** WARNING: Unable to verify timestamp for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {fffe9080, 2, 1, 806ef2dc}



Probably caused by : ntoskrnl.exe ( nt!NtWaitForMultipleObjects+112 )

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

kd> !analyz -v
No export analyz found
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffe9080, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 806ef2dc, address which referenced memory

Debugging Details:
------------------




WRITE_ADDRESS: fffe9080

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpStopOhciInterrupt+5c
806ef2dc 890d8000feff mov dword ptr ds:[0FFFE0080h],ecx

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: steam.exe

LAST_CONTROL_TRANSFER: from 80566374 to 806ef2dc

STACK_TEXT:
edecfcf0 80566374 00000000 00000001 00000000 hal!HalpStopOhciInterrupt+0x5c
edecfd54 804de7ec 0000036c 00000000 1111fe14 nt!NtWaitForMultipleObjects+0x112
edecfd64 7c90eb94 badb0d00 1111fe0c 00000000 nt!KiUnexpectedInterrupt65+0x2
WARNING: Frame IP not in any known module. Following frames may be wrong.
edecfd68 badb0d00 1111fe0c 00000000 00000000 0x7c90eb94
edecfd6c 1111fe0c 00000000 00000000 00000000 0xbadb0d00
edecfd70 00000000 00000000 00000000 00000000 0x1111fe0c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtWaitForMultipleObjects+112
80566374 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!NtWaitForMultipleObjects+112

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 469f609b

FAILURE_BUCKET_ID: 0xA_W_nt!NtWaitForMultipleObjects+112

BUCKET_ID: 0xA_W_nt!NtWaitForMultipleObjects+112

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

 

The debung report is incomplete as it does not have module list and it is very useful to find out the root cause of the problem. The crash was occurred when you invoke steam.exe. What is steam.exe? You have to make sure that your windows is infected with virus.

 

Steam is a trusted gaming "client" by Valve. Apparently reinstalling it helped.
But I only got BSOD's when my cpu was OCed, so did those BSOD's come because of Steam only? Or is there some errors about overheating?
I think the cpu didn't overheat as the temp only raised by ~4'C when OCing.

 

I would reckon OCing it caused the BSOD's.
Especially if you didn't have any extra cooling onto the CPU and motherboard.
At the very least you should add a extra case fan. One can be had for $25 or cheaper at radio shack.

Good Luck

 

As I said cpu temperature only got up with ~4'C when OCed. I think that isn't overheating, as without OCing it goes above that when gaming. But now it's working, even when OCed and I have 3 or 4 extra fans.

 

Try and run the debugwiz on the same computer the problem occured on and make sure the c:\symbols directory is getting created so the symbols will be correct. Then snippet below indicates it's looking in the wrong place for the symbols and the !analyze isn't complete.

Symbol search path is: C:\windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Good Luck,

John

 

Hi, Wesku.

As PeteC suggested (and debugnt referenced), please carefully follow all the instructions in this link and paste your DebugWiz-generated dump analysis logs here.

I expect following those instructions carefully will address the concerns cpc2004 stated about the missing module list and the concerns debugnt stated about the symbols path.

After running the DebugWiz tool (while connected to the Internet), the symbols search path and executable search path shown in the C:\debuglog.txt file should be displayed as
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers

Please verify the search paths above are the same as yours before pasting more dump logs. If yours are different, please let us know so we can offer suggestions about how to fix the search paths.

I noticed the dump logs you posted above are for system crashes that occurred on January 27, 2008 unless your computer clock's date is incorrect. Please hover your mouse cursor over your computer's clock in the lower right corner of your screen and verify the date is correct.

Please paste DebugWiz-generated dump logs for your most recent system crashes (BSODs).

When using the DebugWiz tool to browse to the C:\WINDOWS\Minidump\ folder, look for dump files that are named as follows.

 

I expect overclocking can also produce system instability in other ways besides CPU temperature.

Perhaps mattman, Rockster2U, or one of the other hardware gurus will see this thread and offer some advice.

EDIT: I expect they will want details about your hardware. Therefore, I suggest you post those details so they have something to work with.

• motherboard brand and model
• motherboard BIOS version
• motherboard chipset driver version
• CPU brand, model, speeds (both the manufacturer's speed and OC'd speed), and voltage
• RAM brand, model, timings, number of sticks, and which slots they are using
• graphics card brand, model, and driver version
• power supply unit (PSU) brand, model, power (watts), and +12V amperage rating (all printed on the PSU)
• sound card (if installed) brand, model, and driver version
• etc.