bsodfrom hd failing

brian

brian

VIP Member
ok. i just got a new hd (WD 2.5" sata) model #wd1600bevsrtl. but yesterday and today i got a bsod from the hd failing. i accealy here it lose power and power back up. could it be my hd or my computer. it never happened before and i got the hd 1 mounth ago. i will post back with the bsod #
 
Most of the time the reason for any BSODs is a software/driver related problem like a bad install of video or sound drivers. Besides ending up with a drive seeing defects simply installing Windows on a drive can see problems at times. Was this a new primary or simply a drive for backing things up onto?
 
so are you saying i should reinstall vista. i just installed it a month ago so i dont mind doing it again
 
HDTune can read the SMART data for your drive, assuming it works to windows.

How do you know the BSOD was because the hd is failing?
 
You could be seeing some bad sectors being reported. The most common cause however is found to be device drivers like for video and sound. Sometimes Windows will simply lockup totally with reference to some type of memory error while there's nothing wrong with the physical memory installed.

It can also be seen when running an older program or game with newer hardwares installed. With Vista and XP dual booted on a new build here one game in particular saw blue screens or crashes to the desktop with the new DX10 video card and X-FI series sound card now being used. On the old build with multibooting there the same game ran on both Vista and XP without problems. Both cases run the same WD drives having moved 3 out of 4 into the new case. While never ruling a factory defect getting out WD has alwayts seen reliable drives here free of errprs suggesting a Windows or other software as the real problem to look into.

(HDTune is great freeware for hard drives. It displays the current temps as well as othering settings and monitoring)
 
Last edited:
got it. it seems like it is happining when i hibernate. i will try again soon. but i dont know why the one happened when my comp just bs
my.php
 
Last edited:
If it's NTFS reboot and run Chkdsk /f /r, it's also commonly caused by bad RAM. If chkdsk comes back OK try running memtest.
 
I saw a similar error screen appear on the new build here before the board went doa on the second with the Catalyst 7.8 drivers and an old game being tested. A good run of memtest ruled out bad ram while giving the appearance of it. When drivers try accessing an address reserved by Windows that screen will come up at times.

Beside the chkdsk command with the switches WD has a good dianostic tool for their drives to run as well as memtest there. You may want to disable the hibernation mode for the time being until you know what the problem is. That suggestion along with reviewing the version of the driver set for video, sound, etc. is another thought there.
 
Now you have to start looking at a driver or other software problem where something is trying to load into reserved memory address. With the old Soldier of Fortune II being the game tested that surprisingly even runs well on Vista the latest Catalyst 7.8 for XP for a new DX10 capable card was seeing crashes with that type of BSOD on the new build.

The new memory used here is in spotless condition pointing a driver incompatibility issues as the likely cause. With Vista being a new version out there's some obvious bugs that still need repair. But the problem there may be simply from something that didn't go on correctly to the new drive if no flaws are found with it.

What did you use to partition and formet it would be one question to ask. The Vista installer? Other partitioning software like Partition Magic? GParted?
 
You must log in or register to reply here.
Back
Top