I get BSOD errors no matter what I try. Safe Mode, While running Windows Defender Offline, Using recovery disk, Last good config startup, etc.
Errors are as listed in title. Suspect bad hard drive. No way to get the dump files.
Using Windows 7 home 64bit on Samsung laptop.
Any ideas?
Last edited by cyclonebax; 03 Jan 2013 at 01:07. Reason: Additional info
Are you getting BSODs while in the Recovery Disk environment, or are you saying the recovery disk doesn't fix the problem?
Those bugcheck codes are pretty common, and without any further information we can't work on this, though given that one of them refers to NTFS activity failure, it may indeed involve a bad hard drive. Unless you're actually getting BSODs inside the recovery disk environment, in which case it would be another hardware failure.
Is your laptop currently under warranty? If so, best to approach Samsung about it. If need be, enforce the idea that you want the system replaced, not just 'fixed'. Often times OEMs will only replace one part and send it back to you. If that part wasn't what caused it, it would mean having to repeat the process till the replace what does. Better to just do it all in one go. Otherwise, yes, I do believe we are dealing with hard drive failure, albeit with what little data we have.
When I use the recovery disk I get to the choice to repair the system or restore to backup(I think those are the 2 choices). I chose the repair the system and then after a couple of minutes got the BSOD.
Every choice I select gets the BSOD. I thought I would check for viruses and did a bootable usb of Windows Defender Offline. It ran for about 10-15 minutes and I got the BSOD.
Mmmk, it does sound like any drive activity is causing problems, which means the drive is indeed bad. Looks like you'll wanna replace it.
So I replaced the hard drive and restored last backup. It still gets BSOD, but I was able to go into safe mode and get the dump files.
Any help would be appreciated.
Last edited by cyclonebax; 08 Jan 2013 at 22:42. Reason: corrected zip file
Can you get Driver Verifier going? Set it up in Safe Mode, restart into normal mode, let it crash a few times, then send us resulting minidumps.
I set up verifier per instructions and the computer continues to reboot but no BSOD, goes from blank screen to another screen with choices to start windows normally or launch startup repair.
In startup repair it crashed to BSOD but came back to the same 2 choices. Can't get it to start in Safe Mode now.
Figured out how to get into safe mode and have attached the zip file
The only other possibility besides the drive itself being bad is the drive controller, which is just as likely as a bad drive. The most recent crash appears to be caused by a bit flip, where a single bit of data has unexpectedly been zeroed, often due to a hardware malfunction. It occurred during some bluetooth activity, which is usually one of the first things to go on a bad motherboard, along with USB.
The data seems to compound on the notion that this is indeed a bad motherboard, in which case you will need to send to Samsung for repair/replacement.
Quote