BSOD when playing WOW mostly

Hello,

I have been having the BSOD alot lately and it has been giving different messages.

page file error in nonpaged area
Driver IRQL
Hardware error
System Service Exception
etc

I decided to do a full fresh install of Windows and all the drivers (making sure they are up-to-date).

I have only had 2 BSOD since doing the fresh install (yesterday) but had the Pagefile error and alo Driver IRQL come up since then.

I just want to get to the bottom of it and try to get it fixed as when I play World of Warcraft it seems to happen the most.

I have stress tested my Ram, CPU and Graphics card and all passed without errors. I have ran Checkdisk and it came back Ok.

My Operating system is Windows 7 Home Premium 64bit Retail.
All other details can be found on my profile about my System spec.

I enclose the reports to help you diagnose this issue.

Please help. Thank you!

Sorry I had the Performance and maintenance thread open to read and also the Crashes and Debugging page and posted this in the wrong section. Please could someone move it for me? Thanking you in advance! :)

Antivirus Software:

Code:

avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1748	8	200	1380	03/03/2012 20:57	7.0.1407.0	43.72 KB (44,768 bytes)	03/03/2012 04:22
avastui.exe	c:\program files\avast software\avast\avastui.exe	3564	8	200	1380	03/03/2012 20:57	7.0.1407.0	3.84 MB (4,031,368 bytes)	03/03/2012 04:22

Possible out of date drivers:

Code:

JmtFltr	fffff880`075bf000	fffff880`075ca580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e		JmtFltr.sys
vhidmini	fffff880`0555b000	fffff880`0555e680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys

JmtFltr
vhidmini.sys
These are probably not related to the crashes, but still a good idea to try to update if you can.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Sywade\Windows_NT6_BSOD_jcgriff2\030312-28111-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`03254e70
Debug session time: Sat Mar  3 13:55:44.800 2012 (UTC - 7:00)
System Uptime: 0 days 2:23:24.719
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800515e9bf, fffff880067f7938, fffff880067f71a0}

Probably caused by : hardware ( dxgmms1!VidSchiCheckGPUTimeout+7b )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800515e9bf, The address that the exception occurred at
Arg3: fffff880067f7938, Exception Record Address
Arg4: fffff880067f71a0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VidSchiCheckGPUTimeout+7b
fffff880`0515e9bf 85a500000048    test    dword ptr [rbp+48000000h],esp

