BSOD (Again)
-
So memtest86+ on the second stick came up with lots of errors. Weird cos it didn't before and I did 6 passes but I guess that's life. I guess I'll have to RMA this one too. Hopefully, if I boot with just the 1 stick it won't blue screen. Should be a good test of the RAM. I might see if the guys at Newegg will refund me and let me have other RAM, 2 defective sticks out of 4 is pretty bad.
-
-
Yes, sometimes it will run twice. The log should show up in Event Viewer under Application. Look for the wininit entry.
It certainly will not hurt to run the manufacturers' hard drive checkers. These are much more thorough than Check Disk.
Indeed, two bad sticks out four is bad; but it does happen. Don't for get to test you motherboard slots with the good stick. Post back with how your computer does on the one good stick.
-
I'll do some disk checks now, I'll have to RMA that RAM though. I guess the fact it didn't show errors the first time was just a fluke? It definitely seems bad now. Hopefully it was this that was the cause. I'll let you know.
-
-
Memtest is not 100% perfect. It is not unusual for it to miss something the first time or even miss it altogether. We have seen this happen before.
-
![]()
My chkdsk results, there are a couple of inconsistencies;
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 3)...
211200 file records processed. File verification completed.
281 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
266716 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
The hash value 0xc2a48011 of the security descriptor entry with Id
0x15c at offset 0x5110 is invalid. The correct value is 0xc2a48019.
The hash value 0xc0e6f51d of the security descriptor entry with Id
0x246 at offset 0x10ff0 is invalid. The correct value is 0xc0eaf51d.
Repairing the security file record segment.
211200 file SDs/SIDs processed. Cleaning up 77 unused index entries from index $SII of file 9.
Cleaning up 77 unused index entries from index $SDH of file 9.
Cleaning up 77 unused security descriptors.
Security descriptor verification completed.
27759 data files processed. CHKDSK is verifying Usn Journal...
35685712 USN bytes processed. Usn Journal verification completed.
Windows has made corrections to the file system.
976657407 KB total disk space.
37704660 KB in 182952 files.
89840 KB in 27760 indexes.
0 KB in bad sectors.
342387 KB in use by the system.
65536 KB occupied by the log file.
938520520 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
234630130 allocation units available on disk.
Internal Info:
00 39 03 00 23 37 03 00 af 98 05 00 00 00 00 00 .9..#7..........
9a 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
-
The chkdsk results for the other drive, all ok by the looks of it;
Checking file system on D:
The type of the file system is FAT32.
A disk check has been scheduled.
Windows will now check the disk.
Volume Serial Number is DD94-6957
Windows is verifying free space...
Free space verification is complete.
Windows has checked the file system and found no problems.
976513536 KB total disk space.
118496 KB in 3596 hidden files.
105984 KB in 3308 folders.
522518720 KB in 37721 files.
453770304 KB are available.
32768 bytes in each allocation unit.
30516048 total allocation units on disk.
14180322 allocation units available on disk.
-
-
Alderosa
A quick question.
Why is that drive formatted FAT32??
-
It's an external hard drive from about 4 years ago and the power supply to it (transformer) broke so I bunged it into this PC when I set it up. I didn't have a large drive (till I bought the main one for this PC) to transfer the stuff on it to and reformat (which I've been meaning to do) but I've got bigger fish to fry at the moment in terms of trouble shooting!
What do you think of the results for the other drive posted above the FAT32 one? Is there anything to worry about?
Hopefully it is just the RAM that's defective and been causing my problem. I should know tomorrow morning if it BSODs on the first boot of the day again. The RAM in it now (1 stick of 2Gb) has gone through 2 memtests of 6 passes each so hopefully it is actually good. I'm going to have to return it though and tbh I think I'm going to get a different brand. I'll reformat the hard disk when the other issues are sorted, unless you think it might be a problem?
-
Just had results of SFC check, no problems reported.
-
Drive C: looks fine. There were a few things wrong in the file system; but Check Disk fixed them. There are no bad sectors - that is a good thing. It is a good idea to run Check disk every now and then to keep the file system in good shape. And if you start seeing many bad sectors popping up, that may be a sign the hard drive is on its way out. A few bad sectors is normal. Drive D: is fine. I, too, was surprised to see it was FAT32.
Quote