Question Multiple SYSTEM_SERVICE_EXCEPTION BSODs

[zyd2001]

I got several BSODs recently, which is very annoying. All BSODs happen when I was just browsing websites. I've got the latest windows update and graphics driver.
I used bluescreenview but it just points out ntoskrnl.exe so I can't locate the problem. Can someone help me with this?
My PC configuration:
CPU: R7 5800x
GPU: RTX 3080 FE
Motherboard: MSI B550 Gaming Edge wifi

Four minidumps
https://drive.google.com/file/d/1YFUS2zpbuz1R_8l5vqsHWyBuaEVb9oJ2/view?usp=sharing
https://drive.google.com/file/d/1X5E3aCgydauVNwc5jFZDHmXT8cXiRyFB/view?usp=sharing
https://drive.google.com/file/d/1DYe4DNyfpEdDmI5ToIrpPz3t7OOg8vK0/view?usp=sharing
https://drive.google.com/file/d/1XXIo8RgsTt8_22F0hoa6O8S2T8s1vflu/view?usp=sharing

 

[Koekieezz]

I got several BSODs recently, which is very annoying. All BSODs happen when I was just browsing websites. I've got the latest windows update and graphics driver.
I used bluescreenview but it just points out ntoskrnl.exe so I can't locate the problem. Can someone help me with this?
My PC configuration:
CPU: R7 5800x
GPU: RTX 3080 FE
Motherboard: MSI B550 Gaming Edge wifi

Four minidumps
https://drive.google.com/file/d/1YFUS2zpbuz1R_8l5vqsHWyBuaEVb9oJ2/view?usp=sharing
https://drive.google.com/file/d/1X5E3aCgydauVNwc5jFZDHmXT8cXiRyFB/view?usp=sharing
https://drive.google.com/file/d/1DYe4DNyfpEdDmI5ToIrpPz3t7OOg8vK0/view?usp=sharing
https://drive.google.com/file/d/1XXIo8RgsTt8_22F0hoa6O8S2T8s1vflu/view?usp=sharing

try follow this step by step in order (read till end):

