New
#11
No my SSD died, this is a re-install on a new HDD. Thats why I thought maybe a Sata controller might be causing this. I've only had these problems since it died a month ago.
No my SSD died, this is a re-install on a new HDD. Thats why I thought maybe a Sata controller might be causing this. I've only had these problems since it died a month ago.
Okay then, Run SeaTools SeaTools for DOS and Windows - How to Use
Ok the Seatools for windows didn't work (no drives listed), so ran the DOS version and both Short and Long Tests PASSED.
There is no generic test in the DOS version, only short, long and acoustic. And I can't hear anything in the acoustic test.
ok I'm going to start trying driver verifier..
My second BSOD to occur, but I'm afraid I don't think it's related to my problem. If I'm reading it right, it's zone alarm firewall, but the windows hang problem preceded this installation. I'll disable it though in the mean time to avoid more conflicts with DV.
This is your Zone Alarm TrueVector Device Driver, update it.Code:BugCheck 50, {fffff6f850013718, 0, fffff80002b95c25, 5} Unable to load image vsdatant.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for vsdatant.sys *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys Could not read faulting driver name Probably caused by : vsdatant.sys ( vsdatant+4bf3a )
I am starting to pull my hair out with this, windows is continuing to freeze, but I am not getting any more BSOD. Should I change DV to check MS drivers as well?