Blue screen issue - NextGenUpdate
THREAD: Blue screen issue
  1. 11-11-2017, 01:13 AM
    #1
    illusional's Avatar
    illusional
    Gym leader
    illusional's Avatar
    illusional
    Gym leader
    346
    Posts
    1,296
    Reputation
    Nov 2015
    NextGenUpdate
    Sponsored Links

    i have been getting a blue screen after startup of my computer being in sleep mode for awhile i looked at the BlueScreenViewer and i get this

    It has started ever since i updated too the fall update that has recently been released (Windows 10 x64-Bit)

    Spoiler:

    ==================================================
    Dump File : 111017-35171-01.dmp
    Crash Time : 11/10/2017 10:25:29 PM
    Bug Check String : CRITICAL_PROCESS_DIED
    Bug Check Code : 0x000000ef
    Parameter 1 : ffffc205`9df8e5c0
    Parameter 2 : 00000000`00000000
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+163960
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.16299.19 (WinBuild.160101.0800)
    Processor : x64
    Crash Address : ntoskrnl.exe+163960
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\111017-35171-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 16299
    Dump File Size : 692,284
    Dump File Time : 11/10/2017 10:30:10 PM
    ==================================================
  2. Sponsored Links
  3. 11-11-2017, 08:15 PM
    #2
    2,758
    Posts
    34,614
    Reputation
    Feb 2010
    NextGenUpdate
    Originally Posted by illusional View Post
    i have been getting a blue screen after startup of my computer being in sleep mode for awhile i looked at the BlueScreenViewer and i get this

    It has started ever since i updated too the fall update that has recently been released (Windows 10 x64-Bit)

    Spoiler:

    ==================================================
    Dump File : 111017-35171-01.dmp
    Crash Time : 11/10/2017 10:25:29 PM
    Bug Check String : CRITICAL_PROCESS_DIED
    Bug Check Code : 0x000000ef
    Parameter 1 : ffffc205`9df8e5c0
    Parameter 2 : 00000000`00000000
    Parameter 3 : 00000000`00000000
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+163960
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 10.0.16299.19 (WinBuild.160101.0800)
    Processor : x64
    Crash Address : ntoskrnl.exe+163960
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\111017-35171-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 16299
    Dump File Size : 692,284
    Dump File Time : 11/10/2017 10:30:10 PM
    ==================================================
    Likely an issue with your hardware and possibly the drivers for it.
    Quoted Message Blue screen issue
    If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.

    If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.

    Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

    Check with the manufacturer to see if an updated system BIOS or firmware is available.

    You can try running the hardware diagnostics supplied by the system manufacturer.

    Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example, you can get information about required hardware at Windows 10 Specifications.

    Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows, and resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

    Use the System File Checker tool to repair missing or corrupted system files. The System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Use the following command to run the System File Checker tool (SFC.exe) in a command prompt with admin rights.

    SFC /scannow

    For more information, see Use the System File Checker tool to repair missing or corrupted system files.
    Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
    Source: [Only registered and activated users can see links. ]
  4. 11-13-2017, 12:26 AM
    #3
    illusional's Avatar
    illusional
    Gym leader
    illusional's Avatar
    illusional
    Gym leader
    346
    Posts
    1,296
    Reputation
    Nov 2015
    NextGenUpdate
    Originally Posted by Insight View Post
    Likely an issue with your hardware and possibly the drivers for it.


    Source: [Only registered and activated users can see links. ]
    that bluescreen was fixed now i've been getting a few others kinda annoying that i keep getting new ones lol

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •