Antivirus software? Recommend either 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\michaelkearns34\Windows_NT6_BSOD_jcgriff2\030712-25365-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e70
Debug session time: Wed Mar 7 16:16:27.435 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:51.198
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800030cd7a5, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
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: fffff800030cd7a5, 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!ExpInterlockedPopEntrySListFault16+0
fffff800`030cd7a5 498b08 mov rcx,qword ptr [r8]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033020e0
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: explorer.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88008539678 -- (.exr 0xfffff88008539678)
ExceptionAddress: fffff800030cd7a5 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88008539720 -- (.trap 0xfffff88008539720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000002bd420003 rbx=0000000000000000 rcx=fffffa8004616440
rdx=ff00fa80075b6831 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030cd7a5 rsp=fffff880085398b0 rbp=0000000000000043
r8=ff00fa80075b6830 r9=0000000000000001 r10=fffffa8004616440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`030cd7a5 498b08 mov rcx,qword ptr [r8] ds:faa8:ff00fa80`075b6830=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003104919 to fffff800030ca5c0
STACK_TEXT:
fffff880`08538ea8 fffff800`03104919 : 00000000`0000001e ffffffff`c0000005 fffff800`030cd7a5 00000000`00000000 : nt!KeBugCheckEx
fffff880`08538eb0 fffff800`030c9c02 : fffff880`08539678 fffff880`08539960 fffff880`08539720 00000000`00000000 : nt!KiDispatchException+0x1b9
fffff880`08539540 fffff800`030c850a : fffff8a0`0125ea40 fffff8a0`081fbed8 fffff6fc`500092f0 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`08539720 fffff800`030cd7a5 : fffff880`08539960 fffff880`0101dd31 00000000`79853867 fffff880`08539900 : nt!KiGeneralProtectionFault+0x10a
fffff880`085398b0 fffff880`0101dd31 : 00000000`79853867 fffff880`08539900 fffffa80`07a13ec8 fffffa80`07a13ec8 : nt!ExpInterlockedPopEntrySListFault16
fffff880`085398c0 fffff880`0101c6c7 : fffffa80`05af0010 fffffa80`04616440 fffffa80`0518a040 00000000`000007ff : fltmgr!FltpPassThrough+0x421
fffff880`08539940 fffff800`030bc0c2 : fffffa80`05af0030 fffffa80`072f2320 00000000`00000043 00000000`717f9578 : fltmgr!FltpDispatch+0xb7
fffff880`085399a0 fffff800`030bc3c5 : 00000000`00000001 00000000`00000001 fffff880`08539a60 fffff880`08539a90 : nt!IoPageRead+0x252
fffff880`08539a30 fffff800`030e570b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff680`00000000 : nt!MiIssueHardFault+0x255
fffff880`08539ac0 fffff800`030c86ae : 00000000`00000000 00000000`05fae3d0 00000000`00001f01 00000000`00000000 : nt!MmAccessFault+0x14bb
fffff880`08539c20 00000000`773e58b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`05fae140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773e58b5
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`030cd7a5 498b08 mov rcx,qword ptr [r8]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
BUCKET_ID: X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\michaelkearns34\Windows_NT6_BSOD_jcgriff2\030412-26426-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`0328fe70
Debug session time: Sun Mar 4 17:18:54.807 2012 (UTC - 7:00)
System Uptime: 2 days 20:59:22.461
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, fffffa8005d451a0, 10de077e, fffffa800767b638}
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa8005d451a0, Device extension pointer of the host controller
Arg3: 0000000010de077e, PCI Vendor,Product id for the controller
Arg4: fffffa800767b638, Pointer to Endpoint data structure
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff88003858ec2 to fffff800030c25c0
STACK_TEXT:
fffff800`043a5c88 fffff880`03858ec2 : 00000000`000000fe 00000000`00000005 fffffa80`05d451a0 00000000`10de077e : nt!KeBugCheckEx
fffff800`043a5c90 fffff880`03886fac : 00000000`bf804100 fffffa80`05d466a0 00000000`00000000 fffffa80`0767b7b0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff800`043a5cd0 fffff880`03886b73 : fffffa80`0767b638 fffffa80`05d45d28 fffffa80`0767b7b0 fffff880`0383c54a : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
fffff800`043a5d60 fffff880`0388bd05 : fffffa80`0767b638 fffff800`030cb239 00000000`00000002 fffffa80`05d45050 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff800`043a5da0 fffff880`0382ce8b : 00000000`00000002 fffffa80`05d451a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0x41
fffff800`043a5de0 fffff880`038319b1 : 00000000`00000040 00000000`00000004 fffffa80`0767b3f0 fffffa80`05d45050 : USBPORT!MPf_PollEndpoint+0x9b
fffff800`043a5e10 fffff880`0383d057 : fffffa80`05d451a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff800`043a5e70 fffff880`0382df89 : fffffa80`05d45050 00000000`00000000 fffffa80`05d45a02 fffffa80`05d45a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff800`043a5ed0 fffff800`030cda9c : fffff800`0323ce80 fffffa80`05d45a18 fffffa80`05d45a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`043a5f00 fffff800`030c8705 : 00000000`00000000 fffffa80`07dbcb60 00000000`00000000 fffff880`0382ddb0 : nt!KiRetireDpcList+0x1bc
fffff800`043a5fb0 fffff800`030c851c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`092dfbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
usbehci!EHCI_sMode_PollEndpointSlot+6c
fffff880`03886fac 4533c9 xor r9d,r9d
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+6c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbehci
IMAGE_NAME: usbehci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0a91
FAILURE_BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
BUCKET_ID: X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c
Followup: MachineOwner
---------
- Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash. - USB related, probably a USB device, device driver, or the ports themselves having problems.
The problem is your USB wireless device. The drivers for it are dated pre-Windows 7. USB wireless is inherently unstable because the USB ports do not provide enough power for the adapter to function in a stable manner. Couple that with an outdated driver, and crashes are imminent. We get these crashes a lot on SevenForums. Please replace the device with one that is newer technology. I would also recommend trying to find an actual wireless adapter card to put in the system rather than a USB device.
Code:
jswpslwfx fffff880`02d3d000 fffff880`02d4a000 Thu May 15 04:28:50 2008 (482c1062) 00011e66 jswpslwfx.sys
jswpslwfx.sys