Hello, all. I received great help here on building my new system, which for the most part is excellent. The only problem is that I get rare BSODs--maybe once a day on average--with the following error codes. Bccode 24 supposedly relates to ntfs.sys, and there WAS INDEED one checkdisk fix--the one time checkdisk was made to run after a crash, it found file errors and fixed them. However, since them there has been no forced checkdisk after any crash, and I forced (chkdsk /f /r) one scan that found nothing. Just now, however, I tried to run checkdisk to check for bad sectors, while in Windows 7, and it crashed.
The components I think might be at fault are the hard drive, my #1 suspect, which is a Samsung OEM 250GB drive; and my two RAM sticks, each 2 gigs from Corsair. I'd like to know what to run to test these things. I can only find a primitive DOS-based Samsung drive test program. I will run Memtest86+ shortly, though.
Below are the error codes. They have, I think, been consistent across all crashes. Please let me know if you'd like me to post the memory dump or the other file.
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7600
Service Pack: 0_0
Thanks cpatel! As far as CRC, when using bittorrent I've had torrents formerly reported as finished later report as 98.x or 99.x complete. This can be caused by RAM failure to collate the data from different seeders, I'm told, as well as hard drive problems . . . also, there were install errors with some of these torrented programs--strangely, in fact, they would sometimes install with no errors and other times get "corruption" calls (CRC, I think). I suppose that randomness recommends a RAM check, but on the other hand the hard drive did have some errors on it that once.
Right now I'm going to run Memtest86+, but I'm also going to try to do chkdsk's "check for bad sectors" option.
Finally--sorry for the length here--I just installed BlueScreen Viewer and found that several of my earlier crashes were 3b and 7e/7f error codes. I read that both can sometimes be caused by a display driver error. I've installed the drivers that came with my graphics card, though (a Gigabyte Geforce 460GTX 1GB). They're 4-month-old NVIDIA drivers. In fact all of my drivers seem to be up-to-date. My one concern in Device Manager is that the Teredo Tunneling Pseudo-Interface "cannot start," but I've read that this can happen with many ISPs.
Did you ever change the voltages or timings on your Corsair RAM? I have had several issues (due to under-educated OCing attempts) with burning out RAM and MemTest86+ always found the errors for me. Run the test and see if you get errors. Run overnight for sure too; a few hours is not always enough. If you can get a hold of other RAM, do so and try it. You can also try booting up and running with just one of the two sticks.
Luckily, Corsair has one of the best RMA policies out there. Even if only one stick is gone, they will send you two new ones and the turnaround time is pretty quick (a week or so). Post the info above and any info you get from MemTest over on their tech forums (http://forum.corsair.com/v3/forumdisplay.php?f=198) and open a ticket to start the RMA process. They tend to issue you RMA tickets within a few hours of opening a thread if you provide them with the proper data.
I never messed with the RAM or anything else, really. Here's a major new development though:
I have twice--once in Normal Mode and once in Safe Mode--attempted to scan with Avira, and both times the system has crashed with Bccode 24 (as sometimes above). It seemed to crash both times around 70 percent completion. There were 3 detections thus far (both times), but I REALLY think this suggests there is a hard drive error at that spot. The fact chkdsk, when scanning for bad sectors, crashed partway through also suggests this. Any thoughts? I need a way to check the hard drive without crashing it, I think! I'm going to run chkdsk again now and see if it crashes the system again . . .
I will run that next; right now chkdsk is going, and I expect it to crash again partway through.
Things that scan the hard drive somewhat comprehensively--Avira and chkdsk--have crashed the computer 3 out of 3 times, whereas I can play games or watch films for hours on end generally with no crashes (well, maybe once in the 2 weeks it has crashed DURING a game).