[SOLVED] random crash 0xb3 and 8 min BSOD when verifier.exe on

Joined
Mar 14, 2022
Posts
33
Since I upgrade my GTX 1660 super to RTX 3050 I have to upgrade my graphic card driver to get it usable, but the system are constantly freeze or BSOD in any 511. driver( currently 511.79, DDU already). I simply take a look at the dump file and Event Viewer to find out mostly is "nvlddmkm.sys" fault. So I went to verifier.exe to test the driver, when it's on, the BSOD 0x3b will happen after 8 min, it's wired that it doesn't come up with the "Driver Violation Error". And the interesting 8 min you can find it in the dump file "System Uptime". I thought maybe my graphic card are corrupt, so I borrow an GTX 1050 with verifier.exe on, it do the same 8 min BSOD. The crash is happen randomly if the verifier.exe off ( but not experiment crashing after switch to GTX 1050, and a friend have my RTX 3050 to test a few days with the same driver version and have no problem at all), I'm absolutely lack of knowledge about it and turn to you brilliant guys.

Before upgrade no BSOD happening;
I have test my memory with memtest86, 4pass no error;
disk tested have no bad sectors;
The 0xb3 is the only one i can reproduce, there are also 0xfc & 0x50 error & bunch of livekernelEvent( sometime the driver successfully recovered)... some are maybe belong other issue.

here is the BSOD file: Sharing Link Validation

the password is "nvidia"
 
Last edited:
  • Windows 10 21H1 19043.1586
  • CPU: is i5-10400F
  • RAM: cuso 16GB DDR4 runing at 2666Mhz
  • RTX3050 is the problem one, switching to GTX 1050 and previous using GTX 1660 super have no problem at all.
  • MotherBoard: colorful CVN B460I GAMING V20
  • driver verifier on with nvlddmkm.sys and nvhda64v.sys without systematic low resources simulation.
  • using system defender, no 3rd party anti-virus software.
  • using ThrottleStop for CPU undervolt that stable runing for two years.
 
Oh i notice that my bios isn't the latest version, and it update with graphic card compatibility, i think that was the problem. If works I will reply here.
 
The single dump file I checked does appear to certainly point to a graphics card driver or graphics card issue. If the other two cards appear to work with no issues, then it would suggest an issue with either the card or the motherboard. You've mentioned that the latest BIOS update appears to resolve a compatibility issue so I'll wait to see if they appears to remedy your issue before providing any further comments.
 
There are no more BSOD after I upgrade the bios in three days! But when i turn verifier on to test the nvidia's driver, still BSOD in 8 min, can say there are still some issue within the driver when in the specific circumstance? ( i have meet a freeze issue after 35 hours, seem the Nvidia forum have the same freeze issue posted, so I just let them handle it. But here I want to say is maybe the verifier.exe found the PAGE_FAULT_IN_NONPAGED_AREA issue is the reason trigger the freeze issue? )
 
But here I want to say is maybe the verifier.exe found the PAGE_FAULT_IN_NONPAGED_AREA issue is the reason trigger the freeze issue? )
No and it wasn't triggered by Driver Verifier either. Does the freezing continue after disabling Driver Verifier? You can disable it from an elevated command prompt using the following command:

Rich (BB code):
verifier /reset
 
Freeze happen when disabling driver Verifier ( the secound freeze I catch is after two days ). Because when Verifier on, BSOD happen in 8 min so I can't test when Verifier is on.
 
Could you please provide the latest dump file(s) using the Sysnative file collection tool as you did before?
 
The latest "Verifier on dump" is uploaded at the same link name "RTX3050-verifier-on-ver.512.15-3-24-2022.dmp", and the "freeze dump" is a compelete dump (32GB) which is uploading.
 
The suggested mini dump I have uploaded in the same share link is named "RTX-3050-Freeze-ver.512.15-3-28-2022-mini.dmp" and "RTX-3050-Freeze-ver.512.15-3-25-2022-mini.dmp".
 
No, what is the dump file settings? Please open a command prompt shell and then enter the following command:

Rich (BB code):
reg query HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

Please post the output in your next post.
 
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl
    AutoReboot    REG_DWORD    0x1
    CrashDumpEnabled    REG_DWORD    0x1
    DumpFile    REG_EXPAND_SZ    %SystemRoot%\MEMORY.DMP
    DumpLogLevel    REG_DWORD    0x0
    EnableLogFile    REG_DWORD    0x1
    LogEvent    REG_DWORD    0x1
    MinidumpDir    REG_EXPAND_SZ    %SystemRoot%\Minidump
    MinidumpsCount    REG_DWORD    0x5
    Overwrite    REG_DWORD    0x1
    DumpFilters    REG_MULTI_SZ    dumpfve.sys
    AlwaysKeepMemoryDump    REG_DWORD    0x0
 
Code:
wmic recoveros
AutoReboot  Caption  DebugFilePath            DebugInfoType  Description  ExpandedDebugFilePath  ExpandedMiniDumpDirectory  KernelDumpOnly  MiniDumpDirectory      Name                                                              OverwriteExistingDebugFile  SendAdminAlert  SettingID  WriteDebugInfo  WriteToSystemLog
TRUE                 %SystemRoot%\MEMORY.DMP  1                           C:\Windows\MEMORY.DMP  C:\Windows\Minidump        FALSE           %SystemRoot%\Minidump  Microsoft Windows 10 Pro|C:\Windows|\Device\Harddisk1\Partition3  TRUE                        FALSE                      TRUE            TRUE
 
Let's change the dump file settings back to their defaults so Minidumps are produced as well. Please enter the following command from an elevated command prompt:

Rich (BB code):
reg add HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl /v CrashDumpEnabled /t REG_DWORD /d 0x7 /f

Afterwards, please reboot the computer.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top