[cucubelu]

Right.

Blue Screen of Death.

Followed by my primary OS partitioned drive being unavailable (during which only my other HD is available, and Windows won't boot up) upon reboot for the first 5 mins after crash. I wait 5 mins, and then reboot normally.

I am thinking this is a HD problem or a motherboard, but I am torn between the two.

Crash happens randomely, between four/five times a day and sometimes every 3 days.


Yes I have tried googling this problem, really didn't get anywhere. Figured I would give it a shot here before I go spend $200 on a new SSD.

Here the dump shot:

Double post

Adding my dxdiag.

open CMD as administrator and run the command "chkdsk /f" to check and attempt to repair hard drive errors. but im leaning towards memory, not sure why XD... in your start menu search type "windows memory diagnostic" and run that just to be thorough

[cucubelu]

I will give it a go on my next scheduled reboot in a few hours, if it doesn't crash sooner that is haha!

Double post

Update:

Both tests came out 100% error free...bah!
I will wait for next crash to display the 2nd error message I keep getting. The one that won't allow my drive to be accessed. I will post it as soon as I get it.

Double post

Here it is... just a few hours later! haha! ...this is sad

ok def.. u make any changes to ur system that coincides with the blue screens? you can try doing a system restore to an earlier time before the blue screens started happening. this will undo any adverse changes to ur registry which may be the cause. viruses or malware can cause these issues so make sure u rule both of those possibilities out by thoroughly scanning

def update ur SSD firmware if you dont have the latest version with the ADATA field updater. the new firmware is supposed to fix some issues with blue screens as well:

Fixes:Issue resolved since version 3.2.0: - Fixed a rare condition when waking from slumber mode that could cause the drive to hang. This can cause a Blue Screen error if the drive is the primary storage boot device.
- Fixed a rarely occurring issue during S3/S4 cycling to handle marginal flash timing. This can cause a Blue Screen error if the drive is the primary storage boot device.
- Fixed an issue during a firmware update where APM would be marked
disabled in identify.

[cucubelu]

Thanks! I will give it a go. I always forget to update the firmware on the drives. Hopefully this will work. Cheers!

Double post

Well, their support was fascinating. Couldn't firmware update, as their own update doesn't recognize my drive, and after a few hours on the phone with their support they still don't know what is going on, and say "this is quite common with our drives". Hilarious, that their own support is saying how shit they are.

A professional samsung 256 SSD might be where I end up after all!

I've had both Samsung and Intel SSDs and I can say you cant beat them for reliability. I also have an OCZ thats been flawless for me, but ive had friends who wernt so lucky with them. Intel SSDs r pure win on all fronts.

Before u condemn ur SSD as the cause i wud clone ur C drive to another HDD or SSD if you have one laying around and use that for a few days and see wut happens, then u will be sure. plus u will have a full C drive backup to boot.

[cucubelu]

SAMSUNG 840 Pro Series MZ-7PD256BW 2.5" 256GB SATA III MLC Internal Solid State Drive (SSD)

$40 off this weekend. Not a bad deal! :-)
Screw ADATA bullshit shenanigans!

nice and gl!

[cucubelu]

nice and gl!

Thanks for the help Pishtim!

I got the same error once the computer crashes after 5-10 minutes so i installed a new windows and it got fixed