Random BSOD With Various Reasons During Gaming

C

christantoan

Active member
Joined
May 22, 2015
Posts
43
A brief description of your problem (but you can also include the steps you tried)
Random fatal OS crashes happen during gaming, sometimes Windows doesn't even produce BSODs, just the screen freezes at its last moment and the last sound repeating. The reasons for the BSODs are also different (almost) each time.
I have tried:
  • Disabling Hardware-accelerated GPU Scheduling and Variable Refresh Rate in Windows' Graphics settings
  • DISM: several entries of:
    2023-03-19 20:09:05, Info CSI 00000001 Shim considered [l:126]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2664_none_7dfa24947c9c0a36\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2023-03-19 20:09:05, Info CSI 00000002 Shim considered [l:123]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.2664_none_7dfa24947c9c0a36\wcp.dll' : got STATUS_SUCCESS
  • SFC: several entries of:
    2023-03-19 20:23:41, Info CSI 0000033e [SR] Repairing 1 components
    2023-03-19 20:23:41, Info CSI 0000033f [SR] Beginning Verify and Repair transaction
    2023-03-19 20:23:41, Info CSI 00000340 [SR] Repairing file \??\C:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\\OneDrive.lnk from store
    2023-03-19 20:23:41, Info CSI 00000342 [SR] Repair complete
  • Checking the system drive for errors: no errors
  • SMART extended test the drives via Hard Disk Sentinel: completed successfully
  • MemTest86+ (the Plus variant) for 8 passes: passes, no errors
  • Driver Verifier: Run with no crashes for 24+ hours but the computer almost only idles during the test as the performance is too low to run games.

System Manufacturer? ASUS
Laptop or Desktop? Laptop
Exact model number (if laptop, check label on bottom) Asus ROG GL502VS-FY045T
OS ? (Windows 11, 10, 8.1, 8, 7, Vista) Windows 10
x86 (32bit) or x64 (64bit)? x64
(Only for Vista, Windows 7) Service pack? N/A
What was original installed OS on system? Windows 10
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
Age of system? (hardware) 6 years
Age of OS installation? 6 years
Have you re-installed the OS? Yes
CPU Intel Core i7-6700HQ
RAM (brand, EXACT model, what slots are you using?) Corsair CMSX16GX3M2B1600C9 Vengeance 16GB (2x8GB) DDR3 1600Mhz CL9, all 2 slots
Video Card NVidia GeForce GTX 1070 8GB VRAM
MotherBoard - (if NOT a laptop) N/A
Power Supply - brand & wattage (if laptop, skip this one) N/A
Is driver verifier enabled or disabled? Disabled during BSODs
What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Kaspersky Internet Security 21.3.10.391 (j)
Are you using proxy, vpn, ipfilters or similar software? dnscrypt-proxy and WireGuard VPN
Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) I have PowerISO but don't use its Virtual Drive functionality.
Are you currently under/overclocking? Are there overclocking software installed on your system? Not under/overclocking but undervolting. However, BSODs also happen when the undervolting is disabled. Using ThrottleStop 9.5.

Sysnative zip file is attached.
Speccy snapshot: http://speccy.piriform.com/results/1vBtSVWItAlP3O850QxNbrO

Thank you very much in advance!
 

Attachments

Another thing I've tried is DDU and installing latest NVidia driver.

Also, during test with Driver Verifier, I've had to skip testing a driver, mrigflt.sys because it causes crash at boot. The driver comes from Macrium Reflect and it still crashes even on the latest version so I figured that was how it works.
 
I'm a bit concerned about the age of most of your drivers. You have third-party drivers going back to 2009. Some examples...
Code: 
pwdrvio.sys                                   Tue Jun 16 04:43:45 2009
speedfan.sys                                 Sat Dec 29 22:59:35 2012
atkwmiacpi64.sys                           Tue Jul  2 11:35:32 2013
rt640x64.sys                                 Thu Jul 23 11:53:50 2015
ICCWDT.sys                                   Sun Sep 20 10:59:19 2015
dptf_acpi.sys                                 Fri Oct 23 22:24:17 2015
But there are many more. The main drivers with dates less than a year old are things like VMWare, HWInfo, Nvidia, etc.

