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: Bluescreen Crashes/World of Warcraft

23 Jan 2011   #11
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by XPhile2012 View Post
SteelSeries World of Warcraft: Cataclysm MMO Gaming Mouse - 15-btn Mouse - Wired - USB

SteelSeries – World of Warcraft® MMO Gaming Mouse
Ah, thanks for letting me know. I just wanted to make sure it was not a malware driver.

Quote   Quote: Originally Posted by XPhile2012 View Post
Installing Microsoft Security Essential now.
Very good. Keep us updated.


My System SpecsSystem Spec
.
23 Jan 2011   #12
XPhile2012

Windows 7 64bit
 
 

G.SKILL Ripjaws Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM is the memory package I purchased from Newegg.com. Came as one set of 4 memory chips. Was said to be matching.

also, correction on the mouse. New link is listed below:

http://steelseries.com/products/game...o-gaming-mouse

I don't think it would cause a system crash though, would it?
My System SpecsSystem Spec
23 Jan 2011   #13
CarlTR6

Windows 7 Ultimate 32 bit
 
 

I don't suspect the mouse; the dump did not indicate it was involved. I just saw a driver I did not recognize and I wanted to be sure it was not malware. And I could not find anything on it through Google. Malware can definitely cause BSOD's.
My System SpecsSystem Spec
.

24 Jan 2011   #14
XPhile2012

Windows 7 64bit
 
 

PC is virus/malware free.
Are you thinking it's a problem with the RAM I purchased?

BSOD again this morning:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002ADAC7F
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Attaching report again.
Again, thank you so much for your help with this issue.
My System SpecsSystem Spec
24 Jan 2011   #15
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Actually you have two dumps from today. The earlier one is bugcheck 1E and blames ntkrnlmp.exe. The later on is bugcheck 3B and blames hardware and implicates dxgmms1.sys, Direct X. Both indicate memory corruption.
Quote:
Are you thinking it's a problem with the RAM I purchased?
I cannot tell from the dumps; but that is a possibility. Have you run Memtest yet? You definitely need to test your RAM. If your Memtest shows no errors, I suggest you test your graphics card with Furmark following the instructions in this tutorial: Video Card - Stress Test with Furmark. Post back with your results. But run Memtest first.

