Windows 7 crashes after 5 minutes.

[noaco]

I attach the crash file.
eh ok.
thanks.
bye.
ciao.
andrea.

 

[richc46]

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\8TAPMLWM\Windows_NT6_BSOD_jcgriff2[1]\Windows_NT6_BSOD_jcgriff2\123010-15475-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Thu Dec 30 17:15:30.299 2010 (GMT-5)
System Uptime: 0 days 0:04:52.297
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..........................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800434c2fd, fffff880009e7878, fffff880009e70e0}
Unable to load image \SystemRoot\system32\DRIVERS\libusb0.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+392c )
Followup: MachineOwner
---------
3: 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: fffff8800434c2fd, The address that the exception occurred at
Arg3: fffff880009e7878, Exception Record Address
Arg4: fffff880009e70e0, 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: 
usbhub!UsbhFdoSetPowerDx_Action+4d
fffff880`0434c2fd 488b6e48        mov     rbp,qword ptr [rsi+48h]
EXCEPTION_RECORD:  fffff880009e7878 -- (.exr 0xfffff880009e7878)
ExceptionAddress: fffff8800434c2fd (usbhub!UsbhFdoSetPowerDx_Action+0x000000000000004d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048
CONTEXT:  fffff880009e70e0 -- (.cxr 0xfffff880009e70e0)
rax=fffffa8003bf2c60 rbx=fffffa800514a050 rcx=fffffa800514bbf0
rdx=000000000000339a rsi=0000000000000000 rdi=fffffa800514a050
rip=fffff8800434c2fd rsp=fffff880009e7ab0 rbp=fffffa800514a708
 r8=0000000050734478  r9=0000000000000000 r10=fffffa800514a1a0
r11=0000000000000000 r12=fffffa8003bf2c60 r13=0000000000000010
r14=0000000000000000 r15=fffffa800514a1a0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
usbhub!UsbhFdoSetPowerDx_Action+0x4d:
fffff880`0434c2fd 488b6e48        mov     rbp,qword ptr [rsi+48h] ds:002b:00000000`00000048=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
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:  0000000000000048
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec10e0
 0000000000000048 
FOLLOWUP_IP: 
libusb0+392c
fffff880`0432392c ??              ???
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER:  from fffff8800434aa7a to fffff8800434c2fd
STACK_TEXT:  
fffff880`009e7ab0 fffff880`0434aa7a : fffffa80`0514a050 00000000`00000004 fffffa80`0514a708 00000000`00000004 : usbhub!UsbhFdoSetPowerDx_Action+0x4d
fffff880`009e7b10 fffff880`0434970b : fffffa80`03bf2e50 fffffa80`0514a1a0 fffffa80`0514a050 fffffa80`03bf2c60 : usbhub!UsbhFdoDevicePowerState+0x206
fffff880`009e7b60 fffff880`043489c7 : fffffa80`03bf2c60 fffffa80`03bf2e98 fffffa80`0514a050 fffff800`02d8c4a2 : usbhub!UsbhFdoPower_SetPower+0x93
fffff880`009e7ba0 fffff880`0432ffdf : fffffa80`03bf2c60 fffffa80`0514e1a0 fffffa80`05a351a0 fffffa80`04929a98 : usbhub!UsbhFdoPower+0xaf
fffff880`009e7be0 fffff800`02d8c562 : fffffa80`03bf2c60 fffffa80`03bf2e98 fffffa80`0514e1a0 fffffa80`03bf2c60 : usbhub!UsbhGenDispatch+0x7f
fffff880`009e7c10 fffff880`0432392c : fffff880`043260d0 00000000`00000003 00000000`00000000 fffffa80`03bf2c60 : nt!IopPoHandleIrp+0x32
fffff880`009e7c40 fffff880`043260d0 : 00000000`00000003 00000000`00000000 fffffa80`03bf2c60 00000000`00000000 : libusb0+0x392c
fffff880`009e7c48 00000000`00000003 : 00000000`00000000 fffffa80`03bf2c60 00000000`00000000 fffffa80`03bf2c60 : libusb0+0x60d0
fffff880`009e7c50 00000000`00000000 : fffffa80`03bf2c60 00000000`00000000 fffffa80`03bf2c60 fffffa80`0514e050 : 0x3
 
SYMBOL_STACK_INDEX:  6
SYMBOL_NAME:  libusb0+392c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: libusb0
IMAGE_NAME:  libusb0.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  44f19708

The main problem is to update this driver

Libusb0.sys file description
Productname: LibUSB-Win32 - Kernel Driver
Description: LibUSB-Win32 - Kernel Driver
Company: libusb-Win32


[Outdated drivers
CODE] athrxu6.sys Wed Jul 04 22:58:34 2007
AsIO.sys Mon Dec 17 04:11:49 2007
[/CODE]


The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command


Scan with your Anti Virus

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included the driver verifier test so that you may determine which drivers are in need of immediate attention.

How to Find Drivers
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 help you 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
- - 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: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html