The dumps have varied stop codes, including two WHEA errors (these generally indicate a hardware problem, but they can be caused by bad drivers). All these BSODs could be caused by outdated drivers, so ensuring that all drivers are updated is an essential first step. Windows Update will usually keep Windows 10 drivers updated, do you run it regularly?

The best place to source the correct drivers for laptops is from the laptop vendor's website. That's because laptop drivers are often customised in order to improve battery life or for other hardware specific reasons. It's not uncommon to find that generic drivers (Intel drivers, Nvidia drivers, Realtek drivers etc) don't work properly in some laptops for these reasons. In your case you need the Asus Driver Download site, you'll need the Asus model name/number of your laptop. See whether they have later drivers than those you have installed.

Get all of your drivers up to date and see whether the laptop is stable. If not please post another Sysnative File Collection file again.
 
ubuysa said:
I'm a bit concerned about the age of most of your drivers. You have third-party drivers going back to 2009. Some examples...
Code: 
pwdrvio.sys                                   Tue Jun 16 04:43:45 2009
speedfan.sys                                 Sat Dec 29 22:59:35 2012
atkwmiacpi64.sys                           Tue Jul  2 11:35:32 2013
rt640x64.sys                                 Thu Jul 23 11:53:50 2015
ICCWDT.sys                                   Sun Sep 20 10:59:19 2015
dptf_acpi.sys                                 Fri Oct 23 22:24:17 2015
But there are many more. The main drivers with dates less than a year old are things like VMWare, HWInfo, Nvidia, etc.

The dumps have varied stop codes, including two WHEA errors (these generally indicate a hardware problem, but they can be caused by bad drivers). All these BSODs could be caused by outdated drivers, so ensuring that all drivers are updated is an essential first step. Windows Update will usually keep Windows 10 drivers updated, do you run it regularly?

The best place to source the correct drivers for laptops is from the laptop vendor's website. That's because laptop drivers are often customised in order to improve battery life or for other hardware specific reasons. It's not uncommon to find that generic drivers (Intel drivers, Nvidia drivers, Realtek drivers etc) don't work properly in some laptops for these reasons. In your case you need the Asus Driver Download site, you'll need the Asus model name/number of your laptop. See whether they have later drivers than those you have installed.