• Disconnect from internet and close any background apps.
• Uninstall every gpu driver using DDU (clean and do not restart).
• Uninstall all the processors (is a must, should be 16 on yours since it's 16 threads, also when it asks for restart, click on no and keep uninstalling all processors) on device manager like this:
  
  
  
  
  
• Uninstall AMD Chipset Software in control panel (if there is none, skip it.)
  
  
• restart the pc to bios, disable AMD fTPM and secure boot, save and exit, go to bios again, flash to the latest bios (version 7C91v1A with agesa 1.2.0.7), go to bios after finished updating, then load default or optimized settings, disable CSM, enable Above 4G Decoding and Resizable bar option (these 2 options wont be available unless CSM is disabled), then save and exit.
  
  
• boot up to windows and install the latest Chipset driver (should be ver 4.06.xx), then reboot. after that check in Control Panel > Uninstall a Program > AMD Chipset Software and see if its already ver 4.06.xx that's installed.
  
  
• Install the latest nvidia driver, and then connect to internet.
  
  *do this all offline until reboot after installing chipset driver, put ram on slot A2 and B2 (slot 2 and 4) if your sticks are only 1 pair, also you may reboot to bios after all of this to set the XMP (and previous settings you did). Download needed files (highlighted word) before doing step 1, do the step by orders.
  
  
• Run cmd as admin, then do chkdsk /x /f /r, after that do sfc /scannow
  
  
• And check windows update if there is any and install them (except optional update).
  
  
• Make sure the psu connected to the gpu is 1 pcie cable per 1 slot (use main cable, not the branches/split) like this:
  
  

 

[johnbl]

most likely you have a driver overwriting memory it does not own. this causes a bucheck later when the driver that owns the memory uses it and crashes.
you should look for updated driver for your newtek software and droid software. it you can not find updates then you would have to run verifier on the drivers to find out which driver is corrupting system memory. Verifier will call a bugcheck at the time of corruption and will name the driver that wrote to memory it does not own. Or you can remove software. verifier is faster but sometimes people have issues where they just can not boot after running it and have to reinstall.
normally, when you get bugchecks that involve access violations you would want to run memtest86 to verify your memory timings.
In this case you can do that but memory contents looked like a driver bug rather than a memory timing bug.
--------------------
(dump from june 15)
looks like some driver corrupted a timer table:
likely to be caused by: your newtek drivers or your android software. yuu should check for updates as a first fix attempt.

newtek_wdm_ks.sys (may 28 2021)
newtek_autioPortclass.sys (june 25 2021)

droidcam.sys (apr 2020) (*** see if you can update this file)
droidcamvideo.sys (apr 2021)


something corrupted the timer table, then a browser attempted to use its timer and got a bugcheck from the corruption. it was not likely to be the cause of the corruption, just the victim.
will take a quick look at the other bugchecks to see if they give more clues to the cause.
------------
dump dated june 17
second bugcheck also looks like memory corruption
by a driver.
new added suspect drivers:
amdryzenmasterdriver.sys (overclock driver is now running)
two copies of ntiolib_x64.sys (now running)
gpu_z_v2.sys (now running)

bugcheck caused by some driver writing the number 10 over memory it does not own and corruption some network structure and causing the bugcheck.

(remove the added drivers using microsoft autoruns64.exe from here:Autoruns for Windows - Windows Sysinternals | Microsoft Docs
---------------
dump from 2/23
buchceck due to some access violation in
some background proecss.

same driver problems as before:
-------------
second dump from 2/23 was an access violation in wdfilter
would need kernel dump to look at logs for this one.

 

[zyd2001]

most likely you have a driver overwriting memory it does not own. this causes a bucheck later when the driver that owns the memory uses it and crashes.
you should look for updated driver for your newtek software and droid software. it you can not find updates then you would have to run verifier on the drivers to find out which driver is corrupting system memory. Verifier will call a bugcheck at the time of corruption and will name the driver that wrote to memory it does not own. Or you can remove software. verifier is faster but sometimes people have issues where they just can not boot after running it and have to reinstall.
normally, when you get bugchecks that involve access violations you would want to run memtest86 to verify your memory timings.
In this case you can do that but memory contents looked like a driver bug rather than a memory timing bug.
--------------------
(dump from june 15)
looks like some driver corrupted a timer table:
likely to be caused by: your newtek drivers or your android software. yuu should check for updates as a first fix attempt.

newtek_wdm_ks.sys (may 28 2021)
newtek_autioPortclass.sys (june 25 2021)

droidcam.sys (apr 2020) (*** see if you can update this file)
droidcamvideo.sys (apr 2021)


something corrupted the timer table, then a browser attempted to use its timer and got a bugcheck from the corruption. it was not likely to be the cause of the corruption, just the victim.
will take a quick look at the other bugchecks to see if they give more clues to the cause.
------------
dump dated june 17
second bugcheck also looks like memory corruption
by a driver.
new added suspect drivers:
amdryzenmasterdriver.sys (overclock driver is now running)
two copies of ntiolib_x64.sys (now running)
gpu_z_v2.sys (now running)

bugcheck caused by some driver writing the number 10 over memory it does not own and corruption some network structure and causing the bugcheck.

(remove the added drivers using microsoft autoruns64.exe from here:Autoruns for Windows - Windows Sysinternals | Microsoft Docs
---------------
dump from 2/23
buchceck due to some access violation in
some background proecss.

same driver problems as before:
-------------
second dump from 2/23 was an access violation in wdfilter
would need kernel dump to look at logs for this one.

I believe all these drivers should be OK since I installed them several months ago. I updated or removed most of them, I will see if BSOD still happen.
I just find an older minidump, it looks like something wrong with the netadaptercx.sys. I will also update my network driver.
https://drive.google.com/file/d/1Wf7bX76kEMd0Us7zbY6Pmr2KhRvnv39j/view?usp=sharing

 

[johnbl]

I believe all these drivers should be OK since I installed them several months ago. I updated or removed most of them, I will see if BSOD still happen.
I just find an older minidump, it looks like something wrong with the netadaptercx.sys. I will also update my network driver.
https://drive.google.com/file/d/1Wf7bX76kEMd0Us7zbY6Pmr2KhRvnv39j/view?usp=sharing

your only fix would be to update or remove the offending driver.
it looks like a common driver coding bug.
where the coder dereferenced incorrectly and passed the contents of a memory address to a function rather than the memory address.

in the debugger I should see the call looking like this:
fffff8011449fec3 (this would be a pointer to kernel memory)
the contents would be a size then some data

when people make this coding mistake the debugger just sees the size and the value looks like this:
00000000000000002
(this is most likely the size for the buffer, not a random number)
(the system would assume 00000000000000002 would be a pointer to usermode memory which would be invalid and would call a bugcheck)

bad ram generally would not have this type of corruption.


if you can not get a update to the drivers, you will have to run verifier to prove which driver is causing the corruption. After you find the driver your only fix is to remove it or update it. verifier will check every memory allocation by the verified drivers and will call a bugcheck when a error is made.

 

[zyd2001]

your only fix would be to update or remove the offending driver.
it looks like a common driver coding bug.
where the coder dereferenced incorrectly and passed the contents of a memory address to a function rather than the memory address.

in the debugger I should see the call looking like this:
fffff8011449fec3 (this would be a pointer to kernel memory)
the contents would be a size then some data

when people make this coding mistake the debugger just sees the size and the value looks like this:
00000000000000002
(this is most likely the size for the buffer, not a random number)
(the system would assume 00000000000000002 would be a pointer to usermode memory which would be invalid and would call a bugcheck)

bad ram generally would not have this type of corruption.


if you can not get a update to the drivers, you will have to run verifier to prove which driver is causing the corruption. After you find the driver your only fix is to remove it or update it. verifier will check every memory allocation by the verified drivers and will call a bugcheck when a error is made.

I just got a new SYSTEM_SERVICE_EXECEPTION BSOD, but this time it says the problem is from nvlddmkm.sys. I will try to reinstall NVIDIA driver.
The minidump file:
https://drive.google.com/file/d/1zZ-r_Stjeoj1Gg9N_Se8bO27LWNHbUoV/view?usp=sharing

 

[johnbl]

I just got a new SYSTEM_SERVICE_EXECEPTION BSOD, but this time it says the problem is from nvlddmkm.sys. I will try to reinstall NVIDIA driver.
The minidump file:
https://drive.google.com/file/d/1zZ-r_Stjeoj1Gg9N_Se8bO27LWNHbUoV/view?usp=sharing

stack corrupted, raw stack looks like msedge.exe calling some functions, then a directx call that broke and called an exception handling routine that ended passing off to the nvidia graphic kernel, the graphic kernel bugchecked due to a unknown function call.

would guess that some driver is corrupting driver memory space
debugger does not report any corrupted files

 

[zyd2001]

stack corrupted, raw stack looks like msedge.exe calling some functions, then a directx call that broke and called an exception handling routine that ended passing off to the nvidia graphic kernel, the graphic kernel bugchecked due to a unknown function call.

would guess that some driver is corrupting driver memory space
debugger does not report any corrupted files

I updated Nvidia drivers and the bluescreen didn't show until recently I got two new BSODs.
BluescreenViewer says first is caused by NetAdapterCX.sys so I updated my network drivers. However, the second one shows ntoskrnl.exe again. Could you help me take a look?
All these BSODs happens when I watch videos or browse some websites. It never occurs when I playing games.
https://drive.google.com/file/d/1d11I5Yi-Y9fBKCV5WLXv6UUj1m-5jtOP/view?usp=sharing

081722-8234-01.dmp

drive.google.com

 

[Koekieezz]

I updated Nvidia drivers and the bluescreen didn't show until recently I got two new BSODs.
BluescreenViewer says first is caused by NetAdapterCX.sys so I updated my network drivers. However, the second one shows ntoskrnl.exe again. Could you help me take a look?
All these BSODs happens when I watch videos or browse some websites. It never occurs when I playing games.
https://drive.google.com/file/d/1d11I5Yi-Y9fBKCV5WLXv6UUj1m-5jtOP/view?usp=sharing

081722-8234-01.dmp

drive.google.com

tried what i've suggested in the 1st post?

 

[Colif]

John may not be back but I had a look at the dump files and got this result

File: 081722-8234-01.dmp (Aug 18 2022 - 09:21:45)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 6 Day(s), 20 Hour(s), 37 Min(s), and 42 Sec(s)

that one appears to be lan drivers
Download Win11 Auto Installation Program (NetAdapterCx) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

I have seen this cause errors before
Jan 27 2022 - BstkDrv_nxt.sys - BlueStacks driver

MSI B550 Gaming Edge wifi

have you updated bios recently as the dump isn't showing BIOS info which often means its an old bios

 

[zyd2001]

John may not be back but I had a look at the dump files and got this result

File: 081722-8234-01.dmp (Aug 18 2022 - 09:21:45)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 6 Day(s), 20 Hour(s), 37 Min(s), and 42 Sec(s)

that one appears to be lan drivers
Download Win11 Auto Installation Program (NetAdapterCx) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

I have seen this cause errors before
Jan 27 2022 - BstkDrv_nxt.sys - BlueStacks driver



have you updated bios recently as the dump isn't showing BIOS info which often means its an old bios

I actually updated my BIOS after I post this thread which should be the latest. I updated my lan driver after this BSOD, but I then got another one the day before yesterday. It says UNEXPECTED_KERNEL_MODE_TRAP and is related to ntoskrnl.exe
https://drive.google.com/file/d/1d11I5Yi-Y9fBKCV5WLXv6UUj1m-5jtOP/view?usp=sharing

Is the bluestacks driver a possible cause?

 

[Colif]

File: 082122-11734-01.dmp (Aug 22 2022 - 08:08:32)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP (7F)]
*** WARNING: Unable to verify timestamp for Netwtw10.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 3 Day(s), 22 Hour(s), 44 Min(s), and 32 Sec(s)
intel wifi drivers

I almost suggested you update those before but it pointed at realtek in a way
May 24 2022 - Netwtw10.sys - Intel Wi-Fi driver
run this and see if its got newer - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

 

[zyd2001]

File: 082122-11734-01.dmp (Aug 22 2022 - 08:08:32)
BugCheck: [UNEXPECTED_KERNEL_MODE_TRAP (7F)]
*** WARNING: Unable to verify timestamp for Netwtw10.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 3 Day(s), 22 Hour(s), 44 Min(s), and 32 Sec(s)
intel wifi drivers

I almost suggested you update those before but it pointed at realtek in a way
May 24 2022 - Netwtw10.sys - Intel Wi-Fi driver
run this and see if its got newer - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

I checked and they are up to date. I uninstalled bluestacks. I will be back if I got another BSOD.

 

[Colif]

errors bouncing around

I would be tempted to run this on ram
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it
it will take a while to run, so overnight good time.

 

[zyd2001]

errors bouncing around

I would be tempted to run this on ram
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it
it will take a while to run, so overnight good time.

Thanks, I will try this tonight