Solved Random BSOD - IRQL NOT LESS OR EQUAL -

[kaid]

Good day.


Recently, I encountered a few blue screens and I decided to ask you guys for help regarding this issue.


The blue screen was encountered 2 times when the laptop was left idle for approximately 8 hours and one time today but not in idle.


I have attached a zip with the required logs.

Thank you for your help.

 

[Arc]

Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 14.4 WHQL only.

When done, Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html .

http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html.

Let us know the results.
_______________________________________

BugCheck A, {0, 2, 0, fffff800030d6e52}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )

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

6: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800030d6e52, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003308100
GetUlongFromAddress: unable to read from fffff800033081c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+42
fffff800`030d6e52 488b3f          mov     rdi,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

TRAP_FRAME:  fffff88007eefa00 -- (.trap 0xfffff88007eefa00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff880032f9180
rdx=fffffa800acbf420 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d6e52 rsp=fffff88007eefb90 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff88007eefc20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po cy
nt!KiSignalSynchronizationObject+0x42:
fffff800`030d6e52 488b3f          mov     rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d0169 to fffff800030d0bc0

STACK_TEXT:  
fffff880`07eef8b8 fffff800`030d0169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07eef8c0 fffff800`030cede0 : fffff880`07eef9f8 00000000`00000004 00000000`00000000 fffffa80`0acbf428 : nt!KiBugCheckDispatch+0x69
fffff880`07eefa00 fffff800`030d6e52 : fffffa80`0acbf3b0 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`07eefb90 fffff800`030d5256 : 00000000`00000000 fffff880`0f20b1d8 00000000`00000000 fffffa80`0ad59410 : nt!KiSignalSynchronizationObject+0x42
fffff880`07eefbe0 fffff880`0f21b47f : fffffa80`00000000 00000000`00000000 fffffa80`0ba11300 fffff880`07eefca0 : nt!KeSetEvent+0x106
fffff880`07eefc50 fffff880`0f2392e9 : fffffa80`00000000 fffffa80`0ad59410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`07eefca0 fffff880`0f238574 : fffff800`0462d080 fffffa80`0a8aeb90 00000000`00000000 fffffa80`0ad59410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`07eefcd0 fffff880`0f238012 : 00000000`00000000 fffffa80`0a8aeb90 00000000`00000080 fffffa80`0ad59410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`07eefd00 fffff800`0336c73a : 00000000`01be277e fffffa80`0ac35060 fffffa80`06d19b30 fffffa80`0ac35060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`07eefd40 fffff800`030c18e6 : fffff800`0324be80 fffffa80`0ac35060 fffff800`03259cc0 fffffa80`07e55190 : nt!PspSystemThreadStartup+0x5a
fffff880`07eefd80 00000000`00000000 : fffff880`07ef0000 fffff880`07eea000 fffff880`07eef400 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmiProcessTerminationCommand+5f
fffff880`0f21b47f 33d2            xor     edx,edx

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VidMmiProcessTerminationCommand+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_dxgmms1!vidmmiprocessterminationcommand+5f

FAILURE_ID_HASH:  {24a5b05f-0da8-ee02-b6e4-43c87a433b59}

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

 

[kaid]

Good day.

I want to thank you for your time and work.

I have followed every step and it was all good.

During the Fusmark test, no BSOD / crash was encountered.


I will come back with an answer to let you know if the problem was fixed.

Many thanks and have a good day.


Speccy link - http://speccy.piriform.com/results/Qg6qBCpQIOMShiFp3q6g6N7

 

[kaid]

I have just received another BSOD.

I have attached two logs, one from last night and the one generated today after I installed the CCC 14.4 WHQL.

 

[Arc]

From you speccy snapshot ......

CPU
Intel Core i7 740QM @ 1.73GHz:
74 °C
Clarksfield 45nm Technology

RAM
8.00GB Dual-Channel DDR3 @ 664MHz (9-9-9-24)

Motherboard
Hewlett-Packard 1448 (CPU):
74 °C

The computer is set on fire, almost. You need to control the temps at once. Otherwise it may go fatal.

Your computer needs dusting and re-applying thermal paste. Open the computer clean the inside very carefully using compressed air. Clean all the air vents and fan grills so that it can blow the hot air out efficiently. When you are re-seating the computer, apply new thermal paste to the CPU.



If you cannot do it yourself, get it done by somebody who can. You can take the help of the professionals too. But it would be highly important. Do it as early as possible, preferably at once.

 

[kaid]

Thanks for your reply, so most likely this is the cause of the BSOD?

 

[Arc]

Thanks for your reply, so most likely this is the cause of the BSOD?

That might not be a single cause, but one of the causes for sure; and which is to be minimized at once. Dont let the computer run with such high temps .... it may affect the hardware components.