Windows 8 x101 BSOD

It's not so much anything that you're doing is making it corrupt, the DMP file itself is corrupt. It's of no use, unfortunately. We'll have to wait until we get a new one.

Regards,

Patrick
 
This is what I'm consistently getting when attempting to analyze your Kernel Dumps. Any other analysts having any luck?

error1.png

Regards,

Patrick
 
I downloaded the kernel from the same link, and the only way I could reproduce your error is by opening it from within the compressed folder. Are you extracting the kernel first and then opening it from within WinDbg?
 
Hi,

Yes, of course. I am extracting it and then loading the DMP through WinDbg.

Regards,

Patrick
 
Still the same error, unfortunately.

Hang tight, I'll see if any other analysts can view it.

Regards,

Patrick
 
I tried the Skydrive upload, same error :/

Edit: Likewise with the latest dump.
 
Last edited:
I've got no problem loading the kernel in WinDbg. Perhaps someone could guide me through the analysis? SS of "!analyze -v" on the latest: Untitled.jpg
 
Hi -

Paste these commands into kd>
Code: 
!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios

They may yield clues.

Attach entire Windbg log (text file) to next post.

Regards. . .

jcgriff2
 
So it's looking like I committed the ultimate sin in computer troubleshooting and didn't check the simplest and most obvious resolution first. After formatting the drive and installing Windows 7(which I wanted to do regardless of the crash issues), the system was immediately giving me the same issues. I checked the temps inside and noticed the CPU was idling at about 70 degrees celsius. Took off the heatsink, cleaned out the fins and fan, and the idle dropped down to 28. I'm assuming that hadn't been cleaned since I put this system together, as it's not mine, but one I built for a friend. So far, everything looks good, but I will keep you guys updated. Thanks again for your help.
 
Yes both versions are full retail. I figured reformatting and reinstalling the OS would be a quick remedy for a driver issue. With regards to the previously crashing unit, however, the computer seemed to be doing well. So well, in fact, I actually did a little bit of overclocking on the CPU/GPU and RAM. I'll watch it for the next couple days, though, and let you guys know if we can call this case closed.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top