BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl

vikhik · 09 Oct 2015

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

---

Am I done? :)

vikhik · 09 Oct 2015

Hmm. Apparently no dice. Crashed again playing MGS. Here's the log collection: Attachment 41991

vikhik · 09 Oct 2015

I ran Furmark for ages, following the tenforums guide, and no issues happened until I tried to get a screenshot after 45 minutes.
Attachment 42012

vikhik · 09 Oct 2015

I just used the Display Driver Uninstaller (Display Driver Uninstaller Download version 15.5.1.0) and re-installed the latest drivers. That apparently sometimes helps with W10/NVIDIA cards.

axe0 · 10 Oct 2015

Please check the frequency of the RAM in the BIOS and make sure it is supported by the motherboard.

Code:

BugCheck A, {ffffe00174c00848, 2, 0, fffff802b0e236ca}


Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1ea )


Followup: MachineOwner
---------


2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffe00174c00848, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802b0e236ca, address which referenced memory

Please test your hard drive(s)

Diagnostics Test

HDD & SSD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk Disk Check - Windows 7 Help Forums

Code:

STACK_TEXT:  
ffffd000`2354ad48 fffff801`dd617908 : 00000000`0000001e ffffffff`c0000005 fffff800`6fdcf4a6 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2354ad50 fffff801`dd5e8c82 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2ab08
ffffd000`2354b430 fffff801`dd5e717e : 00000000`00000002 fffff801`dd932a66 ffffe000`c68fa010 00000000`00000001 : nt!KiExceptionDispatch+0xc2
ffffd000`2354b610 fffff800`6fdcf4a6 : 00000000`000000f8 fffff801`00000001 ffffe000`c65f4bd8 ffffd000`2354beb0 : nt!KiGeneralProtectionFault+0xfe
ffffd000`2354b7a0 fffff800`6fdcea0e : ffffd000`2234cab8 ffffc000`fc649ac0 ffffd000`2354beb0 ffffd000`2354beb0 : NTFS!NtfsCreateScb+0x106
ffffd000`2354b880 fffff800`6fdab123 : ffffd000`2234ca40 ffffe000`c65f4880 ffffe000`c6874f01 ffffc000`fc4fc420 : NTFS!NtfsBreakBatchOplock+0xae
ffffd000`2354b900 fffff800`6fdaa875 : ffffd000`2234ca40 00000000`00000001 ffffc000`fc649ed0 ffffc000`0000001e : NTFS!NtfsOpenExistingAttr+0x93
ffffd000`2354b9d0 fffff800`6fda99ed : ffffd000`2234ca40 ffffe000`c65f4880 ffffc000`fc649ed0 00000000`0000001e : NTFS!NtfsOpenAttributeInExistingFile+0x135
ffffd000`2354bb90 fffff800`6fdd10ae : ffffe000`c6541dc8 ffffc000`fc649ac0 ffffc000`fc649ed0 00000000`00000000 : NTFS!NtfsOpenExistingPrefixFcb+0x1ed
ffffd000`2354bc80 fffff800`6fdd1d8a : ffffe000`c6541dc8 ffffe000`c65f4880 ffffe000`c6541dc8 ffffd000`2354beb0 : NTFS!NtfsFindStartingNode+0x58e
ffffd000`2354bd40 fffff800`6fdd182d : ffffe000`c6541dc8 ffffe000`c65f4880 ffffd000`2234ca40 ffffe000`c641ad01 : NTFS!NtfsCommonCreate+0x52a
ffffd000`2354bf50 fffff801`dd5e0da7 : ffffd000`2234c9f0 00000000`02e4ea78 00000000`00000000 00000000`02e4eb41 : NTFS!NtfsCommonCreateCallout+0x1d
ffffd000`2354bf80 fffff801`dd5e0d6d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
ffffd000`2234c830 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.

How to fill in your system specs:

vikhik · 10 Oct 2015

I checked the frequency support, again, and it's just fine.

How likely is it that the Mobo is faulty?

Doing disk checks now.

Added (slightly) more info to my rig spec.

axe0 · 10 Oct 2015

Not likely, more a driver problem.

vikhik · 10 Oct 2015

Ran the SeaTools for Windows Fix All (Fast), no issues found (Fix All Fast - Passed, 100%).

CHKDSK for my SSD (Windows):

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:

Volume label is Windows.

Stage 1: Examining basic file system structure ...

226816 file records processed. File verification completed.

4594 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...

Found an unneeded link ($FILE_NAME: "REPORT~2") in index "$I30" of directory "\ProgramData\Microsoft\Windows\WER <0x1,0x543>"

... repaired online.

Found an unneeded link ($FILE_NAME: "ETWRTE~1.ETL") in index "$I30" of directory "\Windows\System32\LogFiles\WMI\RtBackup <0x1,0x1327>"

... repaired online.

309120 index entries processed. Index verification completed.

Stage 3: Examining security descriptors ...

Security descriptor verification completed.

41153 data files processed. CHKDSK is verifying Usn Journal...

40215776 USN bytes processed. Usn Journal verification completed.

Windows has found problems and they were all fixed online.

No further action is required.

243684351 KB total disk space.

71893992 KB in 180212 files.

112164 KB in 41154 indexes.

341115 KB in use by the system.

65536 KB occupied by the log file.

171337080 KB available on disk.

4096 bytes in each allocation unit.

60921087 total allocation units on disk.

42834270 allocation units available on disk.

----------------------------------------------------------------------

Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Unable to locate the file name attribute of index entry REPORT~2

of index $I30 with parent 0x543 in file 0x545.

Deleting index entry REPORT~2 in index $I30 of file 1347.

Unable to locate the file name attribute of index entry ETWRTE~1.ETL

of index $I30 with parent 0x1327 in file 0xa2f8.

Deleting index entry ETWRTE~1.ETL in index $I30 of file 4903.

Stage 3: Examining security descriptors ...

CHKDSK for my HDD (Data):

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on D:
Volume label is Data.

Stage 1: Examining basic file system structure ...

273152 file records processed. File verification completed.

1386 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...

343532 index entries processed. Index verification completed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.

35191 data files processed. CHKDSK is verifying Usn Journal...

36899456 USN bytes processed. Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

2861458 MB total disk space.
129642328 KB in 241749 files.
65756 KB in 35192 indexes.
464827 KB in use by the system.
65536 KB occupied by the log file.
2734337 MB available on disk.

4096 bytes in each allocation unit.
732533503 total allocation units on disk.
699990276 allocation units available on disk.

----------------------------------------------------------------------

Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...

Windows has scanned the file system and found no problems.
No further action is required.

vikhik · 10 Oct 2015

I've been doing some sniffing around, apparently it's common for people with NVIDIA cards on W10 to have these kinds of issues.

Can I/Should I downgrade to W7?

axe0 · 10 Oct 2015

Please perform the long generic test in SeaTools