Bsod

[insanegain]

Hi everyone,

I have reports of this brand new build shutting down. Found 3 files in the minidump folder and haven't the slightest of what they mean.

Can anyone shed some light on this for me?

Thanks!

insanegain

PS: I can't attach them because they are slightly greater than 200k and don't know how to make them smaller


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\host\Desktop\Logan Minidumps\010811-23712-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50
Debug session time: Sat Jan 8 22:25:55.426 2011 (GMT-8)
System Uptime: 0 days 0:00:24.924
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ff00f3, fffff880031708b8, fffff88003170120}

Probably caused by : ntoskrnl.exe ( nt!PerfInfoAddToFileHash+42 )

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

 

[B00kWyrm]

I just noticed no-one had replied yet.
Getting anywhere?

If not...

"A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information."