• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSODs after installing new 1TB drive and fresh vista install

KeypoX

KeypoX

Diamond Member
I just got a samsung 1TB and now i keep getting BSODs at random times. With random errors, such as PFN List corrupt, memory management and another one i missed the name of.

I ran vistas memory diagnostic tool 4 passes. And used Everest to check the SMART on the HD. Both have no errors but I keep getting bsod.

Im running a gigabyte p35 ds3l, 4GB ram, vista 64 ultimate, 6400 @ 3ghz.

This was a stable system never had a BSOD, until i installed this HD now i am getting multiple BSODs per day. Well only had it installed for 2 days and had 4 in one day (yesterday) and the day before had minimal use.

I think my next step is to download the samsung disk and check the hard drive with that and probably reinstall 🙁.

Any ideas?
 
OK i checked device manager to see if everything was installed correctly. And there was a missing device so i used my gigabyte disk to install it because it wasnt with the package on gigabytes website...weird. So hopefully now everything will be ok lol. Also i uninstalled CCC because i read that it was causing some people problems. I use ATI TRay tools anywho.

Um i guess i will wait and see what happens now. Cross fingers this system should be 100% stable atleast it was before this HD.

OHHHHH and the stupid samsung tools wouldnt boot!
 
Good luck, but I wouldnt be surprised if you ran into a software bug involving an addressing limitation (eg, buffer size, pointer list, etc.).
 
Originally posted by: C1
Good luck, but I wouldnt be surprised if you ran into a software bug involving an addressing limitation (eg, buffer size, pointer list, etc.).
Click to expand...

And you think this why?
 
In the past years Ive had to abandon or find a work around with most of my formatting and partitioning programs and controllers that wont work with increasing HDD sizes. (Even turns out to be true with hardware a couple years old that cant read media cards because the capacity increases by leaps and bounds [eg, 2 year old $40 Belkin card reader can only read 1Gb SD because that was the largest card at the time of the reader's release; poor anticipation planning as shortly 2Gb SD card came out; OK though if objective is to increase sales of your media readers]).

Ive worked most of my life with computer systems and software development and testing (a lot of it military) and something like what is being reported would not be untypical.

Not saying that it is for sure that this is the cause, but it would be my first suspicion.
It would be resultant more due to a programming oversight or inappropriate specificationing, but would be correctable via a software patch or firmware mod via flash.

PS: Remember that at the time of the release of the aforementioned hardware, the 1 TB HDD did not exist (or was too new) and it would not have been possible (or likely) to test the system's ability to control an HDD at 1 TB and beyond.
 
PS: Remember that at the time of the release of the aforementioned hardware, the 1 TB HDD did not exist (or was too new) and it would not have been possible (or likely) to test the system's ability to control an HDD at 1 TB and beyond.
Click to expand...

I've bee running Vista on over a TB since release day, and there is no magic demark at the 1tb line like there is at certain other sizes. I just dont see that factoring in on this one.

 
That is good news, but in this case I would be suspicious of the MB (BIOS or controller chips) plus even some application accessing the HDD in the background (maybe even a driver) that is running in the OS.

Perhaps Event Viewer might be set up to attempt to capture the source of the event behind the BSOD.

Also wouldnt hurt to pull out and reseat PCI (especially Video) and SATA connectors and especially the RAM.

Wouldnt surprise me if a different brand of 1 TB HDD would be found to work fine in the subject system.
 
Originally posted by: C1
That is good news, but in this case I would be suspicious of the MB (BIOS or controller chips) plus even some application accessing the HDD in the background (maybe even a driver) that is running in the OS.

Perhaps Event Viewer might be set up to attempt to capture the source of the event behind the BSOD.

Also wouldnt hurt to pull out and reseat PCI (especially Video) and SATA connectors and especially the RAM.

Wouldnt surprise me if a different brand of 1 TB HDD would be found to work fine in the subject system.
Click to expand...

He also might want to see if there is either a chipset or BIOS update for his system. I think some nVidia chipset boards are having trouble with 1TB+ drives.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top