- Local time
- 9:21 AM
- Messages
- 19
That's only my problem ? Or there is anything else except windows updating ?
My Computer
- Computer type
- Laptop
- Computer Manufacturer/Model Number
- Asus
- OS
- Windows 7 Home Basic 64bit
- Memory
- 2.00 GB
I don't know because your BSOD'S don't produce .dmp files.
No .dmp files = no BSOD analysis possible.
I don't know because your BSOD'S don't produce .dmp files.
No .dmp files = no BSOD analysis possible.
I don't know because your BSOD'S don't produce .dmp files.
No .dmp files = no BSOD analysis possible.
here we go the .dmp files !
I don't know because your BSOD'S don't produce .dmp files.
No .dmp files = no BSOD analysis possible.
here we go the .dmp files !
Don't start another new thread again, I've already merged these two and removed the one you just started.
You just need to be patient. Starting multiple threads for the same issue is against the rules as well as causing confusion.
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
[COLOR="Red"][B]Windows 7 Kernel Version 7600 MP (4 procs) Free x64[/B][/COLOR]
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`04a04000 PsLoadedModuleList = 0xfffff800`04c40e70
Debug session time: Wed Nov 12 01:41:32.599 2014 (UTC + 10:30)
System Uptime: 0 days 0:03:04.067
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {224, fffff880022ed818, fffff98017d449d0, ffffffffc00000bb}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
Followup: MachineOwner
---------
You still haven't updated Windows as advised - this will likely solve your BSOD which appears to be USB-related.Code:************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: [COLOR="Red"][B]Windows 7 Kernel Version 7600 MP (4 procs) Free x64[/B][/COLOR] Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.17273.amd64fre.win7_gdr.130318-1532 Machine Name: Kernel base = 0xfffff800`04a04000 PsLoadedModuleList = 0xfffff800`04c40e70 Debug session time: Wed Nov 12 01:41:32.599 2014 (UTC + 10:30) System Uptime: 0 days 0:03:04.067 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ .......................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {224, fffff880022ed818, fffff98017d449d0, ffffffffc00000bb} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) Followup: MachineOwner ---------
Read it and follow the instructions:
Install Windows updates in Windows 7
You misread my reply. I said it will "likely" address what"appears" to be USB related....there may still be other issues, but it's not possible to tell until you have updated the installation.