BSOD random ntoskrnl.exe error i'm clueless :(

[zirconicus]

I'm getting this BSOD random every 10-20 hours max,always the same one.
Minidump is attached.

Always the same IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe

I tried a complete memtest and all is OK
i tried a complete windows 7 64bit reinstall with formatting and still the same BSOD

My configuration :

Intel I7 860
12 gb ram crucial 1600mhz
main hd : crucial m4 ssd 128 gb
secondary hd : WD green 2 tb
gpu : XFX ATI 5850 1 gb ram
motherboard : Asus P7P55D LE Intel P55 Socket 1156 DDR3 1600 2xPci Express Integrated:Lan-Audio RETAIL
monitor : dell U2410

no overclock

I'm without a clue sigh please help

I had this configuration from 1 year now and BSOD started to appear like 1 month ago

I have to say that my crucial m4 ssd is with first firmware...should i update it and retest?

 

[writhziden]

Yes, update your SSD to the latest firmware. There have been known problems with the Crucial M4 without the latest firmware. See http://www.sevenforums.com/crashes-...ect_termination-1-hour-after-cold-boot-3.html

You will also want to update the following driver:

ASACPI	fffff880`05698000	fffff880`056a0000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys

There is not an update through your Motherboard support site, but you can update it for a different motherboard since it is just an ASUS utility and not an actual device driver.

• Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
  1. Going to the Asus motherboard support site
     When you reach the website:
  2. Scroll down the page and click Utilities
  3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
  4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
  5. Download and install the driver.
  6. After installation is complete, verify that it installed correctly.
     • Click Start Menu
     • Click My Computer
     • Go to C:\WIndows\System32\drivers\
     • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
  
  Thanks to JMH and zigzag3143 for the above information.

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


