
Quote: Originally Posted by
flamingcherry
I uninstalled both Realtek and NVIDIA, downloaded the updates from both websites and after the restart I had another blue screen. Here are the new dumps if anyone would like to try to give me any other ideas. I appreciate all of the help, they both needed to be updated fairly badly apparently but don't seem to be the actual cause of my problem.

Well I hate to say it but WoW is still crashing your video
driver. Did you follow these when removing and re-installing? There still are 2+ year old
drivers and until they are updated we may never know what the true reason is.
You have had 5 different kinds of crashes at that point I have to start thinking hardware. I dont know if someone has had you run a memory test but you should.
Download a copy of
Memtest86 and burn the ISO to a CD using
Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using
Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Analysis
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\110810-28704-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a03000 PsLoadedModuleList = 0x82b4b810
Debug session time: Mon Nov 8 10:37:27.222 2010 (GMT-5)
System Uptime: 0 days 1:36:09.126
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {3f51a, 2, 0, 82a3fa5b}
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSignalRegisteredEvent+bc )
Followup: MachineOwner
---------
1: 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: 0003f51a, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82a3fa5b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82b6b718
Unable to read MiSystemVaType memory at 82b4b160
0003f51a
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSignalNotificationObject+18
82a3fa5b 807f1601 cmp byte ptr [edi+16h],1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Wow.exe
TRAP_FRAME: 807e6d44 -- (.trap 0xffffffff807e6d44)
ErrCode = 00000000
eax=86fe9138 ebx=0003f504 ecx=807e6e02 edx=86fe1a72 esi=86fe9140 edi=0003f504
eip=82a3fa5b esp=807e6db8 ebp=807e6dc4 iopl=0 nv up ei pl nz na po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
nt!KiSignalNotificationObject+0x18:
82a3fa5b 807f1601 cmp byte ptr [edi+16h],1 ds:0023:0003f51a=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 82a3fa5b to 82a4982b
STACK_TEXT:
807e6d44 82a3fa5b badb0d00 86fe1a72 92fa3cf5 nt!KiTrap0E+0x2cf
807e6dc4 82a6a75d 807c6120 86fe1580 86fe9100 nt!KiSignalNotificationObject+0x18
807e6de8 93960074 86fe9138 00000000 00000000 nt!KeSetEvent+0x98
807e6e18 9396625d 86fe1580 86fe9110 86fe9000 dxgmms1!VidSchiSignalRegisteredEvent+0xbc
807e6e60 93966451 86fe1580 86fe99d0 00000000 dxgmms1!VidSchiProcessDpcCompletedPacket+0x2e5
807e6e7c 9396651e 86fe1580 86dae000 86fe1580 dxgmms1!VidSchiProcessDpcDmaPacket+0xc5
807e6e94 93966832 86dae000 00000001 00000000 dxgmms1!VidSchDdiNotifyDpcWorker+0xb2
807e6eb8 938a3bf5 863be920 807e6ed8 938a3cc4 dxgmms1!VidSchDdiNotifyDpc+0x78
WARNING: Stack unwind information not available. Following frames may be wrong.
807e6ec4 938a3cc4 84fc64a0 863be920 93856698 dxgkrnl+0x1bf5
807e6ed8 92ea3bcb 863be920 93856698 00000000 dxgkrnl+0x1cc4
807e6ef4 92ea3dc3 86568000 86568000 00000000 nvlddmkm+0x81bcb
807e6f0c 92ea4330 86568000 00000000 93856698 nvlddmkm+0x81dc3
807e6f28 92e35345 807c7a00 86568070 85493dcc nvlddmkm+0x82330
807e6f3c 92e350a5 92e3531b 807e6fa4 82a6b3b5 nvlddmkm+0x13345
807e6f48 82a6b3b5 86568070 86568000 00000000 nvlddmkm+0x130a5
807e6fa4 82a6b218 807c6120 85493d48 00000000 nt!KiExecuteAllDpcs+0xf9
807e6ff4 82a6a9dc 9c803ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e6ff8 9c803ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82a6a9dc 00000000 0000001a 00d6850f bb830000 0x9c803ce4
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiSignalRegisteredEvent+bc
93960074 8b36 mov esi,dword ptr [esi]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VidSchiSignalRegisteredEvent+bc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265
FAILURE_BUCKET_ID: 0xA_dxgmms1!VidSchiSignalRegisteredEvent+bc
BUCKET_ID: 0xA_dxgmms1!VidSchiSignalRegisteredEvent+bc
Followup: MachineOwner
--------- Old drivers
Code:
VSTCNXT3.SYS 0x8ffc1000 0x000b5000 10/15/2008 19:29:13 0x48f68ad9 0x8ff0c000
VSTBS23.SYS 0x8fccf000 0x0004c000 10/15/2008 19:30:15 0x48f68b17 0x8fc83000
VSTDPV3.SYS 0x8ff0c000 0x00102000 10/15/2008 19:32:04 0x48f68b84 0x8fe0a000
nvm62x32.sys 0x8fd76c80 0x00054c80 10/17/2008 16:00:39 0x48f8fcf7 0x8fd22000
spldr.sys 0x8b1ef000 0x00008000 5/11/2009 11:13:47 0x4a084ebb 0x8b1e7000
spsys.sys 0xa02a5000 0x0006a000 5/11/2009 11:37:10 0x4a085436 0xa023b000
nvlddmkm.sys 0x919a2940 0x00965940 5/14/2009 15:32:27 0x4a0c7fdb 0x9103d000
How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page:
Drivers and Downloads