locked
WerFault.exe RRS feed

  • Question

  • Anyone have an idea what below means. I've been crashes whenever playing games regarding my Graphics Hardware according to the Event View information. I've tried everything from Tdr setting in registry, to graphics settings, to underclocking gpu, to new GPU, fresh windows install, etc. I've RMA'd my GPU as well as full windows reinstall and I still get crashes within the error which leads me to believe it may be hardware related, but I can't tell. Whenever I crash in games, it seems it always follows a LiveKernalEvent error in Event Viewer. Is there any way to tell which component could be causing this, or any software? I've ran dism/sfc scan/chkdsk/memtest/cpu and gpu bencharmarks and were all fine. I've replaced PSU, played games with each RAM stick individually, RMA'd GPU where both graphics card were crashing with same error.  

    Version=1
    EventType=LiveKernelEvent
    EventTime=132362272742669934
    ReportType=4
    Consent=1
    ReportStatus=2049
    ReportIdentifier=43b0c54d-dc23-447a-a7b1-e42d08a60c73
    Wow64Host=34404
    NsAppName=LiveKernelEvent
    OriginalFilename=WerFault.exe
    AppSessionGuid=00000000-0000-0000-0000-000000000000
    BootId=41
    IsFatal=4294967295
    EtwNonCollectReason=1
    Response.type=4
    Sig[0].Name=Code
    Sig[0].Value=142
    Sig[1].Name=Parameter 1
    Sig[1].Value=ffff9d0fcfdcd460
    Sig[2].Name=Parameter 2
    Sig[2].Value=fffff80477272610
    Sig[3].Name=Parameter 3
    Sig[3].Value=0
    Sig[4].Name=Parameter 4
    Sig[4].Value=2d98
    Sig[5].Name=OS version
    Sig[5].Value=10_0_18363
    Sig[6].Name=Service Pack
    Sig[6].Value=0_0
    Sig[7].Name=Product
    Sig[7].Value=256_1
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.18363.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    OsInfo[0].Key=vermaj
    OsInfo[0].Value=10
    OsInfo[1].Key=vermin
    OsInfo[1].Value=0
    OsInfo[2].Key=verbld
    OsInfo[2].Value=18363
    OsInfo[3].Key=ubr
    OsInfo[3].Value=836
    OsInfo[4].Key=versp
    OsInfo[4].Value=0
    OsInfo[5].Key=arch
    OsInfo[5].Value=9
    OsInfo[6].Key=lcid
    OsInfo[6].Value=1033
    OsInfo[7].Key=geoid
    OsInfo[7].Value=244
    OsInfo[8].Key=sku
    OsInfo[8].Value=48
    OsInfo[9].Key=domain
    OsInfo[9].Value=0
    OsInfo[10].Key=prodsuite
    OsInfo[10].Value=256
    OsInfo[11].Key=ntprodtype
    OsInfo[11].Value=1
    OsInfo[12].Key=platid
    OsInfo[12].Value=10
    OsInfo[13].Key=sr
    OsInfo[13].Value=0
    OsInfo[14].Key=tmsi
    OsInfo[14].Value=57618
    OsInfo[15].Key=osinsty
    OsInfo[15].Value=2
    OsInfo[16].Key=iever
    OsInfo[16].Value=11.836.18362.0-11.0.190
    OsInfo[17].Key=portos
    OsInfo[17].Value=0
    OsInfo[18].Key=ram
    OsInfo[18].Value=32717
    OsInfo[19].Key=svolsz
    OsInfo[19].Value=488
    OsInfo[20].Key=wimbt
    OsInfo[20].Value=0
    OsInfo[21].Key=blddt
    OsInfo[21].Value=190318
    OsInfo[22].Key=bldtm
    OsInfo[22].Value=1202
    OsInfo[23].Key=bldbrch
    OsInfo[23].Value=19h1_release
    OsInfo[24].Key=bldchk
    OsInfo[24].Value=0
    OsInfo[25].Key=wpvermaj
    OsInfo[25].Value=0
    OsInfo[26].Key=wpvermin
    OsInfo[26].Value=0
    OsInfo[27].Key=wpbuildmaj
    OsInfo[27].Value=0
    OsInfo[28].Key=wpbuildmin
    OsInfo[28].Value=0
    OsInfo[29].Key=osver
    OsInfo[29].Value=10.0.18362.836.amd64fre.19h1_release.190318-1202
    OsInfo[30].Key=buildflightid
    OsInfo[31].Key=edition
    OsInfo[31].Value=Professional
    OsInfo[32].Key=ring
    OsInfo[32].Value=Retail
    OsInfo[33].Key=expid
    OsInfo[34].Key=containerid
    OsInfo[35].Key=containertype
    OsInfo[36].Key=edu
    OsInfo[36].Value=0
    File[0].CabName=WATCHDOG-20200609-1847.dmp
    File[0].Path=WATCHDOG-20200609-1847.dmp
    File[0].Flags=851970
    File[0].Type=2
    File[0].Original.Path=\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20200609-1847.dmp
    File[1].CabName=sysdata.xml
    File[1].Path=WER-239544687-0.sysdata.xml
    File[1].Flags=851970
    File[1].Type=5
    File[1].Original.Path=\\?\C:\Windows\TEMP\WER-239544687-0.sysdata.xml
    File[2].CabName=WERInternalMetadata.xml
    File[2].Path=WER3594.tmp.WERInternalMetadata.xml
    File[2].Flags=851970
    File[2].Type=5
    File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3594.tmp.WERInternalMetadata.xml
    File[3].CabName=WERInternalRequest.xml
    File[3].Path=WER35A5.tmp.xml
    File[3].Flags=851970
    File[3].Type=5
    File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35A5.tmp.xml
    File[4].CabName=memory.csv
    File[4].Path=WER35A6.tmp.csv
    File[4].Flags=589826
    File[4].Type=5
    File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35A6.tmp.csv
    File[5].CabName=sysinfo.txt
    File[5].Path=WER35C6.tmp.txt
    File[5].Flags=589826
    File[5].Type=5
    File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35C6.tmp.txt
    File[6].CabName=Report.zip
    File[6].Path=Report.zip
    File[6].Flags=65536
    File[6].Type=11
    File[6].Original.Path=\\?\C:\Windows\system32\Report.zip
    Ns[0].Name=stopcode
    Ns[0].Value=00000142
    Ns[1].Name=p1
    Ns[1].Value=FFFF9D0FCFDCD460
    Ns[2].Name=p2
    Ns[2].Value=FFFFF80477272610
    Ns[3].Name=p3
    Ns[3].Value=0000000000000000
    Ns[4].Name=p4
    Ns[4].Value=0000000000002D98
    FriendlyEventName=Hardware error
    ConsentKey=LiveKernelEvent
    AppName=Windows
    AppPath=C:\Windows\System32\WerFault.exe
    ReportDescription=A problem with your hardware caused Windows to stop working correctly.
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=00000000000000000000000000000000
    MetadataHash=-1623578013

    Wednesday, June 10, 2020 2:30 AM

