BSOD seemingly randomly

Pwnskies · 19 Sep 2013

Hello I have been having random BSOD issues with my computer ever since my brother gave it to me about a year ago and I really don't know what the problem is. It happens pretty infrequently maybe once in a gaming session sometimes everything is fine or it will just BSOD while it's just sitting there doing nothing. I am not really sure what the issue is at all so I don't know what information to provide really I attatched the SF_Pwnskies file like the guide said but if I need to provide more information let me know. I would really appreciate any help I can get!

YoYo155 · 19 Sep 2013

Welcome to SF :) .
You uploaded a limited set of information, only one bugcheck and three out of the eight the SFDT
generates normally so please run the tool again and let it run for 10-15 minutes
in order to have a broader view of the system.

From what you have uploaded I can tell you this.

Your Event log is full (or at least part of which the tool managed to export) of file system errors.

Code:

Event[8525]:
  Log Name: System
  Source: Ntfs
  Date: 2012-11-29T22:34:48.082
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Nick-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.

Event[8526]:
  Log Name: System
  Source: Ntfs
  Date: 2012-11-29T22:34:48.084
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Nick-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.

We will know more once we will have all the files.

As for the bugcheck, the parameters it is displaying are typical for a driver fault.

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa800025a1c0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Code:

dt nt!_mmpfn fffffa800025a1c0
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40000408 _MMPTE
   +0x010 VolatilePteAddress : 0xfffff6fb`40000408 Void
   +0x010 Lock             : 0n1073742856
   +0x010 PteLong          : 0xfffff6fb`40000408
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>

I recommend testing the HDD.

Warning

Do not perform these steps on an SSD!

Testing the HDD:

Perform a Disk Check | Disk Check
Then Post the results following | THIS METHOD
Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If the HDD passes all the tests above run Driver Verifier:

Arc said:

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Pwnskies · 20 Sep 2013

Sorry about that I didn't know it wasn't finished running haha! This time it told me it was done and to upload it to the forums so this should be better. I will go ahead and start doing the other stuff you said while I wait. Thanks a lot for the help!

Pwnskies · 20 Sep 2013

I am not sure if I am supposed to upload a file or just copy paste the results of the disk check so I just chose to copy and paste it!

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)...
251648 file records processed. File verification completed.
Deleting orphan file record segment 61607.
704 large file records processed. 0 bad file records processed. 0 EA records processed. 76 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
Index entry ais_dll_eng-4f2.vpx of index $I30 in file 0xf095 points to unused file 0xf0a7.
Deleting index entry ais_dll_eng-4f2.vpx in index $I30 of file 61589.
Index entry AIS_DL~1.VPX of index $I30 in file 0xf095 points to unused file 0xf0a7.
Deleting index entry AIS_DL~1.VPX in index $I30 of file 61589.
Index entry SE9794~1.TXT of index $I30 in file 0x3a75a points to unused file 0xf0a5.
Deleting index entry SE9794~1.TXT in index $I30 of file 239450.
Index entry serverbrowser_korean.txt of index $I30 in file 0x3a75a points to unused file 0xf0a5.
Deleting index entry serverbrowser_korean.txt in index $I30 of file 239450.
331822 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
251648 file SDs/SIDs processed. Cleaning up 233 unused index entries from index $SII of file 0x9.
Cleaning up 233 unused index entries from index $SDH of file 0x9.
Cleaning up 233 unused security descriptors.
Security descriptor verification completed.
40088 data files processed. CHKDSK is verifying Usn Journal...
35190416 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

312466431 KB total disk space.
252160840 KB in 204368 files.
104412 KB in 40089 indexes.
0 KB in bad sectors.
362995 KB in use by the system.
65536 KB occupied by the log file.
59838184 KB available on disk.

4096 bytes in each allocation unit.
78116607 total allocation units on disk.
14959546 allocation units available on disk.

Internal Info:
00 d7 03 00 f4 ba 03 00 49 b6 06 00 00 00 00 00 ........I.......
3d 03 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 =...L...........
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.

Let me know if that wasn't what I was supposed to do!

Pwnskies · 21 Sep 2013

My computer passed the long and short test from seatools and doesn't seem to be crashing during the stress test, I've been doing the driver verifier for 12 hours and it hasn't crashed so far.