Antivirus Software? Recommend or the
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\msnhao\Windows_NT6_BSOD_jcgriff2\030412-22557-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0321a000 PsLoadedModuleList = 0xfffff800`0345f670
Debug session time: Sun Mar 4 13:26:42.973 2012 (UTC - 7:00)
System Uptime: 0 days 1:46:59.191
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004d36d90, fffff88003efc568, fffff88003efbdc0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 )
Followup: MachineOwner
---------
2: 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: fffff88004d36d90, The address that the exception occurred at
Arg3: fffff88003efc568, Exception Record Address
Arg4: fffff88003efbdc0, 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!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`04d36d90 8b4810 mov ecx,dword ptr [rax+10h]
EXCEPTION_RECORD: fffff88003efc568 -- (.exr 0xfffff88003efc568)
ExceptionAddress: fffff88004d36d90 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000000c4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003efbdc0 -- (.cxr 0xfffff88003efbdc0)
rax=0000800000000000 rbx=fffff8a00a5ee540 rcx=fffffa800ad08000
rdx=fffffa800a764780 rsi=fffffa800ad08000 rdi=fffffa800ad08000
rip=fffff88004d36d90 rsp=fffff88003efc7a0 rbp=fffffa80074a2938
r8=fffffa8006aad501 r9=0000000000000000 r10=0000000000000000
r11=000000000000007f r12=fffffa800a764780 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4:
fffff880`04d36d90 8b4810 mov ecx,dword ptr [rax+10h] ds:002b:00008000`00000010=????????
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c9100
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
fffff880`04d36d90 8b4810 mov ecx,dword ptr [rax+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88004d33ed3 to fffff88004d36d90
STACK_TEXT:
fffff880`03efc7a0 fffff880`04d33ed3 : 00000000`00000000 fffffa80`07181310 00000000`0000001d 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0xc4
fffff880`03efc7d0 fffff880`04d4e65d : 00000000`00000000 fffff8a0`047a51b0 fffffa80`00000000 fffffa80`06aad540 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`03efc9a0 fffff880`04d4e398 : fffff800`04be2080 fffff880`04d4dd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03efcb90 fffff880`04d4de96 : 00000000`00000000 fffffa80`06fccb10 00000000`00000080 fffffa80`0aa95410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03efcbc0 fffff800`03531fee : 00000000`0290d183 fffffa80`0a889a10 fffffa80`066ef3d0 fffffa80`0a889a10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03efcc00 fffff800`032885e6 : fffff800`0340ce80 fffffa80`0a889a10 fffff800`0341acc0 fffff880`0163fcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03efcc40 00000000`00000000 : fffff880`03efd000 fffff880`03ef7000 fffff880`03efc540 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff88003efbdc0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\msnhao\Windows_NT6_BSOD_jcgriff2\030312-27939-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.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03449670
Debug session time: Sat Mar 3 21:04:14.363 2012 (UTC - 7:00)
System Uptime: 0 days 1:05:02.206
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a008931a40, fffff8a008931a40, ffff78a008931a40}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
Followup: Pool_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a008931a40, the pool entry being checked.
Arg3: fffff8a008931a40, the read back flink freelist value (should be the same as 2).
Arg4: ffff78a008931a40, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: aaHMSvc.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800033ae70f to fffff80003280c40
STACK_TEXT:
fffff880`0884b768 fffff800`033ae70f : 00000000`00000019 00000000`00000003 fffff8a0`08931a40 fffff8a0`08931a40 : nt!KeBugCheckEx
fffff880`0884b770 fffff800`033b01a1 : fffffa80`0c217b60 fffff8a0`0cdb74f0 00000000`00000000 fffff800`00000000 : nt!ExDeferredFreePool+0xcbb
fffff880`0884b800 fffff800`0358dc8f : 00000000`00000000 fffff8a0`02438d00 00000000`42456c41 fffff800`000000e2 : nt!ExFreePoolWithTag+0x411
fffff880`0884b8b0 fffff800`0358dd88 : 00000000`00000000 00000000`fffeffff fffff800`033f4e98 00000000`c0000000 : nt!AlpcpMessageDestroyProcedure+0xbf
fffff880`0884b8f0 fffff800`0358d392 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`c0000000 : nt!AlpcpDestroyBlob+0x28
fffff880`0884b920 fffff800`0358e3a6 : fffffa80`0b1cf490 fffff880`c0000000 00000000`c0000000 fffffa80`0b1cf490 : nt!AlpcpReceiveMessage+0x65f
fffff880`0884b9c0 fffff800`0327fed3 : fffffa80`0c217b60 fffff880`0884bb60 00000000`0164e7f8 fffffa80`0b1cea10 : nt!NtAlpcSendWaitReceivePort+0x1e6
fffff880`0884ba70 00000000`770c1b6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0164e7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770c1b6a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+cbb
fffff800`033ae70f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExDeferredFreePool+cbb
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+cbb
BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+cbb
Followup: Pool_corruption
---------
- Related to DirectX/graphics card/graphics card drivers. Other possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
- Possible cause is 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. 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.
- Re-install DirectX drivers using Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details
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.
- Download the latest drivers for your display card(s)
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Expand Display adapters
- 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 latest driver for the display cards once Windows starts
Alternatively:
- Login as an adminstrative user
- Download the latest drivers for your display card(s)
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Expand Display adapters
- 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 latest driver for the display cards once Windows starts
- 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.
Quote