Problem Devices:
Code:
Multimedia Video Controller PCI\VEN_BDBD&DEV_A117&SUBSYS_A117BDBD&REV_00\4&3B43D722&0&0038 The drivers for this device are not installed.
The above missing device driver may be an HP device or something you installed yourself. If it is an HP device, the drivers can be downloaded from HP Support & Drivers | United States. If you installed a multimedia video device to your system, you should download the drivers from the manufacturer's driver support site.
Problematic software:
Code:
ascservice.exe c:\program files (x86)\iobit\advanced systemcare 5\ascservice.exe 672 13 200 1380 4/29/2012 12:02 AM 5.0.0.37 485.84 KB (497,496 bytes) 3/22/2012 2:26 AM
asctray.exe c:\program files (x86)\iobit\advanced systemcare 5\asctray.exe 3412 8 200 1380 4/29/2012 12:03 AM 5.1.0.232 605.84 KB (620,376 bytes) 3/22/2012 2:26 AM
Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Tashikie\Windows_NT6_BSOD_jcgriff2\042912-39156-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03210000 PsLoadedModuleList = 0xfffff800`0344de70
Debug session time: Sat Apr 28 21:56:52.095 2012 (UTC - 6:00)
System Uptime: 0 days 0:50:58.516
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image usbhub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880091112fd, fffff88003fdb718, fffff88003fdaf80}
Probably caused by : usbhub.sys ( usbhub+1e2fd )
Followup: MachineOwner
---------
0: 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: fffff880091112fd, The address that the exception occurred at
Arg3: fffff88003fdb718, Exception Record Address
Arg4: fffff88003fdaf80, 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+1e2fd
fffff880`091112fd 488b6e48 mov rbp,qword ptr [rsi+48h]
EXCEPTION_RECORD: fffff88003fdb718 -- (.exr 0xfffff88003fdb718)
ExceptionAddress: fffff880091112fd (usbhub+0x000000000001e2fd)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048
CONTEXT: fffff88003fdaf80 -- (.cxr 0xfffff88003fdaf80)
rax=fffffa80076a8400 rbx=fffffa8005362050 rcx=fffffa8005363e90
rdx=0000000000008124 rsi=0000000000000000 rdi=fffffa8005362050
rip=fffff880091112fd rsp=fffff88003fdb950 rbp=fffffa8005362708
r8=0000000050734478 r9=0000000000000000 r10=fffffa80053621a0
r11=0000000000000000 r12=fffffa80076a8400 r13=0000000000000010
r14=0000000000000000 r15=fffffa80053621a0
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+0x1e2fd:
fffff880`091112fd 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 fffff800034b80e0
0000000000000048
FOLLOWUP_IP:
usbhub+1e2fd
fffff880`091112fd 488b6e48 mov rbp,qword ptr [rsi+48h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880091112fd
STACK_TEXT:
fffff880`03fdb950 00000000`00000000 : fffff800`78447350 fffffa80`053621a0 fffffa80`076a86c8 fffffa80`076a8400 : usbhub+0x1e2fd
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: usbhub+1e2fd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbhub
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ae28268
STACK_COMMAND: .cxr 0xfffff88003fdaf80 ; kb
FAILURE_BUCKET_ID: X64_0x7E_usbhub+1e2fd
BUCKET_ID: X64_0x7E_usbhub+1e2fd
Followup: MachineOwner
---------
The above crash was caused by a USB device or the USB ports themselves. - Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
- Shut down and turn off the computer.
- Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
- "Remove the computer from any port replicator or docking station, disconnect
cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
- Hold down the power button for 30 seconds. This closes the circuit and ensures all
power from components is drained to clear the software connections between the BIOS
and hardware and clear any corruption in the temporary memory.
- (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
and mouse should suffice and be the only peripherals reconnected.
- Turn it on to reinitialize the software connections between the BIOS and hardware
A few other crashes implicate the Kobo Reader as the USB device causing issues...
Quote