BSOD during games, crossfire 6950 - ntoskrnl.exe

Hi everyone,

Prior to this, everything was perfectly stable. I recently installed a second Radeon 6950 in crossfire and have been experiencing chronic BSOD crashes after 10-15 minutes in any game. The BSODs dont happen at any other time. Stress testing with Furmark doesnt cause any BSODs, so I dont think its a temperature/stress issue.

Ive tried the following:
- Swapped power supplies to a Seasonic Platinum 1000W
- Run each card individually (no problems)
- Wipe drivers clean with Driver Sweeper and install different versions (settled on 12.1 Catalysts)
- Swap card positions and use a different Crossfire bridge (extended period of time until a BSOD)
- Monitor temps which never go above 90C even at full load
- Use Driver Verifier followed by Startup Repair (to no avail)

Using Driver Verifier actually gives me a BSOD right before booting to desktop and punts me to Startup Repair, which finds a problem with ntoskrnl.exe but cant repair it. This happens in a loop and BSODs every time it boots with Verifier. Ive also tried booting normally (without Verifier on) straight to the Win7 DVD to do a startup repair, but no errors were found.

Looking at the dmp files in BlueScreenViewer always shows ntoskrnl.exe along with some other random files being responsible, but never the same one except for ntoskrnl.exe

Im at my wits end! I dont want to have to reinstall a fresh copy of Windows and reinstall all of my programs if I dont have to. Is there anything I can do? Ive attached all of my minidumps. Thanks in advance!

Intel Q6600 @ 3.6GHz
Asus Maximus Formula
8GB OCZ DDR2-800
ATI Radeon 6950 Crossfire
HDDs:
- 64GB Crucial M4 SSD
- 500GB Seagate 7200.11
- 1TB WD Black
- 1TB WD Green

Bump - could anyone help? Thanks!

Bump again - problem is still occurring! Any help or advice would be appreciated

which games are you playing? I was having BSOD's while playing BF3 (you need a browser open while playing it), i was getting the same type of BSOD's u were. Turns out that for some weird reason firefox and chrome eventually crash my system, IE9 does not. I started using IE9 and all my problems went away. You might want to try that i dont know for sure if it will help u.

Possible out of date drivers:

Code:

ASACPI	fffff880`06c6b000	fffff880`06c73000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
yk62x64	fffff880`06a2a000	fffff880`06a8d000	Mon Feb 23 08:02:27 2009 (49a2ba83)	0006049b		yk62x64.sys
LHidFilt	fffff880`08244000	fffff880`08257000	Wed Jun 17 10:49:39 2009 (4a391ea3)	00014ede	None	LHidFilt.Sys
LMouFilt	fffff880`08264000	fffff880`08278000	Wed Jun 17 10:49:43 2009 (4a391ea7)	0001d7ff		LMouFilt.Sys
L8042Kbd	fffff880`06a8d000	fffff880`06a98000	Wed Jun 17 10:50:43 2009 (4a391ee3)	00016327		L8042Kbd.sys

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.

yk62x64.sys
LHidFilt.Sys
LMouFilt.Sys
L8042Kbd.sys

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\harblhat\042312-19780-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`0305c650
Debug session time: Mon Apr 23 21:36:20.159 2012 (UTC - 6:00)
System Uptime: 0 days 3:39:30.797
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff2800923fdd8, 2, 1, fffff88000edcfc0}

*** WARNING: Unable to verify timestamp for LHidFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
Probably caused by : hardware ( mouhid!MouHid_StartRead+d1 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff2800923fdd8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88000edcfc0, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
 fffff2800923fdd8 

CURRENT_IRQL:  2

FAULTING_IP: 
Wdf01000!FxRequest::_CreateForPackage+18c
fffff880`00edcfc0 00740545        add     byte ptr [rbp+rax+45h],dh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  hl2.exe

