Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\carlocgc\Windows_NT6_BSOD_jcgriff2\040712-18267-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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e54650
Debug session time: Sat Apr 7 08:42:15.641 2012 (UTC - 6:00)
System Uptime: 0 days 0:32:49.186
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960001acb98, fffff880027b6fe0, 0}
Probably caused by : win32k.sys ( win32k!DelQEntry+28 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001acb98, Address of the instruction which caused the bugcheck
Arg3: fffff880027b6fe0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
win32k!DelQEntry+28
fffff960`001acb98 48894208 mov qword ptr [rdx+8],rax
CONTEXT: fffff880027b6fe0 -- (.cxr 0xfffff880027b6fe0)
rax=0000000000000000 rbx=fffff900c1d46260 rcx=fffff900c0727ec8
rdx=0000000000000060 rsi=fffff900c1d46260 rdi=0000000000000000
rip=fffff960001acb98 rsp=fffff880027b79c0 rbp=fffff880027b7ca0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff880027b7bd8 r12=fffff880027b7bd8 r13=fffff900c0727ec8
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
win32k!DelQEntry+0x28:
fffff960`001acb98 48894208 mov qword ptr [rdx+8],rax ds:002b:00000000`00000068=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: RtWLan.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960001acb98
STACK_TEXT:
fffff880`027b79c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DelQEntry+0x28
FOLLOWUP_IP:
win32k!DelQEntry+28
fffff960`001acb98 48894208 mov qword ptr [rdx+8],rax
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!DelQEntry+28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f2b63bd
STACK_COMMAND: .cxr 0xfffff880027b6fe0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!DelQEntry+28
BUCKET_ID: X64_0x3B_win32k!DelQEntry+28
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\carlocgc\Windows_NT6_BSOD_jcgriff2\040712-18189-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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e90650
Debug session time: Sat Apr 7 05:26:40.541 2012 (UTC - 6:00)
System Uptime: 0 days 0:17:18.696
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002ccecfe, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )
Followup: MachineOwner
---------
1: 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: fffff80002ccecfe, 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!ExAcquireResourceSharedLite+4e
fffff800`02ccecfe f0480fba696000 lock bts qword ptr [rcx+60h],0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: WerFault.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002d13a08 to fffff80002cc8d40
STACK_TEXT:
fffff880`0a58ba98 fffff800`02d13a08 : 00000000`0000001e ffffffff`c0000005 fffff800`02ccecfe 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a58baa0 fffff800`02cc83c2 : fffff880`0a58c278 e56b6f54`035d041d fffff880`0a58c320 fffff880`0a58c600 : nt! ?? ::FNODOBFM::`string'+0x48d2d
fffff880`0a58c140 fffff800`02cc6cca : 80000001`00000007 fffff800`02fca21c 00000000`00000000 fffff800`02ce74dd : nt!KiExceptionDispatch+0xc2
fffff880`0a58c320 fffff800`02ccecfe : 00000000`00000202 fffff880`00961000 00000000`00000000 fffffa80`06b8bb60 : nt!KiGeneralProtectionFault+0x10a
fffff880`0a58c4b0 fffff800`02fc196a : 00000000`00000011 fffff8a0`0a5aea00 00000000`00000001 fffffa80`074413f8 : nt!ExAcquireResourceSharedLite+0x4e
fffff880`0a58c520 fffff800`02fc20d6 : fffffa80`076c7b60 fffffa80`076c7b60 fffff8a0`0a5aea00 fffff800`0000005a : nt!SeQueryInformationToken+0x3a
fffff880`0a58c5b0 fffff800`02fc3796 : 00000000`00000000 fffffa80`071a1010 00000000`00000002 fffffa80`06c10660 : nt!ObpLookupObjectName+0xe6
fffff880`0a58c6a0 fffff800`02fc509c : fffffa80`076c7b60 00000000`00000000 00000000`00000000 fffff800`02e71d08 : nt!ObOpenObjectByName+0x306
fffff880`0a58c770 fffff800`02fb08c4 : fffff880`0a58c8f0 00000000`80100000 fffff880`0a58c930 fffff880`0a58c8f8 : nt!IopCreateFile+0x2bc
fffff880`0a58c810 fffff800`031226f1 : fffff880`000004a2 00000000`00000000 fffff800`02fca200 fffff800`02fca1c0 : nt!NtOpenFile+0x58
fffff880`0a58c8a0 fffff800`03124409 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!PfSnGetPrefetchInstructions+0x101
fffff880`0a58c980 fffff800`030234ff : 00000000`00000000 00000000`e69f695a fffffa80`0c440b20 00000000`00000000 : nt!PfSnBeginAppLaunch+0x2f9
fffff880`0a58ca50 fffff800`02fb5ccc : fffffa80`076c7b60 fffffa80`0c440b20 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x50eb0
fffff880`0a58ca80 fffff800`02cb9af5 : fffff800`02e3de80 00000000`00000000 fffff800`02fb5b84 fffffa80`076c7b60 : nt!PspUserThreadStartup+0x148
fffff880`0a58cae0 fffff800`02cb9a77 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffff880`0a58cc20 00000000`773ec500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0024faa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773ec500
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExAcquireResourceSharedLite+4e
fffff800`02ccecfe f0480fba696000 lock bts qword ptr [rcx+60h],0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!ExAcquireResourceSharedLite+4e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ExAcquireResourceSharedLite+4e
BUCKET_ID: X64_0x1E_c0000005_nt!ExAcquireResourceSharedLite+4e
Followup: MachineOwner
---------
- Blames a Windows network process...
- Caused by your USB wireless network device. Explains 1.
- Rather inconclusive. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Have you been using the USB wireless network adapter in all crashes, or is this something new? USB wireless network adapters are inherently unstable. USB does not provide the proper power support for wireless network adapters, which can lead to crashes with these devices installed. We usually recommend replacing such devices with a PCI card wireless network adapter instead.
In regards to your programs that are installed. It appears you are currently using the ATI graphics card. If so, you should remove NVIDIA PhysX because it can cause conflicts with the ATI driver. I would also suggest a full uninstall of the ATI software and drivers by uninstalling the ATI Catalyst Install Manager and then install the latest drivers and software for that graphics card from the manufacturer's site: ASUS - Graphics Cards- ASUS EAH6950 DCII/2DI4S/2GD5.
Do the re-install of the ATI drivers after removing NVIDIA PhysX.