Loading Dump File [D:\Kingston\BSODDmpFiles\zirconicus\040412-22167-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a13000 PsLoadedModuleList = 0xfffff800`02c57650
Debug session time: Wed Apr  4 00:04:27.678 2012 (UTC - 6:00)
System Uptime: 1 days 8:35:53.693
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002a96052}

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: fffff80002a96052, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc1100
 0000000000000000 

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

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

LAST_CONTROL_TRANSFER:  from fffff80002a8f2e9 to fffff80002a8fd40

STACK_TEXT:  
fffff880`021608b8 fffff800`02a8f2e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`021608c0 fffff800`02a8df60 : fffff880`030f9180 fffff800`03002ae7 00000000`00000001 fffffa80`0d0c1a78 : nt!KiBugCheckDispatch+0x69
fffff880`02160a00 fffff800`02a96052 : fffffa80`0d0c1a00 00000000`00000000 00000000`00000001 fffff800`02a96010 : nt!KiPageFault+0x260
fffff880`02160b90 fffff800`02a94456 : 00000000`00000000 fffff880`057c51cc 00000000`00000000 fffffa80`0bfbe410 : nt!KiSignalSynchronizationObject+0x42
fffff880`02160be0 fffff880`057d536b : fffffa80`00000000 00000000`00000000 fffffa80`0d1a3a00 fffff880`02160ca0 : nt!KeSetEvent+0x106
fffff880`02160c50 fffff880`057f316d : fffffa80`00000000 fffffa80`0bfbe410 00000000`6d4d6956 fffff880`00000174 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`02160ca0 fffff880`057f23f8 : fffff880`009f1040 fffffa80`0b992950 00000000`00000000 fffffa80`0bfbe410 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`02160cd0 fffff880`057f1e96 : 00000000`000179fa fffffa80`0b992950 00000000`00000080 fffffa80`0bfbe410 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`02160d00 fffff800`02d29f7a : 00000000`034af2c9 fffffa80`0bfa7b60 fffffa80`0973db30 fffffa80`0bfa7b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02160d40 fffff800`02a809c6 : fffff880`009ec180 fffffa80`0bfa7b60 fffff880`009f70c0 2c307830`2c307830 : nt!PspSystemThreadStartup+0x5a
fffff880`02160d80 00000000`00000000 : fffff880`02161000 fffff880`0215b000 fffff880`02160470 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmiProcessTerminationCommand+5f
fffff880`057d536b 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:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

BUCKET_ID:  X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f

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

Your crash is blaming DirectX which means something out of whack with DirectX or your graphics card or the drivers involved.

• Try re-installing DirectX using the http://www.microsoft.com/download/en/details.aspx?id=8109 and see how the system responds.
  
  Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For NVIDIA:
     • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
     • Restart your computer
     • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
     • If any remain of the above, uninstall one at a time
     • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
  6. For AMD:
     • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
     • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
       1. Download the latest drivers for your display card(s)
       2. Click Start Menu
       3. Right Click My Computer/Computer
       4. Click Manage
       5. Click Device Manager from the list on the left
       6. Expand Display adapters
       7. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
       8. Restart your computer after uninstalling drivers for all display cards
       9. Install the latest driver for the display cards once Windows starts
       
       Alternatively:
       1. Login as an adminstrative user
       2. Download the latest drivers for your display card(s)
       3. Click Start Menu
       4. Click Control Panel
       5. Click Hardware and Sound
       6. Click Device Manager (the last link under Devices and Printers)
       7. Expand Display adapters
       8. Do the following for each adapter (in case you have multiple display cards)
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  7. Restart your computer after uninstalling drivers for all display cards
  8. Install the latest driver for the display cards once Windows starts

 

[zirconicus]

Thanks a lot,i updated my ssd firmware and still no BSOD,finger crossed.

If i receive another BSOD i will update the other one

Thanks a lot for your analisys !

 

[writhziden]

You're welcome. Best of luck the SSD firmware update resolved it. Run for a few days and see how the system responds, then post back whether it is solved or not.

 

[zirconicus]

Today after 3 days of perfect running (never happened before the ssd firmware upgrade) another BSOD, the same as usual so the problem is not gone

Is it the same problem ?

Thanks

 

[zirconicus]

For now i have updated directx and ASACPI.SYS as you suggested me. Let's see

 

[writhziden]

Yes, it is the same problem as before pointing to DirectX/graphics card problems. See how the system responds after doing the steps for ASACPI.SYS and DirectX.

 

[zirconicus]

Another BSOD,the same one,only 10 hours after the previous

I'm starting to think about a hardware problem...maybe i can try changing ram slots or gpu with another one ? I have a spare nvidia 9800gt around (shitty card compared to mine,sad face). Or maybe the PSU ?

Nothing else remains i think....my drivers are the latest from ati,installed from scratch after a complete windows7 format and reinstall,so it's useless to wipe em and reinstall

Help please

 

[writhziden]

Yes, still the same crash as before. It does appear to be a hardware issue with the card (or as you said, possibly the PSU). We should try to determine which. Some graphics hardware tests may be in order for the ATI card.

Also, make sure if you decide to switch graphics cards at some point that all ATI software is uninstalled through Start Menu -> Control Panel -> Uninstall a program beofre replacing the ATI card with an NVIDIA card (and vice versa if you switch back).

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

 

[zirconicus]

Another BSOD this morning,still the same one.
This morning i run a gpu memory complete test,all is ok.
I have just changed my GPU from the ATI 5850 to my Nvidia 9800GT. Let's see

If the BSOD will stop i think the problem should be the PSU...the nvidia card uses like 50% less watt than the ati card

 

[writhziden]

Alright, keep us posted with the NVIDIA card. Don't be too quick to rule out the ATI card as a possible cause, as well. Bad graphics cards are just as likely as bad PSUs. The best way to determine which it is would be to borrow a PSU from a friend that is rated better than your current PSU and see if the system is stable.

 

[zirconicus]

Still no BSOD,all is working smooth (except for 50% less gpu power of course ehehhe).

I think the problem should be the PSU then,this 9800 gt should drain 50% less watt than my ati 5850 :|

Sigh

 

[writhziden]

See if you can borrow a PSU from a friend that is rated higher and test whether the ATI card works with it. Make sure to remove all NVIDIA software and drivers before replacing the NVIDIA card with the ATI card.