Are you running any kind of a third party security program such as a banking ID security program, a Wi-Fi security program, a keylogger security program, a gaming security program, etc?

Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5d000 PsLoadedModuleList = 0xfffff800`02c9ae50
Debug session time: Mon Jan 24 13:34:18.316 2011 (GMT-5)
System Uptime: 0 days 0:45:35.267
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002adac7f, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSpinLock+2f )

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002adac7f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

FAULTING_IP: 
nt!KeReleaseSpinLock+2f
fffff800`02adac7f c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d050e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880030b7af8 -- (.exr 0xfffff880030b7af8)
ExceptionAddress: fffff80002adac7f (nt!KeReleaseSpinLock+0x000000000000002f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000008
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880030b7ba0 -- (.trap 0xfffff880030b7ba0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800e6da3a0
rdx=fffffa800e6da302 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002adac7f rsp=fffff880030b7d32 rbp=0000000070616d49
 r8=fffffa800e426c00  r9=0000000000000000 r10=fffffa800e6da100
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeReleaseSpinLock+0x2f:
fffff800`02adac7f c3              ret
Resetting default scope

UNALIGNED_STACK_POINTER:  fffff880030b7d32

LAST_CONTROL_TRANSFER:  from fffff80002b07a39 to fffff80002acd740

STACK_TEXT:  
fffff880`030b7328 fffff800`02b07a39 : 00000000`0000001e ffffffff`c0000005 fffff800`02adac7f 00000000`00000000 : nt!KeBugCheckEx
fffff880`030b7330 fffff800`02accd82 : fffff880`030b7af8 a050ffff`fa800d34 fffff880`030b7ba0 fffffa80`0e6db5f8 : nt!KiDispatchException+0x1b9
fffff880`030b79c0 fffff800`02acb68a : fffffa80`0ec51e90 fffffa80`0ec59801 fffffa80`0ec51ea0 fffffa80`0ec59801 : nt!KiExceptionDispatch+0xc2
fffff880`030b7ba0 fffff800`02adac7f : 0c20ffff`fa800e6d 7375ffff`fa800d35 36f30000`00007062 79a0ffff`f8800481 : nt!KiGeneralProtectionFault+0x10a
fffff880`030b7d32 0c20ffff`fa800e6d : 7375ffff`fa800d35 36f30000`00007062 79a0ffff`f8800481 0c20ffff`fa800ca8 : nt!KeReleaseSpinLock+0x2f
fffff880`030b7d3a 7375ffff`fa800d35 : 36f30000`00007062 79a0ffff`f8800481 0c20ffff`fa800ca8 7375ffff`fa800d35 : 0xc20ffff`fa800e6d
fffff880`030b7d42 36f30000`00007062 : 79a0ffff`f8800481 0c20ffff`fa800ca8 7375ffff`fa800d35 03edffff`fa807062 : 0x7375ffff`fa800d35
fffff880`030b7d4a 79a0ffff`f8800481 : 0c20ffff`fa800ca8 7375ffff`fa800d35 03edffff`fa807062 000f0000`00000000 : 0x36f30000`00007062
fffff880`030b7d52 0c20ffff`fa800ca8 : 7375ffff`fa800d35 03edffff`fa807062 000f0000`00000000 0000ffff`f8800000 : 0x79a0ffff`f8800481
fffff880`030b7d5a 7375ffff`fa800d35 : 03edffff`fa807062 000f0000`00000000 0000ffff`f8800000 8e200000`00000000 : 0xc20ffff`fa800ca8
fffff880`030b7d62 03edffff`fa807062 : 000f0000`00000000 0000ffff`f8800000 8e200000`00000000 ff02ffff`fa800d34 : 0x7375ffff`fa800d35
fffff880`030b7d6a 000f0000`00000000 : 0000ffff`f8800000 8e200000`00000000 ff02ffff`fa800d34 a1a00000`0000ffff : 0x3edffff`fa807062
fffff880`030b7d72 0000ffff`f8800000 : 8e200000`00000000 ff02ffff`fa800d34 a1a00000`0000ffff a1a0ffff`fa800e6d : 0xf0000`00000000
fffff880`030b7d7a 8e200000`00000000 : ff02ffff`fa800d34 a1a00000`0000ffff a1a0ffff`fa800e6d a050ffff`fa800e6d : 0xffff`f8800000
fffff880`030b7d82 ff02ffff`fa800d34 : a1a00000`0000ffff a1a0ffff`fa800e6d a050ffff`fa800e6d 5dd7ffff`fa800e6d : 0x8e200000`00000000
fffff880`030b7d8a a1a00000`0000ffff : a1a0ffff`fa800e6d a050ffff`fa800e6d 5dd7ffff`fa800e6d b5f8ffff`f8800481 : 0xff02ffff`fa800d34
fffff880`030b7d92 a1a0ffff`fa800e6d : a050ffff`fa800e6d 5dd7ffff`fa800e6d b5f8ffff`f8800481 154affff`fa800e6d : 0xa1a00000`0000ffff
fffff880`030b7d9a a050ffff`fa800e6d : 5dd7ffff`fa800e6d b5f8ffff`f8800481 154affff`fa800e6d 6c20ffff`f8800481 : 0xa1a0ffff`fa800e6d
fffff880`030b7da2 5dd7ffff`fa800e6d : b5f8ffff`f8800481 154affff`fa800e6d 6c20ffff`f8800481 a050ffff`fa800e42 : 0xa050ffff`fa800e6d
fffff880`030b7daa b5f8ffff`f8800481 : 154affff`fa800e6d 6c20ffff`f8800481 a050ffff`fa800e42 ffffffff`fa800e6d : 0x5dd7ffff`fa800e6d
fffff880`030b7db2 154affff`fa800e6d : 6c20ffff`f8800481 a050ffff`fa800e42 ffffffff`fa800e6d a1a00000`0000ffff : 0xb5f8ffff`f8800481
fffff880`030b7dba 6c20ffff`f8800481 : a050ffff`fa800e42 ffffffff`fa800e6d a1a00000`0000ffff 9d20ffff`fa800e6d : 0x154affff`fa800e6d
fffff880`030b7dc2 a050ffff`fa800e42 : ffffffff`fa800e6d a1a00000`0000ffff 9d20ffff`fa800e6d 4378ffff`fa800ec4 : 0x6c20ffff`f8800481
fffff880`030b7dca ffffffff`fa800e6d : a1a00000`0000ffff 9d20ffff`fa800e6d 4378ffff`fa800ec4 a050ffff`f8800481 : 0xa050ffff`fa800e42
fffff880`030b7dd2 a1a00000`0000ffff : 9d20ffff`fa800e6d 4378ffff`fa800ec4 a050ffff`f8800481 0000ffff`fa800e6d : 0xffffffff`fa800e6d
fffff880`030b7dda 9d20ffff`fa800e6d : 4378ffff`fa800ec4 a050ffff`f8800481 0000ffff`fa800e6d ad200000`00000000 : 0xa1a00000`0000ffff
fffff880`030b7de2 4378ffff`fa800ec4 : a050ffff`f8800481 0000ffff`fa800e6d ad200000`00000000 6c20ffff`fa800e6d : 0x9d20ffff`fa800e6d
fffff880`030b7dea a050ffff`f8800481 : 0000ffff`fa800e6d ad200000`00000000 6c20ffff`fa800e6d ae00ffff`fa800e42 : 0x4378ffff`fa800ec4
fffff880`030b7df2 0000ffff`fa800e6d : ad200000`00000000 6c20ffff`fa800e6d ae00ffff`fa800e42 ff02ffff`fa800e6d : 0xa050ffff`f8800481
fffff880`030b7dfa ad200000`00000000 : 6c20ffff`fa800e6d ae00ffff`fa800e42 ff02ffff`fa800e6d 00000000`0000ffff : 0xffff`fa800e6d
fffff880`030b7e02 6c20ffff`fa800e6d : ae00ffff`fa800e42 ff02ffff`fa800e6d 00000000`0000ffff ffff0000`00000000 : 0xad200000`00000000
fffff880`030b7e0a ae00ffff`fa800e42 : ff02ffff`fa800e6d 00000000`0000ffff ffff0000`00000000 ffff0000`0000ffff : 0x6c20ffff`fa800e6d
fffff880`030b7e12 ff02ffff`fa800e6d : 00000000`0000ffff ffff0000`00000000 ffff0000`0000ffff 00000000`0000ffff : 0xae00ffff`fa800e42
fffff880`030b7e1a 00000000`0000ffff : ffff0000`00000000 ffff0000`0000ffff 00000000`0000ffff a1a00000`00000000 : 0xff02ffff`fa800e6d
fffff880`030b7e22 ffff0000`00000000 : ffff0000`0000ffff 00000000`0000ffff a1a00000`00000000 ff02ffff`fa800e6d : 0xffff
fffff880`030b7e2a ffff0000`0000ffff : 00000000`0000ffff a1a00000`00000000 ff02ffff`fa800e6d ad200000`0000ffff : 0xffff0000`00000000
fffff880`030b7e32 00000000`0000ffff : a1a00000`00000000 ff02ffff`fa800e6d ad200000`0000ffff 6c20ffff`fa800e6d : 0xffff0000`0000ffff
fffff880`030b7e3a a1a00000`00000000 : ff02ffff`fa800e6d ad200000`0000ffff 6c20ffff`fa800e6d 9d20ffff`fa800e42 : 0xffff
fffff880`030b7e42 ff02ffff`fa800e6d : ad200000`0000ffff 6c20ffff`fa800e6d 9d20ffff`fa800e42 1e86ffff`fa800ec4 : 0xa1a00000`00000000
fffff880`030b7e4a ad200000`0000ffff : 6c20ffff`fa800e6d 9d20ffff`fa800e42 1e86ffff`fa800ec4 a050ffff`f8800481 : 0xff02ffff`fa800e6d
fffff880`030b7e52 6c20ffff`fa800e6d : 9d20ffff`fa800e42 1e86ffff`fa800ec4 a050ffff`f8800481 a050ffff`fa800e6d : 0xad200000`0000ffff
fffff880`030b7e5a 9d20ffff`fa800e42 : 1e86ffff`fa800ec4 a050ffff`f8800481 a050ffff`fa800e6d 1920ffff`fa800e6d : 0x6c20ffff`fa800e6d
fffff880`030b7e62 1e86ffff`fa800ec4 : a050ffff`f8800481 a050ffff`fa800e6d 1920ffff`fa800e6d a1a0ffff`fa800e6c : 0x9d20ffff`fa800e42
fffff880`030b7e6a a050ffff`f8800481 : a050ffff`fa800e6d 1920ffff`fa800e6d a1a0ffff`fa800e6c 0002ffff`fa800e6d : 0x1e86ffff`fa800ec4
fffff880`030b7e72 a050ffff`fa800e6d : 1920ffff`fa800e6d a1a0ffff`fa800e6c 0002ffff`fa800e6d 25c2ffff`fa800000 : 0xa050ffff`f8800481
fffff880`030b7e7a 1920ffff`fa800e6d : a1a0ffff`fa800e6c 0002ffff`fa800e6d 25c2ffff`fa800000 2450ffff`f8800480 : 0xa050ffff`fa800e6d
fffff880`030b7e82 a1a0ffff`fa800e6c : 0002ffff`fa800e6d 25c2ffff`fa800000 2450ffff`f8800480 00220000`0000746f : 0x1920ffff`fa800e6d
fffff880`030b7e8a 0002ffff`fa800e6d : 25c2ffff`fa800000 2450ffff`f8800480 00220000`0000746f 00000000`00000000 : 0xa1a0ffff`fa800e6c
fffff880`030b7e92 25c2ffff`fa800000 : 2450ffff`f8800480 00220000`0000746f 00000000`00000000 ffff0000`00000000 : 0x2ffff`fa800e6d
fffff880`030b7e9a 2450ffff`f8800480 : 00220000`0000746f 00000000`00000000 ffff0000`00000000 ad200000`0000ffff : 0x25c2ffff`fa800000
fffff880`030b7ea2 00220000`0000746f : 00000000`00000000 ffff0000`00000000 ad200000`0000ffff 2f89ffff`fa800e6d : 0x2450ffff`f8800480
fffff880`030b7eaa 00000000`00000000 : ffff0000`00000000 ad200000`0000ffff 2f89ffff`fa800e6d a050ffff`f8800480 : 0x220000`0000746f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeReleaseSpinLock+2f
fffff800`02adac7f c3              ret

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KeReleaseSpinLock+2f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KeReleaseSpinLock+2f

BUCKET_ID:  X64_0x1E_nt!KeReleaseSpinLock+2f

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

Debug session time: Mon Jan 24 01:35:24.528 2011 (GMT-5)
System Uptime: 0 days 0:20:39.839
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff8800483a8f1, fffff88007d8e8c0, 0}

Probably caused by : hardware ( dxgmms1!VidSchiSubmitCommandPacketToQueue+129 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff8800483a8f1, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007d8e8c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
dxgmms1!VidSchiSubmitCommandPacketToQueue+129
fffff880`0483a8f1 48f6877808000002 test    byte ptr [rdi+878h],2

CONTEXT:  fffff88007d8e8c0 -- (.cxr 0xfffff88007d8e8c0)
rax=0000000000000000 rbx=fffffa800cb0e990 rcx=0000000000000000
rdx=fffffa800ce85d30 rsi=fffffa800fe8e9c0 rdi=fffffa800e4cf010
rip=fffff8800483a8f1 rsp=fffff88007d8f298 rbp=fffffa800f0eb000
 r8=fffffa800f0eb000  r9=0000000000000000 r10=000001e100000000
r11=fffff88007d8f270 r12=fffffa800e345601 r13=fffffa800e3456e0
r14=0000000000000001 r15=fffffa800e4cf010
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
dxgmms1!VidSchiSubmitCommandPacketToQueue+0x129:
fffff880`0483a8f1 48f6877808000002 test    byte ptr [rdi+878h],2 ds:002b:fffffa80`0e4cf888=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
dxgmms1!VidSchiSubmitCommandPacketToQueue+129
fffff880`0483a8f1 48f6877808000002 test    byte ptr [rdi+878h],2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800483a8f1

STACK_TEXT:  
fffff880`07d8f298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x129


FOLLOWUP_IP: 
dxgmms1!VidSchiSubmitCommandPacketToQueue+129
fffff880`0483a8f1 48f6877808000002 test    byte ptr [rdi+878h],2

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+129

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff88007d8e8c0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec
25 Jan 2011   #16
XPhile2012

Windows 7 64bit
 
 

Happened again today.
Attaching the health scan and report below. Could you please see if it is similar to the previews scans?
Also, running memtest now. Will report results in a few hours when it completes.
My System SpecsSystem Spec
26 Jan 2011   #17
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote:
Bugcheck 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

Bugcheck A, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
The first of the two dumps blame dxgmms1.sys, Windows system Direct X driver; the second blames ntkrnlmp.exe, Windows system core file. Neither is likely to be the real cause. Your perfmon reports are very similar.

Are you running any kind of a third party security program, besides Spybot and AVG, such as a banking ID security program, a Wi-Fi security program, a keylogger security program, a gaming security program, etc? I recommend that you uninstall Spybot. TeaTimer has been known to cause conflicts on Win 7 systems. Your dumps are similar to those when a third party security program is causing conflicts. Download, install, and update Malwarebytes (free). Use it as an on demand scanner. It generally runs very well with Win 7.

Completely uninstall AVG using this removal tool:
Tool (64 bit). If you are running AVG Identity Protection, remove it with this tool: Tool. AVG is a known cause of BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place. Many third party security programs conflict with Win 7 due to Win 7's own internal security coding.

Follow these three suggestions, reboot and see how your system runs. Please post back and let us know.


Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
Debug session time: Tue Jan 25 21:36:22.993 2011 (GMT-5)
System Uptime: 0 days 1:23:56.304
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff8800480af73, fffff880064b5958, fffff880064b51c0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSwitchContextWithCheck+123 )

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

4: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8800480af73, The address that the exception occurred at
Arg3: fffff880064b5958, Exception Record Address
Arg4: fffff880064b51c0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
dxgmms1!VidSchiSwitchContextWithCheck+123
fffff880`0480af73 7432            je      dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7)

EXCEPTION_RECORD:  fffff880064b5958 -- (.exr 0xfffff880064b5958)
ExceptionAddress: fffff8800480af73 (dxgmms1!VidSchiSwitchContextWithCheck+0x0000000000000123)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880064b51c0 -- (.cxr 0xfffff880064b51c0)
rax=0000000000000000 rbx=fffffa800de15090 rcx=0000000000000000
rdx=fffffa800cd99de0 rsi=fffffa800f412010 rdi=0000000000000001
rip=fffff8800480af73 rsp=fffff880064b5b90 rbp=fffffa800f461000
 r8=0000000000000002  r9=0000000000000000 r10=fffffa800f4127e0
r11=fffff880064b5b70 r12=000000000de15090 r13=fffff880064b5d00
r14=0000000000000000 r15=0000000000000001
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!VidSchiSwitchContextWithCheck+0x123:
fffff880`0480af73 7432            je      dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7) [br=1]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff8800480b193 to fffff8800480af73

FAILED_INSTRUCTION_ADDRESS: 
dxgmms1!VidSchiSwitchContextWithCheck+123
fffff880`0480af73 7432            je      dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7)

