Windows 7: Windows 7 64 bit spontaneous restart, Memory dump file provided, ty

cherrylisdal · 18 Jan 2012

Windows 7 64Bit
Desktop, namebrand components
amd

Spontaneous restart..
Bug check
Windows debugger has provided the following information on the memory dump
below:

Code:

 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\011812-25927-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 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`03219000 PsLoadedModuleList = 0xfffff800`0345e670
Debug session time: Wed Jan 18 18:47:23.166 2012 (UTC - 6:00)
System Uptime: 0 days 1:47:35.430
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1E, {0, 0, 0, 0}
 
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbDoneDpc_Worker+2a3 )
 
Followup: MachineOwner
---------
 
2: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
 
FAULTING_IP: 
+3334396164663431
00000000`00000000 ?? ???
 
EXCEPTION_PARAMETER1: 0000000000000000
 
EXCEPTION_PARAMETER2: 0000000000000000
 
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
 
BUGCHECK_STR: 0x1E_0
 
CUSTOMER_CRASH_COUNT: 1
 
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
 
PROCESS_NAME: System
 
CURRENT_IRQL: 2
 
EXCEPTION_RECORD: fffff88002f8ca08 -- (.exr 0xfffff88002f8ca08)
ExceptionAddress: fffff8800533a9c3 (USBPORT!USBPORT_Core_UsbDoneDpc_Worker+0x00000000000002a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
 
TRAP_FRAME: fffff88002f8cab0 -- (.trap 0xfffff88002f8cab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ff00fa800735b120 rbx=0000000000000000 rcx=ff00fa80070428c8
rdx=fffffa8007396758 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800533a9c3 rsp=fffff88002f8cc40 rbp=fffffa80080911a0
r8=fffffa80080911a0 r9=0000000000000000 r10=00000000ffffffff
r11=fffffa800735b010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
USBPORT!USBPORT_Core_UsbDoneDpc_Worker+0x2a3:
fffff880`0533a9c3 488908 mov qword ptr [rax],rcx ds:1050:ff00fa80`0735b120=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER: from fffff8000328d5fe to fffff80003295c10
 
STACK_TEXT: 
fffff880`02f8bae8 fffff800`0328d5fe : fffffa80`074fbf68 00000000`00000cca fffff880`02f8c260 fffff800`032c1830 : nt!KeBugCheck
fffff880`02f8baf0 fffff800`032c14fd : fffff800`0349f71c fffff800`033dcc30 fffff800`03219000 fffff880`02f8ca08 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8bb20 fffff800`032c02d5 : fffff800`033e00fc fffff880`02f8bb98 fffff880`02f8ca08 fffff800`03219000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8bb50 fffff800`032d1361 : fffff880`02f8ca08 fffff880`02f8c260 fffff880`00000000 fffffa80`08091050 : nt!RtlDispatchException+0x415
fffff880`02f8c230 fffff800`032952c2 : fffff880`02f8ca08 fffffa80`07396670 fffff880`02f8cab0 fffffa80`08091ba0 : nt!KiDispatchException+0x135
fffff880`02f8c8d0 fffff800`03293bca : fffff880`03bd8080 fffff880`045f4e5f fffffa80`07396a8c fffffa80`07396ac0 : nt!KiExceptionDispatch+0xc2
fffff880`02f8cab0 fffff880`0533a9c3 : fffffa80`07396670 fffffa80`08091ba0 fffffa80`08091ba0 fffffa80`080911a0 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8cc40 fffff880`0532bf89 : fffffa80`08091050 00000000`00000000 fffffa80`08091b02 fffffa80`08091ba0 : USBPORT!USBPORT_Core_UsbDoneDpc_Worker+0x2a3
fffff880`02f8cca0 fffff800`032a10ac : fffff880`02f64180 fffffa80`08091ba0 fffffa80`08091bb8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f8ccd0 fffff800`0328d96a : fffff880`02f64180 fffff880`02f6efc0 00000000`00000000 fffff880`0532bdb0 : nt!KiRetireDpcList+0x1bc
fffff880`02f8cd80 00000000`00000000 : fffff880`02f8d000 fffff880`02f87000 fffff880`02f8cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
 
 
STACK_COMMAND: kb
 
FOLLOWUP_IP: 
USBPORT!USBPORT_Core_UsbDoneDpc_Worker+2a3
fffff880`0533a9c3 488908 mov qword ptr [rax],rcx
 
SYMBOL_STACK_INDEX: 7
 
SYMBOL_NAME: USBPORT!USBPORT_Core_UsbDoneDpc_Worker+2a3
 
FOLLOWUP_NAME: MachineOwner
 
MODULE_NAME: USBPORT
 
IMAGE_NAME: USBPORT.SYS
 
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c08
 
FAILURE_BUCKET_ID: X64_0x1E_0_USBPORT!USBPORT_Core_UsbDoneDpc_Worker+2a3
 
BUCKET_ID: X64_0x1E_0_USBPORT!USBPORT_Core_UsbDoneDpc_Worker+2a3
 
Followup: MachineOwner

zigzag3143 · 19 Jan 2012

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

Quote:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

Quote:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Windows 7: Windows 7 64 bit spontaneous restart, Memory dump file provided, ty

Windows 7 64 bit spontaneous restart, Memory dump file provided, ty problems?