BSOD ntoskrnl.exe CRITICAL_PROCESS_DIED

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 10 Home 10.0.16299 64bit
       #1

    BSOD ntoskrnl.exe CRITICAL_PROCESS_DIED


    Hi guys!

    Recently I've been repeatedly getting BSODs, of which I do not know the cause. It happens sometimes when I wake the computer from sleep (open the lid, screen unresponsive and remains black, and then reboots), or when I am using the computer and everything suddenly starts getting laggy and unresponsive.

    Minidump files are created, DM log collector runs successfully to completion but no zip file is created, be it on the Desktop or in any other location. I've tried running it as Administrator, taking ownership of the dump file, but only a temp.txt and a _zipIt.vbs (tried running the vbs alone, but there's an error) is created.

    As such, I've only attached the minidump file directly. Sorry :/

    Specs: Windows 10 64bit, ASUS Motherboard, NVIDIA GeForce GTX 1060.

    Thanks in advance!
    Last edited by cabbagething; 11 Dec 2017 at 02:08.
      My Computer


  2. Posts : 5,184
    64bit Win 10 Pro ver 21H2
       #2

    Hello cabbagething and welcome to TenForums :)

    It's possible that your anti-virus package may be preventing the logfile collector from completing its operation. Try temporarily stopping your AV and see if it will then work.

    Please can you fill in as many details as possible about you system in the My Computerarea of your profile.
      My Computers


  3. Posts : 9
    Windows 10 Home 10.0.16299 64bit
    Thread Starter
       #3

    I have disabled both my antiviruses, but unfortunately DM log collector still fails to work. Just for additional info, running _zipIt.vbs alone gives the Microsoft VBScript runtime error: Subscript out of range, code: 800A009. I assume this script is used by the log collector.

    I have also included more detailed system specs. Let me know if more is needed!
      My Computer


  4. Posts : 10,545
    Windows 10 Workstation x64
       #4

    Try this log collector instead

    Attachment 167739
      My Computers


  5. Posts : 9
    Windows 10 Home 10.0.16299 64bit
    Thread Starter
       #5

    Ok, I have finally got it working :)
      My Computer


  6. Posts : 5,184
    64bit Win 10 Pro ver 21H2
       #6

    Unfortunately your report shows that you are using improperly activated software (probably includes MSOffice, and a bunch of others too!)
    This forum's Rules clearly state that help will not be provided to those using Non genuine software installations.

    Rule 4
    No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.

    One of the main reasons for this is that the act of pirating the software will inevitably change the working of the software and make investigation and repair impossible. Please install a legitimate copy of the software and if you are still experiencing the issue we will be pleased to assist - No further assistance will be provided until we are satisfied that the software is genuine.
      My Computers


  7. Posts : 9
    Windows 10 Home 10.0.16299 64bit
    Thread Starter
       #7

    I have attempted to remove the piracy software on my laptop. Attached is the new report log, let me know if there are still any remnants!
      My Computer


  8. Posts : 9
    Windows 10 Home 10.0.16299 64bit
    Thread Starter
       #8

    I got another BSOD while attempting to wake the computer up from sleep. This time bug check code is 0x0000010e, caused by driver watchdog.sys, caused by address watchdog.sys+3330.

    Crash address is ntoskrnl.exe+1640e0.

    Besides watchdog.sys, dxgmms2.sys (dxgmms2.sys+17011) Microsoft® Windows® Operating System DirectX Graphics MMS is also highlighted in red. These information are obtained from Nirsoft's BlueScreenView to analyze the minidump.
      My Computer


  9. Posts : 13,955
    Windows 10 Pro X64 21H1 19043.1503
       #9

    Always post a new zip when you get a new BSOD.
      My Computers


  10. Posts : 9
    Windows 10 Home 10.0.16299 64bit
    Thread Starter
       #10

    Ah garbage, I didn't act fast enough and the two minidumps have already been automatically deleted (encountered another BSOD while using the laptop after the one caused by watchdog.sys, this one was back to ntoskrnl.exe CRITICAL_PROCESS_DIED.)

    Not sure if the log collector zip would still be useful, sorry
      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 16:20.
Find Us




Windows 10 Forums