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

Discus and support BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl in Windows 10 BSOD Crashes and Debugging to solve the problem; sfc found issues so restarting and doing it again... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by vikhik, Oct 3, 2015.

Page 3 of 7
  1. VIKHIK
    vikhik Win User

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


    sfc found issues so restarting and doing it again...
     
    vikhik, Oct 9, 2015
    #31
  2. VIKHIK
    vikhik Win User

    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? *Smile
     
    vikhik, Oct 9, 2015
    #32
  3. VIKHIK
    vikhik Win User
    Hmm. Apparently no dice. Crashed again playing MGS. Here's the log collection: Attachment 41991
     
    vikhik, Oct 9, 2015
    #33
  4. VIKHIK
    vikhik Win User

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

    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, Oct 9, 2015
    #34
  5. VIKHIK
    vikhik Win User
    vikhik, Oct 9, 2015
    #35
  6. AXE0
    axe0 New Member
    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[/quote] Please test your hard drive(s)




    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]
    Diagnostics Test
    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]
    HDD & SSD TEST

    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]
    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums


    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]
    Note Do not run SeaTools on an SSD as the results will be invalid.


    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]
    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[/quote] Please fill in your system specsPlease 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:

    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]


    BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl [​IMG]
     
    axe0, Oct 9, 2015
    #36
  7. VIKHIK
    vikhik Win User
    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.
     
    vikhik, Oct 9, 2015
    #37
  8. AXE0
    axe0 New Member

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

    Not likely, more a driver problem.
     
    axe0, Oct 9, 2015
    #38
  9. VIKHIK
    vikhik Win User
    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~2of 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.ETLof 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, Oct 9, 2015
    #39
  10. VIKHIK
    vikhik Win User
    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?
     
    vikhik, Oct 9, 2015
    #40
  11. AXE0
    axe0 New Member
    Please perform the long generic test in SeaTools
     
    axe0, Oct 9, 2015
    #41
  12. AXE0
    axe0 New Member
    You can downgrade to 7 via multiple ways. However, the ways of Microsoft will give you more/other problems
     
    axe0, Oct 9, 2015
    #42
  13. AXE0
    axe0 New Member

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

    Tomorrow I'll check for drivers that need updating.
     
    axe0, Oct 10, 2015
    #43
  14. AXE0
    axe0 New Member
    There are just 2 drivers dating a little old.
    Please check Realtek for the audio driver and Qualcomm for the network driver updates
    Code: 2: kd> lmvm RTKVHD64 start end module name fffff800`238d0000 fffff800`23c84380 RTKVHD64 (deferred) Image path: RTKVHD64.sys Image name: RTKVHD64.sys Timestamp: Tue Mar 11 13:56:41 2014 (531F0809) CheckSum: 003B9623 ImageSize: 003B4380 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 2: kd> lmvm athuw8x start end module name fffff800`23cf0000 fffff800`24089000 athuw8x (deferred) Image path: athuw8x.sys Image name: athuw8x.sys Timestamp: Mon Oct 15 13:08:55 2012 (507BEEC7) CheckSum: 003956BB ImageSize: 00399000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
     
    axe0, Oct 10, 2015
    #44
  15. VIKHIK
    vikhik Win User
    Updated the Realtek driver... It doesn't seem like there is an updated driver for my wireless dongle... (Atheros AR7105). I'm going to uninstall the driver and do without the ability to Chromecast and see if that helps.
     
    vikhik, Oct 11, 2015
    #45
Page 3 of 7
Thema:

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

Loading...

  1. BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl - Similar Threads - BSOD playing MGSV

  2. BSOD when playing Dota 2 but not other games

    in Windows 10 Gaming
    BSOD when playing Dota 2 but not other games: This is the report from Reliability Monitor Source Windows Summary Shut down unexpectedly Date ‎4/‎4/‎2020 8:49 PM Status Not reported Problem signature Problem Event Name: BlueScreen Code: 124 Parameter 1: 0 Parameter 2: ffffca0e31c03028 Parameter 3: be000000 Parameter 4:...

  3. Recurring BSOD playing Dota 2 Driver IRQL not less not equal ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    Recurring BSOD playing Dota 2 Driver IRQL not less not equal ntoskrnl: Hi Guys, I've been encountering multiple BSODs while playing dota 2. The latest set of BSODs are Driver IRQL not less not equal. I've reinstalled my graphic drivers and several hardware drivers. I don't encounter BSOD if I play other games. hope you can help me out. Thanks...

  4. BSOD playing DOTA 2 & SIM CITY

    in Windows 10 BSOD Crashes and Debugging
    BSOD playing DOTA 2 & SIM CITY: Dear axe0, In accordance with a request to create a new thread. The problem I faced when I was migrating to Windows 10 is I can not get DOTA 2. When installing the update then happens BSOD. I read some threads in this forum but I can not. Similarly, when I play SIM CITY...

  5. BSOD rate increase while play DOTA 2

    in Windows 10 BSOD Crashes and Debugging
    BSOD rate increase while play DOTA 2: im new here, and i think you guys can solved my problem i bought a new PC and fresh install it with windows 10, then the bsod come it keep happening to my pc. then i decide to upgrade my windows 10 to windows 10 pro but bsod stand still. the problem is when i play dota 2...

  6. BSOD on playing Dota 2, error ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

    in Windows 10 BSOD Crashes and Debugging
    BSOD on playing Dota 2, error ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY: My laptop is a Dell XPS 15 9550. Never had BSODs (in any other programs, including more demanding games like Witcher 3) until I installed Dota 2 and started having random BSODs during certain games. The most recent ones are of "ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" (which...

  7. BSOD When i play DOta 2

    in Windows 10 BSOD Crashes and Debugging
    BSOD When i play DOta 2: During nearly every match my game would freeze and cause a machine check exception, just happends in dota, I can play other games Like GTA V without issue, but Dota. First I thought it was overheat issue cuz the temperature was at 65°, now i boosted my fans and i got 50°...

  8. BSOD playing Dota 2 WHEA_UNCORRECTABLE_ERROR

    in Windows 10 BSOD Crashes and Debugging
    BSOD playing Dota 2 WHEA_UNCORRECTABLE_ERROR: I bought this Lenovo Ideapad Y700-15ISK laptop in September, got the occasional BSoD until I updated BIOS. Today I got 4-6 of these BSODs with the WHEA_UNCORRECTABLE_ERROR while trying to play Dota 2. I have previously run multiple programs, perhaps I've overworked the...

  9. BSOD playing dota 2

    in Windows 10 BSOD Crashes and Debugging
    BSOD playing dota 2: Guys help me please... My laptop keep Bsod especially when playing dota 2 I got different BSOD everytime 1. irql_not_less_or_equal 2. system service exception dxgmms1.sys 3. dpc watchdog violation and many many more... Here is my minidump : Dropbox - minidump...

  10. BSOD While Playing dota 2

    in Windows 10 BSOD Crashes and Debugging
    BSOD While Playing dota 2: Hi there. i've been getting this blue screen Death for couple of days , i've never experienced this before , i am using windows 10 pro 64bits, i've changed the whole windows for the BSOD but still i keep getting the blue screen while playing dota 2, any help woulAttachment...