BSOD Hourly, dump files not being captured

[JET711]

Hello there,

Starting last night, I'm getting BSOD every hour (nearly exactly to the hour). I've tried to follow all the advice presented here but it seems that even though I have memory dumps configured properly, they aren't being captured (the folder doesn't even exist -- can I just create one?). BlueScreenView (clearly) can't capture them either...

Because I'm so technically advanced, I took pictures of the BSODs (attached, also). Only 2 out of 16 BSODs have been the fatal errors.

The event viewer details are all the following:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-07-19T02:36:36.710409200Z" />
<EventRecordID>10796</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Jenni-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

The application errors have been for: Windows (on the fatal error BSODs), chrome.exe, firefox.exe, msnmsngr.exe, rundll32.exe, and I think skype.exe. There are probably more but I stopped keeping track.

Basic System Specs:
Windows 7 64bit
Full retail version, reinstalled OS on July 2, 2012
All hardware purchased in November 2011

More detail can be found in my profile, but I am more than happy to provide any additional information that I can.

I really appreciate any guidance you can provide. Thanks for your help!

 

[Vir Gnarus]

The STOP bugchecks are caused by I/O errors suffered during startup when attempting to grab disk contents and slap it into memory. Therefore, either your disk (or disk controller, aka motherboard) is bad, or your memory is bad, or the bus (motherboard) inbetween is bad.

First of all, before doing any testing, I noticed you're using an SSD drive. Because SSD drives are relatively new and the bugs are still being worked out for em, your best bet is to start doing some updates. This includes the BIOS, any chipset or drive controller drivers, and the most important item, the SSD firmware. The SSD firmware especially can be buggy out of the manufacturing plant, and many people have managed to resolve issues such as yours by simply updating their firmware. The other components listed also play a role disk I/O so you'll wanna make sure they are taken care of as well.

Anyways, if you managed to accomplish all of that and things still don't do well, you'll want to run Memtest86+ full passes on your RAM. If that doesn't come up with anything, there's a good chance you have a defunct SSD drive, which isn't uncommon. Or you have a compatibility issue between your motherboard and your SSD, which can happen often when trying to run SSD drives off of older motherboards. Unfortunately there appears to be no drive diagnostic test for your drive, and I'm not sure something like Seatools would work well with it without causing false positives. I recommend if all this does not resolve things, start swapping hardware, that being the SSD drive first, then the RAM, and finally the motherboard.