.dmp file analysis

[poustek]

Hello

Im just looking for someone who can take a look on my last .dmp file and can tell me something more about it.

It happend just like that, when actually I was not doing anything. (Maybe moving my mouse over desktop) Notice the "last change date", Im pretty sure I had right system time set and it happend yeasterday. Also my system time was changed to this value after bsod reboot.


Im not looking for solution, because Im having serious issues with my pc right now and it would be long story. Just want to know, what caused this bsod.


Thanks in advance.

 

[Golden]

With the minimal information you provided, there are several possibilities:

• Outdated Windows installation
• Outdated USB drivers
• Faulty CMOS battery
• All of the above

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*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.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`03651670
Debug session time: [B][COLOR="Red"]Tue Jan  1 11:34:50.229 2008[/COLOR][/B] (UTC + 10:30)
System Uptime: 0 days 1:52:06.851
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 D1, {4a8248c, 2, 1, fffff88006eb5d7c}

Probably caused by :[B][COLOR="red"] hidusb.sys[/COLOR][/B] ( hidusb!HumReadReport+13f )

Followup: MachineOwner
---------