IRQL, System Service Exception, ntoskernel - Various BSOD  

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 10 Pro
       #1

    IRQL, System Service Exception, ntoskernel - Various BSOD


    Just reformatted to try and escape the blue screens but still they find me. Please bear with me as I'm a verified idiot.

    -Version 1909 (18363.592)

    - - - Updated - - -

    Had another crash so I ran V2 again:

    KMODE_EXCEPTION_NOT_HANDLED
    dxgmms2.sys
    nvlddmkm+0xA7DC0
      My Computer


  2. Posts : 1,539
    Windows 8.1 Enterprise x64
       #2

    1. Enable Driver Verifier Manager through type verifier in search in Start menu
    2. Select "create custom settings (for code developers)"
    3. Tick all standard settings and 2 additional settings (force pending i/o request and irp logging)
    4. Select "Select driver names from a list"
    5. Tick all 3rd party drivers
    6. Apply changes and reboot computer
    7. Wait for next BSODs and send new crash dumps
      My Computer


  3. Posts : 40,987
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    Hi KramDiggity,

    Please perform the following steps:

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) bcdedit /enum {badmemory}

    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    13) Make sure that there is no over clocking while troubleshooting

    14) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10

    15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    16) Uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    17) Re-install the Nvidia GPU driver from the Nvidia website

    18) Make sure that you check the clean install box and if available install the physx driver

    Display Driver Uninstaller Download version 18.0.1.5 (or newer version if available)
    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    Display Driver Uninstaller: How to use - Windows 7 Help Forums

    Download Drivers | NVIDIA
    Download Drivers | NVIDIA

    19) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer


  4. Posts : 12
    Windows 10 Pro
    Thread Starter
       #4

    As instructed by zbook (12):

    Microsoft Windows [Version 10.0.18363.592]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    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.

    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is System.

    Stage 1: Examining basic file system structure ...
    343808 file records processed.
    File verification completed.
    2985 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    19526 reparse records processed.
    450926 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    19526 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    53560 data files processed.
    CHKDSK is verifying Usn Journal...
    36966232 USN bytes processed.
    Usn Journal verification completed.

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

    1952852991 KB total disk space.
    399767296 KB in 283984 files.
    174136 KB in 53561 indexes.
    0 KB in bad sectors.
    508331 KB in use by the system.
    65536 KB occupied by the log file.
    1552403228 KB available on disk.

    4096 bytes in each allocation unit.
    488213247 total allocation units on disk.
    388100807 allocation units available on disk.

    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\MUFASA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition4"'
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\MUFASA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition4"'
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\Windows\system32>10) wmic recoveros get DebugInfoType
    '10)' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\Windows\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\Windows\system32>

    - - - Updated - - -

    As requested by zbook (15):

    Attachment 263786Attachment 263787

    - - - Updated - - -

    Completed the rest of the instructions. Haven't had another BSOD yet, although I did have a complete freeze where I had to press the power button. Here is my current MEMORY.DMP.
      My Computer


  5. Posts : 40,987
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    The commands and results for the dism commands were not present.
    When available please run the commands and post results into the thread.
      My Computer


  6. Posts : 12
    Windows 10 Pro
    Thread Starter
       #6

    Sorry about that:

    Microsoft Windows [Version 10.0.18363.592]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>sfc /scannow

    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.

    C:\Windows\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.592

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.592

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\Windows\system32>sfc /scannow

    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.

    C:\Windows\system32>chkdsk /scan
    The type of the file system is NTFS.
    Volume label is System.

    Stage 1: Examining basic file system structure ...
    343808 file records processed.
    File verification completed.
    2988 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    19527 reparse records processed.
    450832 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    19527 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    53513 data files processed.
    CHKDSK is verifying Usn Journal...
    37562704 USN bytes processed.
    Usn Journal verification completed.

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

    1952852991 KB total disk space.
    400684736 KB in 284496 files.
    174076 KB in 53514 indexes.
    0 KB in bad sectors.
    508847 KB in use by the system.
    65536 KB occupied by the log file.
    1551485332 KB available on disk.

    4096 bytes in each allocation unit.
    488213247 total allocation units on disk.
    387871333 allocation units available on disk.

    C:\Windows\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\MUFASA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition4"'
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\MUFASA\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition4"'
    Property(s) update successful.

    C:\Windows\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\Windows\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\Windows\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\Windows\system32>
      My Computer


  7. Posts : 40,987
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer


  8. Posts : 12
    Windows 10 Pro
    Thread Starter
       #8

    Haven't had another BSOD yet but I'm running prime95 and all workers but one show:

    FATAL ERROR: Rounding was 0.5, expected less than 0.4
    Hardware failure detected, consult stress.txt file.

    Errors from about 2-15 minutes.
      My Computer


  9. Posts : 40,987
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    For all tests / steps please make sure images are posted into the thread.

    Which hardware stress tests were ran and how did you decide to run them?

    This is one method for prime95 testing:
    Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    Prime95 - Stress Test Your CPU
    a) Record the maximum temperature and post the maximum temperature into the thread
    b) Record test duration and post the uninterrupted test duration into the thread
    c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10

    This is a link for the Intel processor diagnostic tool (IPDT)
    Download Intel(R) Processor Diagnostic Tool

    This is another software to stress test hardware: OCBASE / OCCT
      My Computer


  10. Posts : 12
    Windows 10 Pro
    Thread Starter
       #10

    Previously I ran the Blend test on all 8 threads and was consistently and quickly failing. Currently (after a restart) running the Small FFTs test as recommended in the link with no errors so far (15 minutes). CPU package temp steady around 75C. I'll post again after a failure or 3 hours.

    Should I stop the test after a single worker failure or wait for all 8 (or 3 hours)?
    Is it okay to run other programs while stress testing?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:32.
Find Us




Windows 10 Forums