BSODs random (WACHTDOG, IRQL...)

  1.    #1

    BSODs random (WACHTDOG, IRQL...)


    Hi,

    Since January, when I made some changes in hardware (cpu, motherboard) to my PC, I started having problems with BSODs and sudden reboots. The best way that I can repeat BOSds is playing a game and listening music in Youtube.

    All these months, I've tried everything, changing RAM, CPU, PSU, etc... Without results. Sometimes_DPC WATCHDOG_VIOLATION BSOD appears, and other times IRQL_NOT_LESS_OR_EQUAL BSOD... and occasionally it freezes suddenly. Attach the ZIP file!

    Thanks for the assistance!
    BSODs random (WACHTDOG, IRQL...) Attached Files
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 8,479
    Windows 10 Pro X64 1903 189362.439
       #2

    Looks like you have a MSI MPG Z390 GAMING PRO CARBON AC (MS-7B17) motherboard.
    BIOS is at the 1.50 version. I think that is the latest 7B17v15 but I'm not certain. Please check.

    Click image for larger version. 

Name:	image.png 
Views:	37 
Size:	4.1 KB 
ID:	242221

    According to V2 log data:

    Crash dump found at C:\Windows\MEMORY.DMP
    Creation date: 08/04/2019 08:10:11
    Size on disk: 715 MB

    Please copy MEMORY.DMP to another location, zip it and upload to a file sharing site like OneDrive then post a link to it here so I can download it. The minidump doesn't have enough info in it to be of any use.

    Edit: Also, since it sounds like you've replaced everything but the motherboard, sorry to say but you need to think about that as the next hardware replacement. Let's try Driver Verifier next:

    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The desired result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.

    Machines exposed to Driver Verifier may run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    More information here: Driver Verifier-- tracking down a mis-behaving driver.

    warning   Warning
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.


    Always create a Restore Point prior to enabling Driver Verifier so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
      My ComputersSystem Spec


  3. Posts : 271
    Windows 8.1 Enterprise x64
       #3
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 8,479
    Windows 10 Pro X64 1903 189362.439
       #4

    @MrPrepka Great minds ....

    I like the tutorial better than my stuff, Will use it from now on.
      My ComputersSystem Spec

  5.    #5

    Ztruker said: View Post
    Looks like you have a MSI MPG Z390 GAMING PRO CARBON AC (MS-7B17) motherboard.
    BIOS is at the 1.50 version. I think that is the latest 7B17v15 but I'm not certain. Please check.

    Click image for larger version. 

Name:	image.png 
Views:	37 
Size:	4.1 KB 
ID:	242221

    According to V2 log data:

    Crash dump found at C:\Windows\MEMORY.DMP
    Creation date: 08/04/2019 08:10:11
    Size on disk: 715 MB

    Please copy MEMORY.DMP to another location, zip it and upload to a file sharing site like OneDrive then post a link to it here so I can download it. The minidump doesn't have enough info in it to be of any use.

    Edit: Also, since it sounds like you've replaced everything but the motherboard, sorry to say but you need to think about that as the next hardware replacement. Let's try Driver Verifier next:

    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The desired result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.

    Machines exposed to Driver Verifier may run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    More information here: Driver Verifier-- tracking down a mis-behaving driver.

    warning   Warning
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.


    Always create a Restore Point prior to enabling Driver Verifier so you have a way to recover if it goes haywire. Seldom does but it can happen.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
    First of all, thanks for your reply! @Ztruker @MrPepka

    The MEMORY.DMP zip file is here: https://mega.nz/#!Q1hiiQpa!X7LxvQ-hV...pP3p2HW_jisWPI

    And about the BIOS is true, the other day I reset it, and forgot to update it again. I have already done it (and BSODs are still produced). And I replaced the motherboard with another one that was the same; through the amazon replacement program.

    And now, Driver Verifier is running, thanks!

    I will keep you informed.
      My ComputerSystem Spec

  6.    #6

    Hi,
    I ran the Driver Verifier, as recomended, for 48 hours and no BSOD's or reboots were produced.

    But if try to play a game and listen to music in YouTube the same problems of BSOD's and reboots reappear. However, now more freezes are produced than before.

    What happens is that the screen image freezes, the keyboard does not respond and the only possible solution is to turn it off from the power supply.

    Do you have any idea of what could be going wrong?

    Thanks!
      My ComputerSystem Spec



  7. Posts : 26,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    Windows driver verifier has customiztions for tests.
    In the link that was used there were 3 simultaneous customized tests.

    In this link there are approximately 19 simultaneous customized tests:
    https://answers.microsoft.com/en-us/...9e4c983?auth=1

    The more the number of simultaneous tests the greater the likelihood of an impact on computer performance and/or boot.

    Make a new restore point:
    Create System Restore Point in Windows 10

    Increase the number of simultaneous tests by 3 to 5 per hour.
    If there are performance or slow boot problems then uncheck the tests that were already performed.
    Over the next 48 hours expose all non-Microsoft drivers to the 19 customized tests.

    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

    If there are no BSOD after testing the additional 16 tests over 48 hours then test the RAM with Memtest86 version 8.2.
    Run two separate tests with 4 passes each.
    Find a camera or smartphone camera to take pictures and post images into the thread.
    For each test post share links using one drive, drop box, or google drive for:
    a) an image of the test results
    b) text report (see software menu)
      My ComputerSystem Spec


  8. Posts : 271
    Windows 8.1 Enterprise x64
       #8

    If there is no BSoD Driver Verifier then it is probably a hardware problem. Did you write that the problem appeared after changing components (specifically CPU and motherboard) or did you test the processor with Prime95, OCCT and Intel Processor Diagnostic Tool? If not, it's worth doing it
      My ComputerSystem Spec


 

Related Threads
Hi, I've been encountering frequent BSODs / game crashes during heavy loads. My system is fairly new and I'm desperate for some help. Hardware: Mobo: ASRock Z270 Killer SLI/ac Drive: 2 x Samsung EVO 960 500GB (not raid) CPU: Intel Core i7...
BSOD @ random, DRIVER IRQL NOT LESS OR EQAL in BSOD Crashes and Debugging
Hi, I've recently reinstall Win10 Home on a company laptop (Sony Vaio, without domain). Problem occurs at random but usually while I try to add network printer from control panel creator menu. I suspect WiFi card and/or Eset Endpoint AV v6....
Hi, After every few random days I am getting BSOD with the title mentioning "IRQL NOT LESS OR EQUAL. FYI, This is a completely new built and only 2 months in use. Currently not using for gaming so no graphics card in it. Using Windows 10. My...
Hi, I would really appreciate it if anyone could shed any light on this. The PC was originally Windows 7 and I upgraded to Windows 10 last year. The crashes seem to be random, sometimes when it's sitting idle, sometimes whilst I'm working. ...
Random BSODs, Driver IRQL ETD.sys in BSOD Crashes and Debugging
Hello, I have been getting random BSODs for weeks now and I am totally clueless on what to do. The BSOD Message is : DRIVER_IRQL_NOT_LESS_OR_EQUAL (ETD.sys) Recently updated to windows 10. I cant seem to remember if the BSODs begun before I...
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 20:05.
Find Us