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: BSOD Every Day - DRIVER_IRQL_IS_NOT_LESS_OR_NOT_EQUAL

08 Sep 2014   #1
rowls93

Windows 7 Home Premium x64
 
 
BSOD Every Day - DRIVER_IRQL_IS_NOT_LESS_OR_NOT_EQUAL

Hi guys i keep getting this error on my PC, it is extremely annoying and so far i have tried 2 graphics cards, interchanging my RAM/Slots used, 2 HDD's and updating all my drivers, its driving me insane as the computer will either freeze solid or simply BSOD, please see attached dumps from the past week.


My System SpecsSystem Spec
.
09 Sep 2014   #2
rowls93

Windows 7 Home Premium x64
 
 

if it helps ive now gathered it only does this during diablo 3
My System SpecsSystem Spec
09 Sep 2014   #3
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi rowls93.

Click on the button below ....



It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums
My System SpecsSystem Spec
.

09 Sep 2014   #4
rowls93

Windows 7 Home Premium x64
 
 

there u go mate
My System SpecsSystem Spec
09 Sep 2014   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The crash dump reports it to be a display hardware issue.
Code:
BugCheck A, {3f8d5, 2, 1, fffff800034c719f}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3b9 )

Followup: MachineOwner
---------
Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

340.52 WHQL is not very stable with some of the systems. Try an older one .... Drivers | GeForce
Before installing the suggested driver,uninstall the installed version of the display driver using DDU.

And, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Let us know the results.
________________________________________
Code:
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {3f8d5, 2, 1, fffff800034c719f}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3b9 )

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

0: 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: 000000000003f8d5, memory referenced
Arg2: 0000000000000002, 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: fffff800034c719f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036fa100
GetUlongFromAddress: unable to read from fffff800036fa1c0
 000000000003f8d5 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+4f
fffff800`034c719f 2000            and     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF80004874FB0

TRAP_FRAME:  fffff8000486e500 -- (.trap 0xfffff8000486e500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000003f8d5 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034c719f rsp=fffff8000486e690 rbp=fffffa800eb0c450
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8010089bd0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeSetEvent+0x4f:
fffff800`034c719f 2000            and     byte ptr [rax],al ds:00000000`0003f8d5=??
Resetting default scope

MISALIGNED_IP: 
nt!KeSetEvent+4f
fffff800`034c719f 2000            and     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff800034c2169 to fffff800034c2bc0

STACK_TEXT:  
fffff800`0486e3b8 fffff800`034c2169 : 00000000`0000000a 00000000`0003f8d5 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`0486e3c0 fffff800`034c0de0 : 000a5a40`00000000 fffff800`034341e0 00000000`00000002 000a5a40`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`0486e500 fffff800`034c719f : fffffa80`1147d160 fffffa80`10089410 fffffa80`10089b80 fffff880`03d6848b : nt!KiPageFault+0x260
fffff800`0486e690 fffff880`03d662ed : fffffa80`00000000 fffffa80`00000000 fffffa80`101d3000 fffffa80`101d3000 : nt!KeSetEvent+0x4f
fffff800`0486e700 fffff880`03d657e6 : fffffa80`00000001 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x3b9
fffff800`0486e7c0 fffff880`03d64e0c : 00000000`00000000 fffffa80`0d25d6c0 00000000`00000000 00000000`00000005 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff800`0486e860 fffff880`03d64c58 : 00000000`00000001 fffffa80`10089410 fffffa80`0eaf6480 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff800`0486e8b0 fffff880`03c6a1cf : fffffa80`0eaf6480 00000000`00000000 fffff800`04868080 00000000`00000022 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff800`0486e900 fffff880`0f1b3d80 : fffffa80`0f296000 fffffa80`0f296000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff800`0486e930 fffffa80`0f296000 : fffffa80`0f296000 00000000`00000000 00000000`00000000 fffff880`0f1b3d13 : nvlddmkm+0xced80
fffff800`0486e938 fffffa80`0f296000 : 00000000`00000000 00000000`00000000 fffff880`0f1b3d13 fffffa80`0f296000 : 0xfffffa80`0f296000
fffff800`0486e940 00000000`00000000 : 00000000`00000000 fffff880`0f1b3d13 fffffa80`0f296000 00000000`00000000 : 0xfffffa80`0f296000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3b9
fffff880`03d662ed 48a12003000080f7ffff mov rax,qword ptr [FFFFF78000000320h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgmms1!VidSchiProcessCompletedQueuePacketInternal+3b9

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18126

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_ip_misaligned

FAILURE_ID_HASH:  {45769616-fd06-8c70-4b8b-74a01eddc0cd}

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

0: kd> lmvm hardware
start             end                 module name
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0e5000 fffff880`0fd73000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
09 Sep 2014   #6
rowls93

Windows 7 Home Premium x64
 
 

thanks for the reply mate, i'm not currently overclocking and the temperature is fine, also its a 1050watt corsair power supply and also i have ran furbench a few times and the outcome is usually fine, to mention i did try a amd radeon 7770 graphics card and still the same thing happened.
My System SpecsSystem Spec
09 Sep 2014   #7
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I would prefer to wait for a formal report of the system heat and the stress test.
My System SpecsSystem Spec
09 Sep 2014   #8
rowls93

Windows 7 Home Premium x64
 
 

also i have played many other games on top settings across all 3 screens and single monitor and have not had the problme just with diablo. i have also tried reinstalling it but this has made no difference
My System SpecsSystem Spec
09 Sep 2014   #9
rowls93

Windows 7 Home Premium x64
 
 

http://speccy.piriform.com/results/8...rZMerVwzD6iOwS

pc has been on and in use now for 6 hours gaming, not playing diablo though
My System SpecsSystem Spec
Reply

 BSOD Every Day - DRIVER_IRQL_IS_NOT_LESS_OR_NOT_EQUAL




Thread Tools Search this Thread
Search this Thread:

Advanced Search



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 20:49.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App