BSoD playing certain games, various error codes (usually 0x03b)

[NoelDP]

There's nothing significantly wrong there - unused index entries aren't uncommon.

 

[F5ing]

Yeah, the index problem isn't that significant, although I don't like it when I see that.

The free space marked as allocated is more significant.

 

[msgerbs]

So, what does that mean, practically speaking?

 

[F5ing]

So, what does that mean, practically speaking?

File system issues on that volume. I'd give this a run first:

Of course it could. Now that you mention that, I'm thinking you might want to avoid another chkdsk run for the time being, unless you already have all of your data backed up somewhere else. Instead I'd start with a quick check of that drive by using something like CrystalDiskInfo: CrystalDiskInfo5_1_0.zip. Post a screenshot...

There may not be anything wrong at all. But it's a quick way to see what the HDD's SMART knows about the health of the drive. If it all looks good, then run another chkdsk to see if all errors have been cleaned up.

 

[msgerbs]

DiskInfo says the drive status is good. Attached is a screenshot of the results. Also attached is an example of what Drive Meter looks like whenever I start my computer. (The blue is disk utilization. You can see it hitting 100% for periods of 30 seconds or more) That screenshot was taken about 3 minutes hitting the desktop. Shortly after that, the disk usage subsided. Is it a normal thing to see so much 100% disk utilization for that long after startup? At the time I took that screenshot, desktop icons were just finishing up loading (Granted I do have a lot of them, and several sizable files on my desktop).

Doing anything with windows updates also seems to drive disk utilization to crippling levels for no apparent reason. Even downloading updates in the background can cause problems.

 

[F5ing]

CrystalDisk looks good. Drive appears healthy. Go ahead and run another chkdsk to see if the previous run cleaned everything up.

You can use Resource Monitor to check disk access. It'll tell you what files are being read/written to.

 

[NoelDP]

Yeah, the index problem isn't that significant, although I don't like it when I see that.

The free space marked as allocated is more significant.

You'll almost always get that when the OS frees space from index entries, as it holds the sectors free for the non-existent entries

 

[msgerbs]

chkdsk results:

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 5)...
  534016 file records processed.                                          File verification completed.
  883 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  670988 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  534016 file SDs/SIDs processed.                                         Cleaning up 82 unused index entries from index $SII of file 0x9.
Cleaning up 82 unused index entries from index $SDH of file 0x9.
Cleaning up 82 unused security descriptors.
Security descriptor verification completed.
  68487 data files processed.                                            CHKDSK is verifying Usn Journal...
  36616184 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  534000 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  159405105 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 976657407 KB total disk space.
 338139632 KB in 417519 files.
    229848 KB in 68488 indexes.
         0 KB in bad sectors.
    667503 KB in use by the system.
     65536 KB occupied by the log file.
 637620424 KB available on disk.

      4096 bytes in each allocation unit.
 244164351 total allocation units on disk.
 159405106 allocation units available on disk.

Internal Info:
00 26 08 00 7e 6a 07 00 49 3e 0d 00 00 00 00 00  .&..~j..I>......
36 03 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  6...<...........
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.

 

[NoelDP]

That looks pretty much fine, to me - the lost entries could be because of a BSOD, or a sudden shutdown?

 

[msgerbs]

Probably because of a BSOD or 5.

 

[msgerbs]

I don't know if it helps or not, but twice today League of Legends crashed but didn't immediately BSOD. It only BSOD'd when the process was killed, first by me, then by the LoL bug reporter.

There's gotta be SOMETHING we can do to figure out what's going on here, because it's seriously pissing me off having a $900 gaming rig and being forced to use my laptop with half of the power.

 

[NoelDP]

You may want to read this thread - another one about LoL and crashes.... http://www.sevenforums.com/crashes-...gnal-after-computer-sleeps-3.html#post2199446

 

[msgerbs]

His STOP codes are completely different from mine. My most common one by far is 0x03b, and I don't think he had any of those, and I don't think I've had any of the same as him. I think LoL is poorly-coded which is why it seems to cause latent problems to manifest, pushing barely-stable systems over the edge. It's even given me problems on my laptop, though not nearly this severe.

Anyway, I digress. My problem seems to be different from his, just similar symptoms.

 

[F5ing]

Have you tested the memory you've got installed? I scanned thru the thread and didn't see any reference to a memory test or results.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[msgerbs]

I ran a memory test months ago and passed with flying colors. I'll run one later if I can find the disk I burned.

 

[msgerbs]

I ahve not yet gotten around to running a memory test. However, I recently installed a 240mm high-performance water cooling kit from a popular brand, and when I did so I removed, cleaned, and reseated everything. Since the install, I have not crashed once (That I can remember). I'll post back if I start having problems again. I don't think it was a heat-related issue, but I'm not going to complain if that fixed it.

(Not to say it did not get hot sometimes. I had to warm the die with a hair dryer and pry the CPU off with a screwdriver, because the factory thermal paste was cooked onto the thermal plate of the CPU.)