STACK_TEXT:  
fffff880`064b5b90 fffff880`0480b193 : fffffa80`0f412010 fffffa80`0de15090 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSwitchContextWithCheck+0x123
fffff880`064b5bf0 fffff880`04837e7a : 00000000`00000000 fffffa80`0de15090 00000000`00000080 fffffa80`0f412010 : dxgmms1!VidSchiScheduleCommandToRun+0xa7
fffff880`064b5d00 fffff800`02d78c06 : 00000000`04d48178 fffffa80`0f3bf060 fffffa80`0ca7c9e0 fffffa80`0f3bf060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`064b5d40 fffff800`02ab2c26 : fffff800`02c4ee80 fffffa80`0f3bf060 fffff800`02c5cc40 fffff880`01224a90 : nt!PspSystemThreadStartup+0x5a
fffff880`064b5d80 00000000`00000000 : fffff880`064b6000 fffff880`064b0000 fffff880`064b5690 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
dxgmms1!VidSchiSwitchContextWithCheck+123
fffff880`0480af73 7432            je      dxgmms1!VidSchiSwitchContextWithCheck+0x157 (fffff880`0480afa7)

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidSchiSwitchContextWithCheck+123

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff880064b51c0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_dxgmms1!VidSchiSwitchContextWithCheck+123

BUCKET_ID:  X64_0x7E_BAD_IP_dxgmms1!VidSchiSwitchContextWithCheck+123

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

Debug session time: Tue Jan 25 22:00:38.723 2011 (GMT-5)
System Uptime: 0 days 0:18:32.034
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {38802674, 2, 0, fffff80002a86d7d}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+6d )

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

4: 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: 0000000038802674, 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: fffff80002a86d7d, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb30e0
 0000000038802674 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessExpiredTimerList+6d
fffff800`02a86d7d 4885c0          test    rax,rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003046680 -- (.trap 0xfffff88003046680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800f329100
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a86d7d rsp=fffff88003046810 rbp=0000000000011673
 r8=fffff880009b4301  r9=0000000000000006 r10=0000000000000073
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiProcessExpiredTimerList+0x6d:
fffff800`02a86d7d 4885c0          test    rax,rax
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7aca9 to fffff80002a7b740

STACK_TEXT:  
fffff880`03046538 fffff800`02a7aca9 : 00000000`0000000a 00000000`38802674 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03046540 fffff800`02a79920 : 00000000`00000000 fffffa80`0f329120 fffff880`03046740 fffffa80`0e65ca30 : nt!KiBugCheckDispatch+0x69
fffff880`03046680 fffff800`02a86d7d : fffffa80`0f329120 fffffa80`0eda3478 fffffa80`0eda3478 00000000`00000102 : nt!KiPageFault+0x260
fffff880`03046810 fffff800`02a874be : 00000002`96d3086f fffff880`03046e88 00000000`00011673 fffff880`009b53e8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`03046e60 fffff800`02a86cb7 : fffff880`009b21c5 fffffa80`00011673 fffffa80`0dce3d38 00000000`00000073 : nt!KiTimerExpiration+0x1be
fffff880`03046f00 fffff800`02a81865 : 00000000`00000000 fffffa80`0f281210 00000000`00000000 fffff880`0526f588 : nt!KiRetireDpcList+0x277
fffff880`03046fb0 fffff800`02a8167c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`064fb6e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessExpiredTimerList+6d
fffff800`02a86d7d 4885c0          test    rax,rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessExpiredTimerList+6d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+6d

BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+6d

Followup: MachineOwner
---------
My System SpecsSystem Spec
28 Jan 2011   #18
XPhile2012

Windows 7 64bit
 
 

Again, thank you so much for your help and time in dealing with my problem. You are a really great guy!
I followed your instructions and have uninstalled Spybot and AVG.
My System SpecsSystem Spec
28 Jan 2011   #19
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Good job. Let us know if this helps your system.
My System SpecsSystem Spec
Reply

 Bluescreen Crashes/World of Warcraft




Thread Tools




Similar help and support threads
Thread Forum
BSOD Surfing internet after World of Warcraft crashes out.
I've been having trouble with WoW crashing out and trying to fix those errors. After one of them I got a BSOD which caused me to actually be concerned instead of just annoyed. Is Windows 7 . . . - x64 - Full retail, fresh install I have already updated all my drivers. Ran memtest86 over...
BSOD Help and Support
World of Warcraft !!
So basically I love playing world of Warcraft . And my wife and boss gets pissed off when they see me play ... Is there some way I can hide the icon from the taskbar ? What would be best if I could have a macro that will port me to the desktop and not showing any icon on the taskbar . Can someone...
Gaming
World of Warcraft
Hello. Okay, so I have these "Not Responding" just blinking in-game. The whole window doesn't shutdown or anything fancy, it's just blinking "Not Responding", and then it does and keeps doing like that. I have reinstalled the game, but still the same. The GPU is on 60C, which is normal I...
Gaming
World Of Warcraft... Oh yes I did
Who plays WoW? Character Name: Class/Race: Server: I'll go first... LviaLViaquez Gnome Mage
Gaming
World of Warcraft Fix
MY World of Warcraft makes my windows 7 Blue screen Crash and it wont start WoW i have tried Uninstalling and installing both Windows and WoW a few times
Gaming


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 09:11.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App