All replies

  • To evaluate the computer environment please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    Choose the applicable link for the operating system:
    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html
    https://www.eightforums.com/threads/language-add-or-remove-in-windows-8.5849/
    https://www.sevenforums.com/tutorials/87317-display-language-change.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There are two files for you to find manually:

    a) dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    b) Download and install:  Everything search

    https://www.voidtools.com/

    Search for:  WATCHDOG-20200609-1847.dmp

    Post a share link into the thread using one drive, drop box, or google drive.


    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .



    Wednesday, June 10, 2020 3:52 AM
  • Here are the files you have asked for. I didn't find any in C:/Windows/MEMORY.DMP, even with hidden files/folders show enabled. Please let me know if anything else is needed.

    https://drive.google.com/file/d/1i5oYZpbQlVE3gmBeUQwYoaExpQTkECu9/view?usp=sharing

    Wednesday, June 10, 2020 4:09 AM
  • Please make links available without sign on.
    Wednesday, June 10, 2020 5:09 AM
  • Sorry about that, let me know if it works now.

    https://drive.google.com/file/d/1i5oYZpbQlVE3gmBeUQwYoaExpQTkECu9/view?usp=sharing

    Wednesday, June 10, 2020 6:52 AM
  • The collected logs displayed no BSOD.

    There were many live kernel events related to video (141 and 142).

    These were the typical log entries:

    Event[6661]:
      Log Name: System
      Source: Display
      Date: 2020-05-19T17:29:29.685
      Event ID: 4101
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-4BPQ8N1
      Description:
    Display driver nvlddmkm stopped responding and has successfully recovered.


    Event[8879]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2020-06-05T20:48:09.102
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-4BPQ8N1
      Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.



    Event[8764]:
      Log Name: System
      Source: EventLog
      Date: 2020-06-05T19:20:37.596
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-4BPQ8N1
      Description:
    The previous system shutdown at 6:54:53 PM on ?6/?5/?2020 was unexpected.

    .

    .

    .

    1) Post images or share links for:

    a) startup and system recovery failure settings

    b) virtual memory / page file settings

    .

    2) Search for:  C:\Windows\LiveKernelReports

    post share links into the thread

    .

    3) See if you can find another PCI-e port on the motherboard for the GPU > test computer stability / instability

    .

    4) Reset the BIOS

    .

    5) Make sure that there is no overclocking

    .

    6) Turn off Windows fast startup:
    https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

    .

    7) What are the BIOS 3.3, 5 and 12 voltage values?

    .

    8) Having replaced the GPU and clean installed these should have ruled out GPU and OS problems

    .

    9) The GPU can be retested (stress tested) checking temperatures at idle and under load

    .


    10) If all of the above do not identify or fix the problem then the remaining option is RMA motherboard

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .


    Wednesday, June 10, 2020 8:02 AM
  • 1-2) Below is the link for 1. The C:Windows/LiveKernalReport only contains 2 Folders (WATCHDOG/win32k.sys) both of which are empty.

    https://drive.google.com/file/d/1rOJH95JAn2GEur9az0z9Yqr--9ttoEu_/view?usp=sharing

    3) I will test a separate PCI-E slot later today and let you know the results.

    4) I've also reflashed latest BIOS version a few times. If this isn't enough and you would like me to test full resetting it (resetting the CMOS) let me know and I can try that.

    5) I have not overclocked anything, I have underclocked to solve for the issue mentioned in this thread which has seemed to help a little.

    6) Windows fast startup is now disabled, will let you know the results.

    7) Below are the values, with no huge fluctuations to show irregularities.

    3.3V = 3.360V Min, 3.376 Max

    5V = 5.040V Min, 5.040 Max

    12V = 12.096V Min, 12.096 Max

    8) I agree, unless I'm reinstalling bad software each time, I don't think software seems to be issue too.

    9) Stress tested with furmark/msi kombuster and temps and load are fine.

    Wednesday, June 10, 2020 4:00 PM
  • It can be easy to miss BSOD when the default automatically restart is checked.

    For startup and recovery system failure uncheck automatically restart.

    Then reboot to maintain settings.

    .

    For the BIOS:

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    https://www.howtogeek.com/131623/how-to-clear-your-computers-cmos-to-reset-bios-settings/
    3 Ways to Reset Your BIOS - wikiHow:
    http://www.wikihow.com/Reset-Your-BIOS

    .

    With the new PCI-e slot retest using Furmark:

    Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
    FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
    https://www.tenforums.com/tutorials/13081-furmark-gpu-stress-test.html
    Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
    a) Record the maximum temperature and post the maximum temperature into the thread.
    b) Record the test duration and post the uninterrupted test duration into the thread.
    c) Aim for testing 1 hour.
    d) Use the Microsoft snipping tool to post images into the thread.


    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .

    Wednesday, June 10, 2020 4:59 PM
  • Here are the FurMark results as well as the Min/Max being tracked with HWMonitor. (I am unable to directly embed images because my account is not verified apparently).

    https://imgur.com/a/8ZSWqfQ

    I have tested CPU/RAM/GPU using Cinebench/ Furmark or Kombuster / memtest, and all worked fine when testing. It seems to only crash when I am playing any game at all, even non intensive ones. I tested running an intensive game (Call of Duty: Warzone) and the crash did eventually happen on default GPU settings. (I run underclocked GPU Clock usually at -1000 MHz since I mentioned that it does seem to mitigate the issue). This issue has happened on original GPU and RMA'd GPU, with the same underclock mitigating the issue.

    Wednesday, June 10, 2020 6:49 PM
  • At this time other options are to:

    a) stress test drivers > check for BSOD > debug any dump files

    b) trial and error to see if one driver provides a more stable computer environment


    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .

    Wednesday, June 10, 2020 7:12 PM
  • Do you have any suggestions on how to stress test specific drivers? I've tested each RAM individually on the optimal slot (2), as well as the RAM together on optimal and non-optimal (2/4 vs. 1/3) and issue still occurred. I got a new PSU because I was thinking the GPU was not getting enough Voltage. Only components I can think of is HDD/SSD, CPU, and Mobo.
    Wednesday, June 10, 2020 7:20 PM
  • 1) Create a new restore point:

    https://www.sevenforums.com/tutorials/285911-restore-point-add-create-restore-point-context-menu-windows.html

    2) Read these links on Windows driver verifier:

    https://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool
    .

    .

    Windows driver verifier is designed to stress test drivers.

    If there are misbehaving drivers the computer will crash.

    If dump files are created they can be debugged.

    Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

    The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

    If there are no further BSOD this concludes the use of the tool.

    After each BSOD you must turn off the tool in order to return to the desktop.

    Learn the Windows RE commands reset and bootmode.

    These are ran in safe mode or safe mode with command prompt.

    In case these fail the next option is system restore.

    If system restore fails you can restore a backup image or use registry commands.

    Start the tool with the 3 customized test settings in the Ten Forums link.

    If there are no BSOD, increase the simultaneous customized test settings up to the customized test settings in the Microsoft link.

    There can be performance problems and / or slow boot while using the tool.

    If necessary the customized test settings can be modified.

    Summary:
    a) make a new restore point
    b) test all non-Microsoft drivers
    c) test no Microsoft drivers
    d) after each BSOD use the reset command to turn off the tool
    e) if the reset command does not work then use the bootmode command
    f) only if both reset and bootmode command fail to turn off the tool then use restore
    g) start with the 3 customized test settings in the Ten Forums link
    h) if there are no BSOD after one hour, increase the customized test settings up to the customized test settings in the Microsoft link
    i) report any performance problems or very slow boot so that the customized settings can be modified

    .

    .

    For any BSOD:

    a) run the administrative command prompt command to collect new files

    b) search for C:\windows\memory.dmp > if the file size is < 1 GB then zip and post a share link into this thread

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .
    Wednesday, June 10, 2020 8:23 PM
  • I've followed the thread, and ensured verifier is on through querysettings. So far I have not crashed once doing my regular routine, and this includes playing games (where I would always crash). I've even defaulted my clock speed back to the normal out-of-box settings, but seems to be running well right now which is weird. Will keep this thread updated along with the log if/when it does crash.
    Thursday, June 11, 2020 7:37 AM
  • I've included everything in the Microsoft link and got a blue screen instantly on reboot of PC. Logs can be found below.

    https://drive.google.com/file/d/1fTjGbByphh_spAGpzJH8oUG211JF5yw5/view?usp=sharing

    EDIT: Including Memory.DMP as well

    https://drive.google.com/file/d/1SPbP9uylMAIC7w1b-l_lqCO-7mSPUjE4/view?usp=sharing
    Thursday, June 11, 2020 5:27 PM
  • There will be people viewing this thread that may not understand the location of the thread:

    How come it was posted in Windows 7 instead of Windows 10?

    .

    .

    There was one memory dump file.

    It was a Window driver verifier crash with one misbehaving driver.

    Uninstall and reinstall:  RzDev_007a.sys

    RzDev_007a   Razer 007a Service     Razer 007a Service     2/17/2020 7:03:27 PM   C:\Windows\system32\drivers\RzDev_007a.sys

    Alternatively uninstall an reinstall all of the Razer software.

    https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1            

    RzDev_007a.sys Mon Feb 17 21:03:27 2020 (5E4B53FF).

    .

    Restart Windows driver verifier with the 19 customized test settings in the Microsoft link.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .


    Thursday, June 11, 2020 6:12 PM
  • Sorry about that, I may have missed the parent thread being Windows 7. Will keep in mind for future.

    Following the above, and turning verifier back on, I am able to use Windows normally with verifier running. However, when testing in-game, I still received the crash in game without any BSOD. Attached are the logs from the above cmd command. (Note, since there are lots of nvidia driver crashes, I just wanted to make note that I have clean uninstall/reinstalled the latest Nvidia drivers with DDU a few times on both original GPU and RMA'd GPU) 

    https://drive.google.com/file/d/1i78vhWrifHBhwFOvtdubJ7PbZiTEgpoK/view?usp=sharing

    Thursday, June 11, 2020 8:07 PM
  • These are trial and error steps:

    Uninstall Nvidia RTX voice and see if it makes any difference: (if possible keep it uninstalled during the troubleshoting)

    https://www.nvidia.com/en-us/geforce/guides/nvidia-rtx-voice-setup-guide/

    .

    .

    Current Nvlddmkm.sys:  Driver Version    26.21.14.4614

    .

    .

    1) Turn off Windows updates of non-Microsoft drivers:


    https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html

    2) Continue running Windows driver verifier for 36 continuous hours with 19 customized test settings

    3) While running windows driver verifier there can be performance problems

    4) After 36 hours of additional testing turn off the tool if there were no BSOD

    5) Use gaming software that may cause performance problems

    6) Report the Nvidia driver and the performance problem into the thread

    7) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

    8) re-install the Nvidia GPU driver from the Nvidia website

    9) make sure that you check the clean install box and if available install the physx driver


    Display Driver Uninstaller Download version 18.0.2.5 (or newer version if available)
    https://www.wagnardsoft.com/

    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

    Download Drivers | NVIDIA
    https://www.nvidia.com/Download/index.aspx


    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .



    Thursday, June 11, 2020 8:40 PM
  • I actually uninstalled RTX voice yesterday because of some crashes I saw in Event Viewer. Issue still occured.

    I followed your link and Enabled the "Do not include drivers with Windows Update".

    I've DDU'd and clean installed multiple times in Minimal Safe Mode, but did it again this time with the above setting enabled just in case. Will let you know if issue is still occurring.

    Latest Nvidia Driver version for my card: 446.14

    Thursday, June 11, 2020 9:26 PM
  • Following issue occurred even after another DDU Safe Mode, with clean install of latest drivers and Windows Update for drivers turned off.

    Video driver just crashed again while gaming. No BSOD again. Seems to be happening about every 30 minutes from when I start gaming.

    https://drive.google.com/file/d/16A9r6kySYCR6smdN_t74zveOWPgGONad/view?usp=sharing

    Friday, June 12, 2020 12:53 AM
  • The logs displayed 2 Windows driver verifier BSOD on 6/11/20:

    .

    .

    Event[10761]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2020-06-11T10:11:55.501
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-4BPQ8N1
      Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c4 (0x0000000000002000, 0xfffff809eedc259c, 0x0000000000000000, 0x0000000065447a52). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: e12b78c7-ab0c-45ed-ad9c-7500f6ceccba.

    .

    .

    Event[11010]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2020-06-11T12:13:23.449
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-4BPQ8N1
      Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c4 (0x0000000000002000, 0xfffff802917d259c, 0x0000000000000000, 0x0000000065447a52). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 23617ac2-0463-4b0f-946e-f8f572e1c126.

    .

    .

    Search for C:\windows\memory.dmp

    Post a share link if the file size is < 1.5 GB.



    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .

    Friday, June 12, 2020 3:28 AM
  • That's weird, I didn't receive any BSOD besides the Razer drivers we called out earlier.

    Here is the MEMORY.DMP file.

    https://drive.google.com/file/d/1Y_js0NTnPV71qyETFA9ElPL70bvhkJNS/view?usp=sharing

    Friday, June 12, 2020 5:14 AM
  • Earlier in the thread what steps were made for RzDev_007a?

    The misbehaving driver in the latest dump was RzDev_007e.

    Uninstall the software or the driver and reinstall.

    Do you have alternative hardware that can be used in case there are recurrent razer problems or for swap testing?

    .

    .

    Restart Windows driver verifier with the 19 customized test settings in the Microsoft link.

    .

    .

    RzDev_007e   Razer 007e Service     Razer 007e Service    2/17/2020 7:04:00 PM   C:\Windows\system32\drivers\RzDev_007e.sys      

    RzDev_007e.sys Mon Feb 17 21:04:00 2020 (5E4B5420)

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .



    Friday, June 12, 2020 6:07 AM
  • I got this Razer mouse and downloaded the drivers after I built this computer, so this shouldn't be the cause as I was already crashing before hand. I do understand it is showing that the driver is crashing now, which is weird but I uninstalled all Razer devices earlier and reinstalled. I've also removed both the Razer Device's from the verifier list, as it was not letting me into the system with that selected.
    Friday, June 12, 2020 6:19 AM
  • A new installation can become corrupted.

    Or older drivers can malfunction as the computer environment changes.

    For example, Nvidia and Microsoft are currently working together on older Nvidia drivers causing BSOD.

    Please make sure that the Razer drivers are tested with windows driver verifier.


    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .

    Friday, June 12, 2020 1:59 PM
  • No, I understand your point. What my point is that, I have been getting these crashes since the day this computer was built about 2 months ago, and that was before I even got this Razer mouse, and hence was happening before I had downloaded any Razer drivers. Even with official firmware/Razer drivers it seems to still cause the blue screen after fresh install/reinstall and prevents boot because the verification fails, that in turn with my issue happening even after I have already had the mouse is why I decided to exclude specifically only the Razer driver.
    Friday, June 12, 2020 3:30 PM
  • Hi,

    Is your problem solved?

    If not, please reply and tell us the current situations and we wil provide further assistance.


    针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。

    Thursday, July 2, 2020 3:06 AM