Get all of your drivers up to date and see whether the laptop is stable. If not please post another Sysnative File Collection file again.
Click to expand...
Thank you for the advice. Unfortunately I've checked Asus download site and already have the latest drivers installed (the joy of having a short supported laptop).
atkwmiacpi64.sys is from ATKPackage V1.0.0061 and was released on 2019/09/20 (latest from Asus' site)
rt640x64.sys is from Realtek Audio Driver version 6.0.1.8564 and was released on 2018/12/25 (latest from Asus' site)
ICCWDT.sys and dptf_acpi.sys are probably part of Intel® Dynamic Platform and Thermal Framework Driver version V8.1.10605.221 and was released on 2016/02/17 (latest from Asus' site)

pwdrvio.sys is part of PowerISO software though I only use the image editing functionality and not the image mounting capability so it's probably safe to delete it? I already have the latest version (8.4) which was released on January 26, 2023
speedfan.sys is from SpeedFan software, a utility to monitor fan speed. I already have the latest version (4.52)

Can you tell me how to get the list of the installed drivers sorted by date so that I can do more checking?

Thank you in advance.
 
christantoan said:
Can you tell me how to get the list of the installed drivers sorted by date so that I can do more checking?
Click to expand...
Open PowerShell and enter the following command DriverQuery /fo csv /v | Out-File C:\mydrivers.csv and you'll get a comma separated mydrivers.csv file which you can import into Excel (or similar) and sort on any field you like. Note that you can call the output file anything you like and specify any convenient path.
 
ubuysa said:
Open PowerShell and enter the following command DriverQuery /fo csv /v | Out-File C:\mydrivers.csv and you'll get a comma separated mydrivers.csv file which you can import into Excel (or similar) and sort on any field you like. Note that you can call the output file anything you like and specify any convenient path.
Click to expand...
Thank you for the tips. I've generated the file but there are a lot of entries with no date. I'm using the Link Date column, is that correct? I also can't find pwdrvio.sys in the output file even though pwdrvio.sys exists in my system.
Also, 2 more BSODs but the last one might be because I'm testing older NVidia drivers.
 

Attachments

Last edited:
Yes, that's the only field that's a date. The blank ones are likely Microsoft drivers that are part of Windows.

I've been looking through your System log and there is an interesting pattern. For most (but not all) of the reported BSODs there are messages about staring VMWare drivers, the BSODs occur at exactly the same time...
Code: 
Event[7679]:
  Log Name: System
  Source: Microsoft-Windows-Hyper-V-VmSwitch
  Date: 2023-03-18T23:06:01.0630000Z
  Event ID: 277
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Andre-Notebook3
  Description: 
vmswitch.sys build 19041.amd64.vb_release_svc_prod1, debug false, official true, 1 1

Event[7680]:
  Log Name: System
  Source: VMnetuserif
  Date: 2023-03-18T23:06:01.0180000Z
  Event ID: 1
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Andre-Notebook3
  Description: 
() Starting up the User Interface Driver for VMware Virtual Networks.

Event[7681]:
  Log Name: System
  Source: VMnetBridge
  Date: 2023-03-18T23:06:00.9800000Z
  Event ID: 10
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Andre-Notebook3
  Description: 
() Starting up the Bridge Driver for VMware Virtual Networks.

Event[7682]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-03-18T23:06:00.9960000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Andre-Notebook3
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff807448c1b49, 0xffffe08fb2926f90, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\031823-17203-01.dmp. Report Id: 537895d2-5fb6-4461-afe7-bc383e3d35c0.
It might be worth paying particular attention to the VMWare driver versions...

There is also a single (but fatal) error for your AX210 card...
Code: 
Event[24296]:
  Log Name: System
  Source: Microsoft-Windows-NDIS
  Date: 2023-02-15T16:27:46.3650000Z
  Event ID: 10317
  Task: PnP
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Andre-Notebook3
  Description: 
Miniport Intel(R) Wi-Fi 6E AX210 160MHz, {48bb79e9-8c59-4257-950a-b4a4f3e136a5}, had event Fatal error: The miniport has detected an internal error
I'd also check the driver version for that card too.

In addition, there have been reported problems in the past with the Samsung secnvme.sys driver, for your two Samsung NVMe SSDs. The version you have is from 2020,...
Code: 
0: kd> lmDvmsecnvme
Browse full module list
start             end                 module name
fffff804`7c550000 fffff804`7c573000   secnvme    (deferred)             
    Image path: secnvme.sys
    Image name: secnvme.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jan 21 07:55:38 2020 (5E26925A)
    CheckSum:         00026678
    ImageSize:        00023000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
It may be worth downloading Samsung Magician and use that to see whether there is an updated NVMe driver available.
 
Thank you very much for finding all of these info.


I'm sorry but English isn't my native language.
ubuysa said:
...about staring VMWare drivers, the BSODs occur at exactly the same time...
Click to expand...
Did you mean here "starting" (as in the drivers want to start) or "starring" (as in the main suspect)?
Sorry. Just read the log entries and found out that you meant "starting".

Also, unfortunately, the VMWare and Intel AX210 drivers are the latest already; and Samsung Magician doesn't report any new driver version.

At this point, it's highly likely that the problem is with the hardware, right?
 
Last edited:
I'm so sorry, that's my typo. It's should be starting. If you look at entry 7681 the Date: field is 2023-03-18T23:06:00.9800000Z, so that's 18th March 2023 at 06:00.98 (the Z means "Zulu" or UTC).

Now look at the entry 7682, this is the bugcheck (the record of the BSOD). It's Date: field is 2023-03-18T23:06:00.9960000Z, and that's 18th March 2023 at 06:00.996, which is almost immediately after the 7681 entry.

There are other BSODs in your log that show this pattern. It appears that some of the dumps are happening when VMWare starts these drivers.
 
ubuysa said:
I'm so sorry, that's my typo.
Click to expand...
No need to be sorry! You've been a lot of help! I also should've been able to catch what you meant by reading the logs more carefully.

I'll try uninstalling VMWare for now as I can't remove the Wi-Fi card and the SSD currently.

Virtualization, networking, and storage though...
If not for you, I would have guessed the problem is with the graphics because the BSODs happen when gaming.
 
christantoan said:
No need to be sorry! You've been a lot of help! I also should've been able to catch what you meant by reading the logs more carefully.

I'll try uninstalling VMWare for now as I can't remove the Wi-Fi card and the SSD currently.

Virtualization, networking, and storage though...
If not for you, I would have guessed the problem is with the graphics because the BSODs happen when gaming.
Click to expand...
You could well be right! The WHEA BSODs are machine check exceptions, meaning that a hardware fault has been detected. Unfortunately, and for reasons that I don't yet understand, I can't access the WHEA error details in your dumps.

However, and fortuitously, one of the two recent dumps you uploaded is not a WHEA bugcheck, it's a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M bugcheck, and they contain a lot more useful information. This bugcheck indicates that an unknown and unhandled exception occurred in kernel mode, and that almost always means a third-party driver - or the associated hardware of course.

The exception record, which defines the exception itself, shows that the exception was an access violation (0xC0000005) caused by an attempt to write to address 0x00000000...
Code: 
EXCEPTION_RECORD:  ffff82087e4a7708 -- (.exr 0xffff82087e4a7708)
ExceptionAddress: fffff805753983ea (dxgmms2!VidSchiCheckNodeTimeout+0x00000000000000aa)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

That's why the BSOD happened, the question is who did that? The exception address shown above is where the exception occurred, and that address is in the dxgmms2!VidSchiCheckNodeTimeout function.

The dxgmms2.sys driver is a component of Windows DirectX and since the dxgmms2.sys driver is a Microsoft driver it's not the root cause, so we need to look lower down in the driver stack at the third-party graphics driver. The VidSchiCheckNodeTimeout would suggest that a video scheduler timeout operation was in progress, and that might suggest a lack of response from the thrid-party graphics driver or from the graphics card itself.

The third-party graphics driver here is nvlddmkm.sys, the Nvidia RTX1070 driver. We can see nvlddmkm.sys being called several times in the full stack text...
Code: 
ffff8208`7e4a6b58  fffff805`7179a8bf nvlddmkm+0x80a8bf
ffff8208`7e4a6b60  00000000`00006c00
ffff8208`7e4a6b68  fffff805`4bc993a9 nt!EtwWriteEx+0x119
ffff8208`7e4a6b70  ffff9707`c27da010
ffff8208`7e4a6b78  fffff805`7178fb71 nvlddmkm+0x7ffb71
ffff8208`7e4a6b80  ffff9707`be34d360
ffff8208`7e4a6b88  00000000`0000097c
ffff8208`7e4a6b90  00000000`00000000
ffff8208`7e4a6b98  ffff9707`ceadd1a8
ffff8208`7e4a6ba0  00000001`000a7700
ffff8208`7e4a6ba8  fffff805`4bd5beaf nt!KeQueryPerformanceCounter+0x5f
ffff8208`7e4a6bb0  00000000`00000001
ffff8208`7e4a6bb8  fffff805`7178f869 nvlddmkm+0x7ff869
ffff8208`7e4a6bc0  ffff9707`c27da010
ffff8208`7e4a6bc8  ffff8208`7e4a6cd9
ffff8208`7e4a6bd0  00000000`0000097c
ffff8208`7e4a6bd8  ffff9707`c5bde7c0
ffff8208`7e4a6be0  00000000`00000000
ffff8208`7e4a6be8  fffff805`7179b19b nvlddmkm+0x80b19b
ffff8208`7e4a6bf0  00000000`00000000
ffff8208`7e4a6bf8  ffff9707`c27da020
ffff8208`7e4a6c00  ffff8208`7e4a6d20
ffff8208`7e4a6c08  00000000`00000000
ffff8208`7e4a6c10  00000000`00000000
ffff8208`7e4a6c18  00000000`00000000
ffff8208`7e4a6c20  00000000`00000000
ffff8208`7e4a6c28  00000000`00000000
ffff8208`7e4a6c30  fffff85d`d58788af
ffff8208`7e4a6c38  ffff9707`c5bde7c0
ffff8208`7e4a6c40  fffff805`717a557d nvlddmkm+0x81557d
ffff8208`7e4a6c48  00000000`00000002
ffff8208`7e4a6c50  00000000`00040293
ffff8208`7e4a6c58  fffff805`4bca07fb nt!KeQueryCurrentStackInformationEx+0x8b

It is entirely possible that the WHEA bugchecks you've been having are graphics card related, as you suspected. However, it might also be the graphics driver, the version you have is dated Dec 2020...
Code: 
2: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff805`70f90000 fffff805`73576000   nvlddmkm T (no symbols)       
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Dec 31 11:22:30 2020 (5FED9856)
    CheckSum:         02552BCA
    ImageSize:        025E6000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

With laptops the graphics driver is often customised by the vendor, so you want to be sure that you're using the latest graphics drivers supplied by Asus - and ONLY those drivers. That includes BOTH the RTX1070 driver AND the Intel integrated GPU driver (the iGPU). On most laptops these two drivers work hand in hand, even if you're only using the RTX1070.

If you already have the latest Asus versions of both drivers installed, then we'd have to suspect the graphics card itself. On a laptop you're unlikely to be able to remove it (they're usually soldered in) but as a test you might try disabling it and running on the iGPU alone. Graphics performance will be dire of course but if it doesn't BSOD then you'd have to suspect the card.
 
Thank you very much for your analyses!
ubuysa said:
With laptops the graphics driver is often customised by the vendor, so you want to be sure that you're using the latest graphics drivers supplied by Asus - and ONLY those drivers. That includes BOTH the RTX1070 driver AND the Intel integrated GPU driver (the iGPU). On most laptops these two drivers work hand in hand, even if you're only using the RTX1070.

If you already have the latest Asus versions of both drivers installed, then we'd have to suspect the graphics card itself. On a laptop you're unlikely to be able to remove it (they're usually soldered in) but as a test you might try disabling it and running on the iGPU alone. Graphics performance will be dire of course but if it doesn't BSOD then you'd have to suspect the card.
Click to expand...
Unfortunately, again, the latest driver from Asus is already too old that Steam protest. Also, this variant of laptop doesn't have iGPU enabled so it only runs with the 1070.
ubuysa said:
It is entirely possible that the WHEA bugchecks you've been having are graphics card related, as you suspected. However, it might also be the graphics driver, the version you have is dated Dec 2020...
Click to expand...
This dump is probably from when I was testing older (but the latest from Asus) driver. When I did more research yesterday, I found out that drivers from around that version are known to have issue with dxgmm2.sys. Here's the forum discussing that topic: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/216864/blue-screen-dxgmms2sys/

My last dump from yesterday and dumps from before 21 March are when I use latest available driver from Nvidia that should no longer has issues with dxgmm2.sys. Can you please check those? Sorry and thank you in advance!
 
Decided to nuke the following currently not running 3rd-party drivers 🙃
Code: 
sc delete pmxdrv
sc delete vuhub
sc delete WinRing0_1_2_0
sc delete SiSRaid2
sc delete SiSRaid4
sc delete pwdspio
sc delete WmHidLo
sc delete iaStorV
sc delete ddmdrv
sc delete stexstor
sc delete amdsbs
sc delete VSTXRAID
sc delete LSI_SSS
sc delete HpSAMD
sc delete megasr
sc delete nvraid
sc delete nvstor
sc delete vsmraid
sc delete ptun0901
sc delete libusbK
sc delete mvumis
sc delete VBAudioVACMME
sc delete iaLPSSi_GPIO
sc delete iaLPSSi_I2C
sc delete megasas
sc delete btwampfl
sc delete bcbtums
sc delete LSI_SAS
sc delete arcsas
sc delete ADP80XX
sc delete amdxata
sc delete amdsata
sc delete 3ware
sc delete LEqdUsb
sc delete LHidEqd
sc delete LMouFilt
sc delete LHidFilt
sc delete silabenm
sc delete GeneStor
sc delete dtultrascsibus
sc delete dtproscsibus
sc delete ampa
sc delete dtultrausbbus
sc delete nvme
sc delete RZSURROUNDVADService
sc delete percsas2i
sc delete ScpVBus
sc delete ScreamBAudioSvc
sc delete ebdrv
sc delete b06bdrv
sc delete qcusbser
sc delete qcusbnet
sc delete qcusbwwan
sc delete qcfilter
sc delete bcmfn2
sc delete iusb3hub
sc delete iusb3xhc
sc delete dg_ssudbus
sc delete ssudmdm
sc delete LSI_SAS2i
sc delete iaLPSS2i_GPIO2_CNL
sc delete iaLPSS2i_I2C_BXT_P
sc delete iaLPSS2i_GPIO2_BXT_P
sc delete iaLPSS2i_GPIO2
sc delete Netwtw06
sc delete iaLPSS2i_I2C_GLK
sc delete iaLPSS2i_GPIO2_GLK
sc delete percsas3i
sc delete iai2c
sc delete iagpio
sc delete dtlitescsibus
sc delete dtliteusbbus
sc delete VBAudioVMAUXVAIOMME
sc delete cht4vbd
sc delete cht4iscsi
sc delete amdgpio2
sc delete SmartSAMD
sc delete amdi2c
sc delete LSI_SAS3i
sc delete megasas2i
sc delete WinMad
sc delete WinVerbs
sc delete ndfltr
sc delete ibbus
sc delete mlx4_bus
sc delete ItSas35i
sc delete megasas35i
sc delete iaLPSS2i_I2C_CNL
sc delete iaStorAVC
sc delete WDC_SAM
sc delete NVHDA
sc delete iriuna0
sc delete iVCam
sc delete e2esoft_ivcamaudio_simple
sc delete klelam
sc delete AIDA64Driver
sc delete iriunvid
sc delete nssmkig
sc delete Netwtw08
sc delete Netwtw10
Nothing explodes (yet)
 
christantoan said:
My last dump from yesterday and dumps from before 21 March are when I use latest available driver from Nvidia that should no longer has issues with dxgmm2.sys. Can you please check those? Sorry and thank you in advance!
Click to expand...
Your last dump from yesterday (032023-14843-01.dmp, dated Mon Mar 20 16:37:30.067 2023 (UTC + 2:00)) does not indicate a dxgmms2.sys issue. It's another WHEA_UNCORRECTABLE_ERROR caused by a machine check exception.

In this dump a networking operation was in progress, I can see the Intel network card driver (Netwtw12.sys), a driver for the NetLimiter product (nldrv.sys), and a driver for the Wireshark protocol analysis tool (wireguard.sys). I'm not suggesting that any of those three are related to the machine check bugcheck, and it's quite possible that the cause of the machine check was completely unrelated to this thread.
 
ubuysa said:
Your last dump from yesterday (032023-14843-01.dmp, dated Mon Mar 20 16:37:30.067 2023 (UTC + 2:00)) does not indicate a dxgmms2.sys issue. It's another WHEA_UNCORRECTABLE_ERROR caused by a machine check exception.

In this dump a networking operation was in progress, I can see the Intel network card driver (Netwtw12.sys), a driver for the NetLimiter product (nldrv.sys), and a driver for the Wireshark protocol analysis tool (wireguard.sys). I'm not suggesting that any of those three are related to the machine check bugcheck, and it's quite possible that the cause of the machine check was completely unrelated to this thread.
Click to expand...
Thank you again for your analyses! I will check those drivers later.
Just FYI, the wireguard.sys is from WireGuard VPN software and not Wireshark.
 
christantoan said:
Decided to nuke the following currently not running 3rd-party drivers 🙃
Code: 
sc delete pmxdrv
sc delete vuhub
sc delete WinRing0_1_2_0
sc delete SiSRaid2
sc delete SiSRaid4
sc delete pwdspio
sc delete WmHidLo
sc delete iaStorV
sc delete ddmdrv
sc delete stexstor
sc delete amdsbs
sc delete VSTXRAID
sc delete LSI_SSS
sc delete HpSAMD
sc delete megasr
sc delete nvraid
sc delete nvstor
sc delete vsmraid
sc delete ptun0901
sc delete libusbK
sc delete mvumis
sc delete VBAudioVACMME
sc delete iaLPSSi_GPIO
sc delete iaLPSSi_I2C
sc delete megasas
sc delete btwampfl
sc delete bcbtums
sc delete LSI_SAS
sc delete arcsas
sc delete ADP80XX
sc delete amdxata
sc delete amdsata
sc delete 3ware
sc delete LEqdUsb
sc delete LHidEqd
sc delete LMouFilt
sc delete LHidFilt
sc delete silabenm
sc delete GeneStor
sc delete dtultrascsibus
sc delete dtproscsibus
sc delete ampa
sc delete dtultrausbbus
sc delete nvme
sc delete RZSURROUNDVADService
sc delete percsas2i
sc delete ScpVBus
sc delete ScreamBAudioSvc
sc delete ebdrv
sc delete b06bdrv
sc delete qcusbser
sc delete qcusbnet
sc delete qcusbwwan
sc delete qcfilter
sc delete bcmfn2
sc delete iusb3hub
sc delete iusb3xhc
sc delete dg_ssudbus
sc delete ssudmdm
sc delete LSI_SAS2i
sc delete iaLPSS2i_GPIO2_CNL
sc delete iaLPSS2i_I2C_BXT_P
sc delete iaLPSS2i_GPIO2_BXT_P
sc delete iaLPSS2i_GPIO2
sc delete Netwtw06
sc delete iaLPSS2i_I2C_GLK
sc delete iaLPSS2i_GPIO2_GLK
sc delete percsas3i
sc delete iai2c
sc delete iagpio
sc delete dtlitescsibus
sc delete dtliteusbbus
sc delete VBAudioVMAUXVAIOMME
sc delete cht4vbd
sc delete cht4iscsi
sc delete amdgpio2
sc delete SmartSAMD
sc delete amdi2c
sc delete LSI_SAS3i
sc delete megasas2i
sc delete WinMad
sc delete WinVerbs
sc delete ndfltr
sc delete ibbus
sc delete mlx4_bus
sc delete ItSas35i
sc delete megasas35i
sc delete iaLPSS2i_I2C_CNL
sc delete iaStorAVC
sc delete WDC_SAM
sc delete NVHDA
sc delete iriuna0
sc delete iVCam
sc delete e2esoft_ivcamaudio_simple
sc delete klelam
sc delete AIDA64Driver
sc delete iriunvid
sc delete nssmkig
sc delete Netwtw08
sc delete Netwtw10
Nothing explodes (yet)
Click to expand...
Apparently I nuked something important there so I decided to do a repair install of Windows. Attached is my latest system information though all the minidumps are lost.
 

Attachments

What is a 'repair install'. If you mean you used the Windows Reset feature then I'm not sure you'll have made much difference, all that does is refresh the Windows libraries, it doesn't reinstall drivers (in fact it uses the same driver code that was already present). For this reason I never recommend the reset feature as a problem determination tool.
 
ubuysa said:
What is a 'repair install'. If you mean you used the Windows Reset feature then I'm not sure you'll have made much difference, all that does is refresh the Windows libraries, it doesn't reinstall drivers (in fact it uses the same driver code that was already present). For this reason I never recommend the reset feature as a problem determination tool.
Click to expand...
No, I didn't mean the Windows Reset feature. Not sure what it's officially called but I use the Windows install disk of the same "service pack" (i.e. 22H2) to install Windows but keeping the files and apps. After the "install", it looks like it reinstall the drivers that I removed before.
 
Last edited:

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

Back
Top