TRAP_FRAME:  fffff8000444e240 -- (.trap 0xfffff8000444e240)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004df1903 rbx=0000000000000000 rcx=fffffa8004e4ac10
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000edcfc0 rsp=fffff8000444e3d0 rbp=fffff8000444e490
 r8=fffffa8004e4afb0  r9=fffffa8004e6de70 r10=fffffa8004e4ac10
r11=fffff88000f35260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Wdf01000!FxRequest::_CreateForPackage+0x18c:
fffff880`00edcfc0 00740545        add     byte ptr [rbp+rax+45h],dh ss:fffff280`0923fdd8=??
Resetting default scope

MISALIGNED_IP: 
Wdf01000!FxRequest::_CreateForPackage+18c
fffff880`00edcfc0 00740545        add     byte ptr [rbp+rax+45h],dh

LAST_CONTROL_TRANSFER:  from fffff80002e94229 to fffff80002e94c80

STACK_TEXT:  
fffff800`0444e0f8 fffff800`02e94229 : 00000000`0000000a fffff280`0923fdd8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`0444e100 fffff800`02e92ea0 : fffffa80`05746ce0 fffff800`02e75590 fffffa80`04e6dfc0 fffffa80`04df19f0 : nt!KiBugCheckDispatch+0x69
fffff800`0444e240 fffff880`00edcfc0 : fffffa80`04e4afb0 fffff800`0444e490 fffffa80`051131a0 fffffa80`04e4ac10 : nt!KiPageFault+0x260
fffff800`0444e3d0 fffff880`00ef93a4 : fffffa80`04e4afb0 fffffa80`04e4ec50 fffffa80`04e4ac10 fffffa80`04e56c90 : Wdf01000!FxRequest::_CreateForPackage+0x18c
fffff800`0444e410 fffff880`00ee3245 : 00000000`00000000 00000000`00000000 fffffa80`04e4ac10 fffffa80`04df18a0 : Wdf01000!FxPkgIo::Dispatch+0x1c8
fffff800`0444e490 fffff880`08259e19 : 00000000`00000000 fffffa80`04df18a0 fffffa80`04df18a0 fffffa80`04e4ea10 : Wdf01000!FxDevice::Dispatch+0xa9
fffff800`0444e4c0 fffff880`08259cd1 : 00000000`00000000 00000000`00000800 fffffa80`04df18a0 fffff800`0444e5a0 : mouhid!MouHid_StartRead+0xd1
fffff800`0444e510 fffff800`02e986c1 : fffffa80`04e4afb3 00000000`00000000 00000000`00000001 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x6f5
fffff800`0444e590 fffff880`00edda52 : 00000000`00000000 fffffa80`04e4ec00 00000000`00000001 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`0444e680 fffff880`00ece13e : fffffa80`04e4ac10 fffffa80`00000001 00000000`00000000 fffffa80`04e4ac10 : Wdf01000!FxRequest::CompleteInternal+0x646
fffff800`0444e730 fffff880`0824d459 : fffffa80`05113510 fffffa80`0566fd20 fffffa80`0566fd20 00000000`00000000 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa
fffff800`0444e7a0 fffffa80`05113510 : fffffa80`0566fd20 fffffa80`0566fd20 00000000`00000000 fffff800`0444e7f0 : LHidFilt+0x9459
fffff800`0444e7a8 fffffa80`0566fd20 : fffffa80`0566fd20 00000000`00000000 fffff800`0444e7f0 00000000`0000000f : 0xfffffa80`05113510
fffff800`0444e7b0 fffffa80`0566fd20 : 00000000`00000000 fffff800`0444e7f0 00000000`0000000f 00000000`00000000 : 0xfffffa80`0566fd20
fffff800`0444e7b8 00000000`00000000 : fffff800`0444e7f0 00000000`0000000f 00000000`00000000 ffffdaf2`21d3a777 : 0xfffffa80`0566fd20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mouhid!MouHid_StartRead+d1
fffff880`08259e19 488d8f98000000  lea     rcx,[rdi+98h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  mouhid!MouHid_StartRead+d1

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

The above crash indicates a problem with your mouse. Install the latest driver for it; your driver appears to be corrupted.

Thanks so much for your help! Ill try your suggestions and report back.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\harblhat\Minidump\042812-19640-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e68000 PsLoadedModuleList = 0xfffff800`030ac650
Debug session time: Sat Apr 28 16:54:47.408 2012 (UTC - 6:00)
System Uptime: 0 days 21:24:18.703
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88003e4aae0, 0, 0, fffff8800740862c}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessIsrCompletedPacket+1ac )

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

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

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88003e4aae0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800740862c

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


