IRQL Not less or equal - Kernel-Power ID-41 while playing games

Memmorath · 17 Jun 2014

Hello

I am getting IRQL Not less or equal quite semi-often, they are all listed as Kernel-Power ID: 41 in the event log. Most often these happen when playing games.

I should note that my Windows 7 64bit is in Finnish.

Also, the event log attaches this message:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

<EventID>41</EventID>

<Version>2</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000002</Keywords>

<TimeCreated SystemTime="2014-06-10T11:28:43.480438300Z" />

<EventRecordID>6440432</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>Omistaja-PC</Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>
<Data Name="BugcheckCode">10</Data>

<Data Name="BugcheckParameter1">0x1f81fa90</Data>

<Data Name="BugcheckParameter2">0xf</Data>

<Data Name="BugcheckParameter3">0x1</Data>

<Data Name="BugcheckParameter4">0xfffff80003225b07</Data>

<Data Name="SleepInProgress">false</Data>

<Data Name="PowerButtonTimestamp">0</Data>

</EventData>

</Event>

And here is the zip from that gathering program.

PeregrineX · 17 Jun 2014

Hello, and welcome to SevenForums!

The BSOD is caused by your AMD Graphics driver:

Code:

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80079fc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b40e2000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000a9000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------
ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff8000304c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02f6ca88 fffff800`03015a3b : 00000000`00000124 00000000`00000000 fffffa80`079fc028 00000000`b40e2000 : nt+0x7cc40
fffff880`02f6ca90 00000000`00000124 : 00000000`00000000 fffffa80`079fc028 00000000`b40e2000 00000000`a9000135 : hal+0x12a3b
fffff880`02f6ca98 00000000`00000000 : fffffa80`079fc028 00000000`b40e2000 00000000`a9000135 fffffa80`07e1c4c0 : 0x124


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

BUCKET_ID:  WRONG_SYMBOLS

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

I see that your AMD drivers are outdated:

Code:

amdide       amdide                 amdide                 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          4ÿ096      0      14.7.2009 2:19:49      C:\Windows\system32\drivers\amdide.sys           4ÿ096
AmdK8        AMD K8 Processor Drive AMD K8 Processor Drive Kernel        Manual     Stopped    OK         FALSE       FALSE        28ÿ672     16ÿ384     0      14.7.2009 2:19:25      C:\Windows\system32\drivers\amdk8.sys            8ÿ192
AmdPPM       AMD-suoritinohjain     AMD-suoritinohjain     Kernel        Manual     Running    OK         TRUE        FALSE        28ÿ672     12ÿ288     0      14.7.2009 2:19:25      C:\Windows\system32\DRIVERS\amdppm.sys           4ÿ096  
amdsata      amdsata                amdsata                Kernel        Manual     Stopped    OK         FALSE       FALSE        0          90ÿ112     0      19.3.2010 2:45:17      C:\Windows\system32\drivers\amdsata.sys          4ÿ096
amdsbs       amdsbs                 amdsbs                 Kernel        Manual     Stopped    OK         FALSE       FALSE        0          172ÿ032    0      20.3.2009 20:36:03     C:\Windows\system32\drivers\amdsbs.sys           4ÿ096
amdxata      amdxata                amdxata                Kernel        Boot       Running    OK         TRUE        FALSE        8ÿ192      8ÿ192      0      19.3.2010 18:18:18     C:\Windows\system32\drivers\amdxata.sys          4ÿ096
AtiPcie      AMD PCI Express (3GIO) AMD PCI Express (3GIO) Kernel        Boot       Running    OK         TRUE        FALSE        4ÿ096      4ÿ096      0      5.5.2009 18:00:22      C:\Windows\system32\DRIVERS\AtiPcie.sys          4ÿ096

Please update the drivers from the AMD Website

Best of luck,

PeregrineX

Memmorath · 17 Jun 2014

Hey, thank you for quick answer.

However, I do not use AMD Graphics card, but GeForce GTX 760.
How should I try to fix these drivers, then?

PeregrineX · 17 Jun 2014

Memmorath said:

Hey, thank you for quick answer.

However, I do not use AMD Graphics card, but GeForce GTX 760.
How should I try to fix these drivers, then?

Yes, I see that now, but you have an AMD CPU.

I will have a look at this in a bit, I have to go to the pool right now.

Boozad · 17 Jun 2014

CPU-Z needs updating or removing.

Code:

0: kd> lmvlm cpuz136_x64
start             end                 module name
fffff880`139a8000 fffff880`139b1000   cpuz136_x64 T (no symbols)           
    Loaded symbol image file: cpuz136_x64.sys
    Image path: \??\C:\Windows\TEMP\cpuz136\cpuz136_x64.sys
    Image name: cpuz136_x64.sys
    Timestamp:        Sat Oct 27 18:24:41 2012 (508C18D9)
    CheckSum:         0000F097
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Logitech camera driver is also old.

Code:

2: kd> lmvm lvrs64
start             end                 module name
fffff880`0952b000 fffff880`0957ea80   lvrs64   T (no symbols)           
    Loaded symbol image file: lvrs64.sys
    Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Wed Jan 18 06:40:36 2012 (4F166964)
    CheckSum:         00061E9E
    ImageSize:        00053A80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for updates here.

Run chkdsk to check your HDD. Disk Check

Download and run SeaTools. SeaTools for DOS and Windows - How to Use

Download and run MemTest86+ to test your RAM.
[/note]Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here.[/url]

Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

Run Furmark to stress test you GPU. Video Card - Stress Test with Furmark

Uninstall DaemonTools, a known cause of BSODs.

1. Uninstall DaemonTools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below

If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

PeregrineX · 17 Jun 2014

Ok, your NVidia driver seems to be causing the issue here:

Code:

*******************************************************************************
*                                                                             *
*                        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: 000000001f7ffe80, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000001, 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: fffff80003809b07, address which referenced memory

Debugging Details:
------------------
ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80003207000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  525da526

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 000000001f7ffe80 

CURRENT_IRQL:  0

FAULTING_IP: 
hal+1db07
fffff800`03809b07 8902            mov     dword ptr [rdx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff8000327c169 to fffff8000327cbc0

STACK_TEXT:  
fffff880`0c9eb268 fffff800`0327c169 : 00000000`0000000a 00000000`1f7ffe80 00000000`0000000f 00000000`00000001 : nt+0x75bc0
fffff880`0c9eb270 00000000`0000000a : 00000000`1f7ffe80 00000000`0000000f 00000000`00000001 fffff800`03809b07 : nt+0x75169
fffff880`0c9eb278 00000000`1f7ffe80 : 00000000`0000000f 00000000`00000001 fffff800`03809b07 fffff880`113cc8d6 : 0xa
fffff880`0c9eb280 00000000`0000000f : 00000000`00000001 fffff800`03809b07 fffff880`113cc8d6 00000000`bf800000 : 0x1f7ffe80
fffff880`0c9eb288 00000000`00000001 : fffff800`03809b07 fffff880`113cc8d6 00000000`bf800000 00000000`00000000 : 0xf
fffff880`0c9eb290 fffff800`03809b07 : fffff880`113cc8d6 00000000`bf800000 00000000`00000000 00000000`00000000 : 0x1
fffff880`0c9eb298 fffff880`113cc8d6 : 00000000`bf800000 00000000`00000000 00000000`00000000 00000000`00000000 : hal+0x1db07
fffff880`0c9eb2a0 00000000`bf800000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1a18d6
fffff880`0c9eb2a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xbf800000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+1a18d6
fffff880`113cc8d6 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nvlddmkm+1a18d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID:  WRONG_SYMBOLS

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

I see your NVidia drivers are mostly up-to-date. In that case you can try reinstalling those drivers.

Best of luck,

PeregrineX