EXCEPTION_RECORD:  fffff880067f7938 -- (.exr 0xfffff880067f7938)
ExceptionAddress: fffff8800515e9bf (dxgmms1!VidSchiCheckGPUTimeout+0x000000000000007b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000048000000
Attempt to read from address 0000000048000000

CONTEXT:  fffff880067f71a0 -- (.cxr 0xfffff880067f71a0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8009717410
rdx=fffff880067f7c00 rsi=fffffa800968d000 rdi=fffffa8009717410
rip=fffff8800515e9bf rsp=fffff880067f7b70 rbp=0000000000000000
 r8=fffff880067f7bf8  r9=0000000000000000 r10=0000000000018fb6
r11=fffff880067f7bd0 r12=fffff880067f7c00 r13=fffffa8009717500
r14=fffffa8009717410 r15=fffff880067f7bf8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
dxgmms1!VidSchiCheckGPUTimeout+0x7b:
fffff880`0515e9bf 85a500000048    test    dword ptr [rbp+48000000h],esp ss:0018:00000000`48000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000048000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bf0e0
 0000000048000000 

FOLLOWUP_IP: 
dxgmms1!VidSchiCheckGPUTimeout+7b
fffff880`0515e9bf 85a500000048    test    dword ptr [rbp+48000000h],esp

BUGCHECK_STR:  0x7E

MISALIGNED_IP: 
dxgmms1!VidSchiCheckGPUTimeout+7b
fffff880`0515e9bf 85a500000048    test    dword ptr [rbp+48000000h],esp

LAST_CONTROL_TRANSFER:  from fffff8800515eb59 to fffff8800515e9bf

STACK_TEXT:  
fffff880`067f7b70 fffff880`0515eb59 : fffffa80`09717d60 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiCheckGPUTimeout+0x7b
fffff880`067f7bc0 fffff880`051302d5 : fffffa80`09717410 fffffa80`09717410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x55
fffff880`067f7bf0 fffff880`0515ce7a : 00000000`00000000 fffffa80`076fb230 00000000`00000080 fffffa80`09717410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`067f7d00 fffff800`033276fa : 00000000`05766abf fffffa80`09684b60 fffffa80`069ab9e0 fffffa80`09684b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`067f7d40 fffff800`03065b46 : fffff880`02ea4180 fffffa80`09684b60 fffff880`02eaf040 fffff880`012182b4 : nt!PspSystemThreadStartup+0x5a
fffff880`067f7d80 00000000`00000000 : fffff880`067f8000 fffff880`067f2000 fffff880`067f7690 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchiCheckGPUTimeout+7b

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880067f71a0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Sywade\Windows_NT6_BSOD_jcgriff2\030312-28953-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`0324ce70
Debug session time: Sat Mar  3 11:31:33.874 2012 (UTC - 7:00)
System Uptime: 0 days 3:09:03.169
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8804b2c7590, 0, fffff8000307e839, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+1e )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8804b2c7590, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000307e839, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b70e0
 fffff8804b2c7590 

FAULTING_IP: 
nt!KiSystemServiceExit+1e
fffff800`0307e839 f685f000000001  test    byte ptr [rbp+0F0h],1

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800aa46a90 -- (.trap 0xfffff8800aa46a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000307e839 rsp=fffff8800aa46c20 rbp=fffff8800aa46ca0
 r8=fffffa800aa540e8  r9=0000000000000000 r10=ffffffffffffffef
r11=fffffa800aa18b60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiSystemServiceExit+0x1e:
fffff800`0307e839 f685f000000001  test    byte ptr [rbp+0F0h],1 ss:0018:fffff880`0aa46d90=33
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030fe7a1 to fffff8000307f5c0

STACK_TEXT:  
fffff880`0aa46928 fffff800`030fe7a1 : 00000000`00000050 fffff880`4b2c7590 00000000`00000000 fffff880`0aa46a90 : nt!KeBugCheckEx
fffff880`0aa46930 fffff800`0307d6ae : 00000000`00000000 00000000`05a60749 0000000b`00000000 fffff880`02ea4180 : nt! ?? ::FNODOBFM::`string'+0x40d4b
fffff880`0aa46a90 fffff800`0307e839 : fffffa80`0aa18b60 00000000`0000013c ffffffff`ffffd8f0 fffffa80`0abd2220 : nt!KiPageFault+0x16e
fffff880`0aa46c20 00000000`74d12dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x1e
00000000`04bdf098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74d12dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+1e
fffff800`0307e839 f685f000000001  test    byte ptr [rbp+0F0h],1

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiSystemServiceExit+1e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aa44

FAILURE_BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+1e

BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+1e

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

1. Points to your DirectX/graphics card/graphics card driver. Other possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
2. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.

• If you are overclocking any hardware, please stop.
  
  
• 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 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
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
  
• 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. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Hi,

Thanks for looking into this for me. I have downloaded the driver for JmtFltr but I cant find a download for the other you mentioned.

I have re-installed DirectX and my Videocard driver.

My Motherboard came to me as an overclocked bundle when I bought it online. They overclocked it with the CPU, Fan, Motherboard and Ram. It was then shipped to me completed and I inserted the board into my new case and added my hard drive and Video card etc to complete the system.

I have already run Furmark and Prime95 they came up ok no errors when I left it on over night. I havent done the Memtest86+ though. So would you recommend doing them all over again, even though I have already done it or shall I skip that step?

Thank you.

Did you monitor the temperatures during those tests? I might recommend running them again if you have not monitored temperatures.

More than likely, temperatures are okay if you were able to run overnight.

PC has crashed a fw more times with the BSOD, so I have uploaded them for you to look over.

I will continue to try the stress tests as I didnt run the temp monitor when I did it before. Also I'll try the Mem86+ test when I can and report back.

Enclosed.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Sywade\Windows_NT6_BSOD_jcgriff2\030412-29796-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03288e70
Debug session time: Sun Mar  4 01:54:01.458 2012 (UTC - 7:00)
System Uptime: 0 days 2:51:44.377
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6638353330336633
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ecca98 -- (.exr 0xfffff88002ecca98)
ExceptionAddress: fffff800030c69be (nt!KiRetireDpcList+0x00000000000000de)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff88002eccb40 -- (.trap 0xfffff88002eccb40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000002ea4180 rbx=0000000000000000 rcx=0000000000802009
rdx=00000000178bfbff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030c69be rsp=fffff88002ecccd0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=0000000000025260
r11=00000000002f6b00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiRetireDpcList+0xde:
fffff800`030c69be f7f9            idiv    eax,ecx
Resetting default scope

MISALIGNED_IP: 
nt!KiRetireDpcList+de
fffff800`030c69be f7f9            idiv    eax,ecx

LAST_CONTROL_TRANSFER:  from fffff800030b32ee to fffff800030bb590

STACK_TEXT:  
fffff880`02ecbb88 fffff800`030b32ee : fffffa80`0ac3d030 fffffa80`08eee600 fffff880`02ecc300 fffff800`030e8524 : nt!KeBugCheck
fffff880`02ecbb90 fffff800`030e12dd : fffff800`032c9b7c fffff800`03203e68 fffff800`0304b000 fffff880`02ecca98 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ecbbc0 fffff800`030e8950 : fffff800`0320ab0c fffff880`02ecbc38 fffff880`02ecca98 fffff800`0304b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ecbbf0 fffff800`030f58cf : fffff880`02ecca98 fffff880`02ecc300 fffff880`00000000 00000000`00100fa0 : nt!RtlDispatchException+0x410
fffff880`02ecc2d0 fffff800`030bac02 : fffff880`02ecca98 00000000`05060800 fffff880`02eccb40 fffff880`02eaf040 : nt!KiDispatchException+0x16f
fffff880`02ecc960 fffff800`030b8d5f : fffff880`02eccb40 00000000`00000002 00000007`f76fac00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02eccb40 fffff800`030c69be : 00000008`ec49ae9c 00000008`ec49aeef 00000008`ec49ae9c 00000000`00000034 : nt!KiInvalidOpcodeFault+0x11f
fffff880`02ecccd0 fffff800`030c3d8a : fffff880`02ea4180 fffff880`02eaf040 00000000`00000000 fffff880`054badb0 : nt!KiRetireDpcList+0xde
fffff880`02eccd80 00000000`00000000 : fffff880`02ecd000 fffff880`02ec7000 fffff880`02eccd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`030b32ee 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

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
---------

Loading Dump File [D:\Kingston\BSODDmpFiles\Sywade\Windows_NT6_BSOD_jcgriff2\030412-32666-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03016000 PsLoadedModuleList = 0xfffff800`03253e70
Debug session time: Sat Mar  3 22:51:22.000 2012 (UTC - 7:00)
System Uptime: 0 days 1:27:06.920
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {486c3b48a, 2, 1, fffff880075c1fb1}

Unable to load image \SystemRoot\system32\DRIVERS\ks.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
Probably caused by : hardware ( usbaudio!UsbHwGetPerfCounterInHNSecUnits+d )

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

4: 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: 0000000486c3b48a, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880075c1fb1, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032be0e0
 0000000486c3b48a 

CURRENT_IRQL:  2

FAULTING_IP: 
usbaudio!UsbHwGetPerfCounterInHNSecUnits+d
fffff880`075c1fb1 0000            add     byte ptr [rax],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  audiodg.exe

TRAP_FRAME:  fffff88003be01f0 -- (.trap 0xfffff88003be01f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000486c3b48a rbx=0000000000000000 rcx=0000000000000001
rdx=0000121b00000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880075c1fb1 rsp=fffff88003be0380 rbp=fffffa800aad8840
 r8=000000004f444600  r9=000000000038bf79 r10=0000000000000048
r11=00000000004f77eb r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbaudio!UsbHwGetPerfCounterInHNSecUnits+0xd:
fffff880`075c1fb1 0000            add     byte ptr [rax],al ds:71a0:00000004`86c3b48a=??
Resetting default scope

MISALIGNED_IP: 
usbaudio!UsbHwGetPerfCounterInHNSecUnits+d
fffff880`075c1fb1 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff80003085b29 to fffff800030865c0

STACK_TEXT:  
fffff880`03be00a8 fffff800`03085b29 : 00000000`0000000a 00000004`86c3b48a 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03be00b0 fffff800`030847a0 : 00000000`00000000 00000000`00000000 00000000`00000002 fffffa80`0aad8840 : nt!KiBugCheckDispatch+0x69
fffff880`03be01f0 fffff880`075c1fb1 : 00000000`0038bf79 00000000`00000000 00000000`004f77eb 0000000c`2bc4a861 : nt!KiPageFault+0x260
fffff880`03be0380 fffff880`075c206e : 00000000`0038bf79 00000000`00000000 00000000`0000176f 00000000`00000000 : usbaudio!UsbHwGetPerfCounterInHNSecUnits+0xd
fffff880`03be03b0 fffff880`075c22ca : 00000000`004f77eb fffff880`03be04a0 fffff880`03be04b0 fffff880`004f77eb : usbaudio!UsbHwFrameCountTimestamp+0x76
fffff880`03be0430 fffff880`075c26f0 : fffffa80`00000000 fffff880`03be04d0 fffffa80`0b0128a0 fffffa80`0aad8880 : usbaudio!USBHwGetClockRatio+0x186
fffff880`03be04a0 fffff880`075d1247 : fffffa80`0b012800 00000000`00000000 00000000`c000000d fffff880`05633500 : usbaudio!USBType1RenderBytePosition+0x70
fffff880`03be0520 fffff880`056357ff : fffffa80`07ac51c0 fffffa80`0b0128a0 fffffa80`07ac51c0 fffff880`00000000 : usbaudio!PropertyGetAudioPositionEx+0x4b
fffff880`03be0560 fffffa80`07ac51c0 : fffffa80`0b0128a0 fffffa80`07ac51c0 fffff880`00000000 00000048`00000028 : ks+0x1a7ff
fffff880`03be0568 fffffa80`0b0128a0 : fffffa80`07ac51c0 fffff880`00000000 00000048`00000028 00000000`00000018 : 0xfffffa80`07ac51c0
fffff880`03be0570 fffffa80`07ac51c0 : fffff880`00000000 00000048`00000028 00000000`00000018 fffffa80`0b0128a0 : 0xfffffa80`0b0128a0
fffff880`03be0578 fffff880`00000000 : 00000048`00000028 00000000`00000018 fffffa80`0b0128a0 00000000`00000000 : 0xfffffa80`07ac51c0
fffff880`03be0580 00000048`00000028 : 00000000`00000018 fffffa80`0b0128a0 00000000`00000000 fffff880`0562b590 : 0xfffff880`00000000
fffff880`03be0588 00000000`00000018 : fffffa80`0b0128a0 00000000`00000000 fffff880`0562b590 fffff880`0562e110 : 0x48`00000028
fffff880`03be0590 fffffa80`0b0128a0 : 00000000`00000000 fffff880`0562b590 fffff880`0562e110 00000000`00000001 : 0x18
fffff880`03be0598 00000000`00000000 : fffff880`0562b590 fffff880`0562e110 00000000`00000001 fffffa80`07ac51c0 : 0xfffffa80`0b0128a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbaudio!UsbHwGetPerfCounterInHNSecUnits+d
fffff880`075c1fb1 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbaudio!UsbHwGetPerfCounterInHNSecUnits+d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_usbaudio.sys

BUCKET_ID:  X64_IP_MISALIGNED_usbaudio.sys

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

1. This crash is typically caused by Drivers... Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates...
   Thanks to JMH for helping with my understanding of this crash.
2. This is usually caused by antivirus software/firewall software. It can also be caused by Memory problems...
3. Caused by a USB device.

Continue through the steps before and check memory. Make sure to run all memory tests (both Memtest86+ and the graphics card memory test) for at least seven passes.


Additionally, with the above information:

• Install all Windows updates. I notice Service Pack 1 is missing. Update to Service Pack 1 (SP1)
  
  Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]
  
  Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]
  
  Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center
  
  Service Pack 1 Download site
  Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
  
  
• Avast is known to cause crashes on some systems. Uninstall Avast and switch to Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.
  
  You can also check out the Good and Free system security combination.
  
  
• Run through the steps for USB Driver - General Fix for Problems to try to resolve the USB problems. What USB devices are you currently using?
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

I ran the Memtest86+ overnight and it came up no errors and all passes. I have been on WOW all night since 7pm and not had 1 bluescreen.......hmmmmmm

Seems running the Memtest86+ fixed it. I wont hold my breath but so far its going well.
Am I jumping the gun or should I see how things goes and maybe do something else to try and get to the bottom of this?

:)

You are likely jumping the gun, unfortunately.

Memtest86+ will not fix problems; it is only a diagnostic utility.

See how things go for a day or two and post back.

Still not had another BSOD so not sure what happened. Since running the Memtest86+ (Which as you said doesnt fix anything or diagnos) it hasnt done it. Strange eh? Thanks for your help though :)

So shall I mark as solved? Cos it is but we dont know how it was solved