New
#21
24 Hours of Driver Verifier and no BSOD.
24 Hours of Driver Verifier and no BSOD.
I'm finding these errors reported frequently in Event Logs:To me, that seems like hard drive trouble. Have you run SeaTools?Code:Event[140]: Log Name: System Source: nvrd64 Date: 2011-03-20T12:54:32.181 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: User-PC Description: The driver detected a controller error on . Event[211]: Log Name: System Source: volmgr Date: 2011-03-20T12:53:36.656 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: User-PC Description: Crash dump initialization failed!
SeaTools for Windows | Seagate
Also, run a disk check; open a command prompt and enter:Let us know the results of both.Code:chkdsk /r
Install the latest nForce package from here, and install the SATA/RAID drivers: NVIDIA DRIVERS 15.49 WHQL
I tried to run disk check. This is what it says:
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another process. Would you like to schedual this volume to be checked the next time the system restarts? (Y/N)
I pressed N just for the time being. What should I do in this case?
Also I tried running SeaTools and I get this error:
Index and length must refer to a location within the string.
Parameter name: length System.String
InternalSubStringWithChecks(Int32, Int32, Boolean)
This is all gibberish to me. Any thoughts on what I should do?
Side note: I am ALMOST CERTAIN that I have been able to run disk check in the past, but I could be wrong.
Hi,
When prompted with :
Chkdsk cannot run because the volume is in use by another process. Would you like to schedual this volume to be checked the next time the system restarts? (Y/N)
You should choose Y , then reboot the computer. At bootup, it will then run the chkdsk.
Regards,
Golden
Thanks Golden, I'll do that right now.
Turns out Disk Check was taking longer than expected so I didn't have enough time to run the full thing, so I'm going to run it in a few minutes. In the meantime, can anyone help with the error I receive from SeaTools when I try to run it?
Index and length must refer to a location within the string.
Parameter name: length System.String
InternalSubStringWithChecks(Int32, Int32, Boolean)
That seems like a program error, rather than a hard drive issue (though either is possible). Try using Data Lifeguard Tools instead: WD Support / Downloads / SATA & SAS / WD Caviar Black
I have installed the program just now, but it won't let me test any drives. There is no drive shown under "Physical Drive", however, there is a drive shown under "Logical Drive" but it won't let me test it. Hmmm...
That seems strange to me; I'd expect at least one of those programs to work for you. Perhaps there is something I don't know which would explain the errors in both.
Continue with the Chkdsk as you find the time; you might also try SeaTools for DOS or Hitach DFT.
Hi,
An additional option to check your hard disk if you can't get SeaTools, Hitachi or LifeGuard to work, is
CrystalDiskInfo
Regards,
Golden