lilbuddhaman wrote:Offhand I'd change your bios settings to wait X seconds at boot for hard drives to spin up, not sure what the field is actually called, but all the ones I've ever worked on have had it. I always set mine to 2s.
Edit 2: If your Mobo is the one I think, with a EUFI bios, the command should be on the Boot tab, called "Post Report", set that to 4 seconds just to test it.
Edit: Also, does your bios have a "clear ram at bootup" option, that could be something to try.
MadManOriginal wrote:So you're using the onboard audio and LAN? It looks like the 12/25 and 12/26 crashes are audio and LAN related.
I rarely use mobo manufacturer website-provided on-board device drivers because they get lazy and stop updating them when they stop selling the motherboard or it's not the latest chipset even though Realtek etc keeps putting out updates. (For example, for your motherboard the 'latest' Realtek audio drivers are from 12/2010...yeah, not the latest drivers by a long shot.) I don't use any special functions which mobo versions of drivers might expose though, especially for audio - I just use 2-channel s/pdif out so I don't know if the following suggestion will cut out some functionality. Anyway, just go to the manufacturer of the audio and LAN chipsets and get their latest drivers for your OS. It looks like you have an Intel NIC and Realtek audio, both ought to be easy to find on their websites.
DairyCreamer wrote:jokinin wrote:If I was you, I would try to test HDD and maybe try to test another PSU.
I have no particular reason to think my SSD is bad. Curious how/why the PSU might be an issue?
TheEmrys wrote:I'd turn off your computer, let it sit for a good 30 minutes or so, and then start looking at it. With it being all over the place with LAN and on-board Audio, I'd look to your chipset or possibly capacitors. Does your chipset have a fan? Does it spin? See an scorch marks? Any capcitors leaking (for those that remember, those were the BAD old days of mobos!)?
For myself, I wouldn't look at your PSU. If it isn't screeching/whining and if you have good power while its running, I wouldn't worry about how things go on shutdown.
Also, do you get these issues when it hibernates?
just brew it! wrote:The fact that the error is different each time is an indication that it isn't a problem with a specific device or driver. General flakiness like this is usually a problem with the motherboard or RAM.
Ethyriel wrote:Or power supply, a bad PSU can manifest itself in any number of ways. I'd definitely run memtest for 2-3 days, a couple passes doesn't cut it. The only driver I'd really consider is the chipset, so make sure you have the latest from Intel's website, not the motherboard manufacturers. Also make sure you're on the latest BIOS, and see if your SSD has a firmware update.
I'd pull everything out of the case and try booting on a non-conductive surface, it could be a bad mount shorting out something on the motherboard. And the PSU is usually the easiest thing to try before replacing the motherboard.
anotherengineer wrote:I concur with Krogoth and JBI, I had strange issues like that with a laptop, MS mem check came back clean as did another one. It lead me to believe it was a bad software update (virus scanner or adobe, etc.) I beat around the bush for awhile.
Put on memtest 86+ one night before bed, the next day there was literally hundreds of memory errors, pulled out one stick, re-ran and indeed it was 1 bad stick of ram giving me all that grief.
ronch wrote:This obviously looks like data is being corrupted somewhere in the system and when things don't match up, you get those BSODs. I would test RAM and the SSD thoroughly and do a reformat just to be sure a corrupted OS is not the culprit. If all these check out ok, it could be your motherboard. Btw, anybody here also thinks this could be caused by a bad SATA cable?
anotherengineer wrote:Memtest 86 and memtest 86+ are different programs, just an fyi.
Always tricky troubleshooting these things, bad or loose sata cables, another culprit.
Try the 86+ version form a bootable ISO CD rom disk, if possible, that's how I found my ram errors.