F5F Stay Refreshed Software Operating Systems Multiple BSODs occur, but the cause is unclear—PC freezes and restarts automatically?

Multiple BSODs occur, but the cause is unclear—PC freezes and restarts automatically?

Multiple BSODs occur, but the cause is unclear—PC freezes and restarts automatically?

Pages (2): Previous 1 2
K
Kayzan_
Senior Member
252
04-05-2021, 12:00 PM
#11
Have you checked the power supply's rails using a digital multimeter while it was running? If the voltage or current is more than 5% off the specifications, then replace the power supply.
K
Kayzan_
04-05-2021, 12:00 PM #11

Have you checked the power supply's rails using a digital multimeter while it was running? If the voltage or current is more than 5% off the specifications, then replace the power supply.

B
ByFeNix1350
Senior Member
502
04-10-2021, 07:36 PM
#12
Thank you for the kernel dump. This is necessary since we can pull the event trace information from the dump and format it so the Windows Performance Analyzer (WPA) can present it effectively. With WPA, we can view all the DPCs that were active and pinpoint those that were running longer than anticipated. Your BSOD occurred because the system remained elevated for more than 2 seconds, likely due to DPCs being executed. The WPA results for your kernel dump are included below.

The list on the left contains every running DPC (ntoskrnl.exe is not a DPC—it's the Windows kernel), ordered from longest to shortest execution time. At the end of the list is the actual runtime for each DPC in milliseconds. Microsoft advises that no DPC should run longer than 100 microseconds.

From the WPA output, we observe two drivers exceeding the 100 microsecond limit—ndis.sys and storport.sys—and ndis.sys is the most problematic, running for 723 microseconds. When we combine their durations, they account for nearly one second of DPC activity, which is half the allowed maximum.

The ndis.sys driver is a high-level networking component, reinforcing my earlier point in post #3: a network operation was likely ongoing when those BSODs happened. This suggests a networking task was contributing to the issue.

If you have already updated the LAN adapter driver, it’s possible the problem lies with the LAN adapter itself or its configuration settings if you changed them. I recommend using a budget USB WiFi adapter and disabling the built-in LAN adapter via Device Manager. Restart the system (to clear the LAN driver), then test with the USB WiFi card to determine if the BSODs cease.
B
ByFeNix1350
04-10-2021, 07:36 PM #12

Thank you for the kernel dump. This is necessary since we can pull the event trace information from the dump and format it so the Windows Performance Analyzer (WPA) can present it effectively. With WPA, we can view all the DPCs that were active and pinpoint those that were running longer than anticipated. Your BSOD occurred because the system remained elevated for more than 2 seconds, likely due to DPCs being executed. The WPA results for your kernel dump are included below.

The list on the left contains every running DPC (ntoskrnl.exe is not a DPC—it's the Windows kernel), ordered from longest to shortest execution time. At the end of the list is the actual runtime for each DPC in milliseconds. Microsoft advises that no DPC should run longer than 100 microseconds.

From the WPA output, we observe two drivers exceeding the 100 microsecond limit—ndis.sys and storport.sys—and ndis.sys is the most problematic, running for 723 microseconds. When we combine their durations, they account for nearly one second of DPC activity, which is half the allowed maximum.

The ndis.sys driver is a high-level networking component, reinforcing my earlier point in post #3: a network operation was likely ongoing when those BSODs happened. This suggests a networking task was contributing to the issue.

If you have already updated the LAN adapter driver, it’s possible the problem lies with the LAN adapter itself or its configuration settings if you changed them. I recommend using a budget USB WiFi adapter and disabling the built-in LAN adapter via Device Manager. Restart the system (to clear the LAN driver), then test with the USB WiFi card to determine if the BSODs cease.

Pages (2): Previous 1 2