[Luv2Ski]

I have finally grown tired of not being able to determine what causes my BSOD problem. It occurs almost every day and sometimes several times a day. I have reinstalled NIS09 believing that might be the problem and checked and rechecked every Dell driver I can find on my machine. No change in operation. I have tried to use Windbg and even tried to find the offending driver (which debug says is crcdisk.sys) but I am out of my league. The one thing that is consistent is that it is a 0xC4 error.

Details:
Dell Inc. Latitude D630
2.00 GHz Intel Core2 Duo
2GB RAM
80 GB Hard Drive
32 bit OS
Windows Vista Business Service Pack 1 (build 6001) w/ all current patches

I have attached the first dump of the day for the last 4 days in the zip file. Any direction or help is appreciated. I have run the memory tests and disk tests but haven’t found any errors there but will do them all again if I can remove this aggravation. Thanx

[Rollin' Rog]

First, you have "Driver Verifier" and it is flagging this module >>

BugCheck C4, {a0, c96b2f20, 8710cba0, 711514c}

Probably caused by : crcdisk.sys ( crcdisk!VerifyOrStoreSectorCheckSum+111 )


If you are using any Virtual Drives such as Alcohol or Daemon Tools, those should be removed since they seem to appear to produce this error in the above module in many searches

And I would also disable Driver Verifier by running the command:

verifier /reset


But if BSODs continue after disabling driver verifier, upload those new minidumps and run chkdsk on your drive since this is a driver which checks for file integrity.

You may also wish to examine the System Log in the Event Viewer (run: eventvwr.msc)) for repeating errors; look especially for any that say "NTFS".

It is also possible that you have corrupt or incompatible SATA drivers, and those may need to be reinstalled.

[Luv2Ski]

Ran verifier /reset. Will let you know results. No virtual drives in use.

[Luv2Ski]

Reloading SATA driver seems to have done the trick. Thanx again.

[Rollin' Rog]

Great to hear, you're most welcome. Saved that suggestion for last since I thought it might be the most problematic to address unless you are already experienced in loading those