CONTEXT:  fffff88003e4aae0 -- (.cxr 0xfffff88003e4aae0)
rax=fffff88007eefa00 rbx=fffffa800540f8f0 rcx=fffffa8004271110
rdx=fffffa8006126610 rsi=fffffa800540e000 rdi=0000000000000000
rip=fffff8800740862c rsp=fffff88003e4b4c0 rbp=fffffa8005239410
 r8=0000000000000000  r9=00000000003c59c0 r10=fffff88000000001
r11=00000046f5f87601 r12=000000000013554a r13=fffffa8004271110
r14=000000000000000a r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VidSchiProcessIsrCompletedPacket+0x1ac:
fffff880`0740862c f083863c0a0000ff lock add dword ptr [rsi+0A3Ch],0FFFFFFFFh ds:002b:fffffa80`0540ea3c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  Crysis2.exe

CURRENT_IRQL:  b

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800740862c

STACK_TEXT:  
fffff880`03e4b4c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x1ac


FOLLOWUP_IP: 
dxgmms1!VidSchiProcessIsrCompletedPacket+1ac
fffff880`0740862c f083863c0a0000ff lock add dword ptr [rsi+0A3Ch],0FFFFFFFFh

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchiProcessIsrCompletedPacket+1ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88003e4aae0 ; kb

FAILURE_BUCKET_ID:  X64_0x3D_dxgmms1!VidSchiProcessIsrCompletedPacket+1ac

BUCKET_ID:  X64_0x3D_dxgmms1!VidSchiProcessIsrCompletedPacket+1ac

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

The above crash implicates DirectX/your graphics card as the culprit.

• Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details 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 drivers you want 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. Click Start Menu
       2. Right Click My Computer/Computer
       3. Click Manage
       4. Click Device Manager from the list on the left
       5. Expand Display adapters
       6. 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
          
          
          Alternatively:
          
          1. Login as an adminstrative user
          2. Click Start Menu
          3. Click Control Panel
          4. Click Hardware and Sound
          5. Click Device Manager (the last link under Devices and Printers)
          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
     • Restart your computer after uninstalling drivers for all display cards
     • Install the driver you selected for the display cards once Windows starts

In addition to the above, please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Thanks for the fast reply! Ive attached the msinfo file.

Does the ntoskrnl.exe file have no bearing on these crashes at all?

ntoskrnl.exe is one of the main Windows processes and often pops up with crashes even though it is not to blame. It is usually blamed by other blue screen analysis tools because it was the primary process running at the time of the crash. It can show up in the blue screen itself for the same reason. If ntoskrnl.exe were truly the cause of a crash, you actually would not be getting a crash but Windows would just not function at all. That is why we use WinDbg because it throws less false positives during analysis than other software might.


Taking a look at your motherboard support site and your current BIOS version, I see there are a few BIOS updates since your version. I am a little concerned about whether that board will work with the SSD you have installed since the latest BIOS is from 2009 which was before SSDs became common. We usually do not recommend using an SSD with BIOS versions older than 2011... That being said, you could contact ASUS and see what their take is on it.

I would recommend flashing your BIOS to the latest, non-beta version. Your version is actually a beta version, and that may be causing some conflicts, as well. ASUS - Motherboards- ASUS Maximus Formula