Windows 10: Repeated BSOD

Repeated BSODs particularly on removal of plug-in charger

Everything runs fine while plugged in but as soon as charger removed or start the laptop without connected to the charger would lead to such BSOD.





System Information local


Computer name: LAPTOP-1U0R8J08
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: TUF Gaming FX505DV_FX505DV, ASUSTeK COMPUTER INC., FX505DV
CPU: AuthenticAMD AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx AMD8664, level: 23
8 logical processors, active mask: 255
RAM: 16978178048 bytes 15.8GB



Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 01-04-2020 14:07:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040120-10765-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2360
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF8013550A057, 0xFFFF8286C892AFD0, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 31-03-2020 21:52:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040120-10781-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2360
Bugcheck code: 0x50 0xFFFFF801F56A601B, 0x2, 0xFFFFF8020C6B6014, 0x2
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 31-03-2020 21:49:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033120-11046-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2360
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF800818785F0, 0xFFFFFD858C298E60, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 31-03-2020 21:47:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033120-17765-01.dmp
This was probably caused by the following module: fltmgr.sys 0xFFFFF80769AE8042
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF80769AE8042, 0xFFFF9301E90B4B50, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Tue 31-03-2020 19:04:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033120-10250-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2380
Bugcheck code: 0xA 0x20, 0xFF, 0x75, 0xFFFFF80416716153
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Any help would be appreciated as it has become a headache to not being able to use the laptop without being plugged in and in general bsod.

:)

 

Keyboard repeat delay and repeat speed

Hi Joseph,

I suggest you to uninstall and reinstall the keyboard driver. Follow the steps to uninstall & reinstall the keyboard driver from device manager.

• 
  Press Windows key + X from the
  Keyboard and click on Device Manager.
  
• 
  In Device Manager, double click on the
  Keyboard.
  
• 
  It will show you the device driver name, select that device and then right click on it.
  
• 
  Click on Uninstall button.
  
• 
  Restart the computer, the drivers will get automatically installed on your Windows 10.
  
• 
  Repeat the same for Mice and other pointing devices.
  

Hope it helps.

 

Multiple BSODs since Windows 10 Creators Update

Hi Carl,

In most cases, blue screen error is caused by faulty memory, corrupted device drivers, or faulty hardware. For us to provide the best resolution possible, we would like to clarify the following:

• What troubleshooting steps have you done so far to avoid repeating the steps that you've already performed?
• Have you tried the troubleshooting steps suggested on this thread? If yes, what are the results?

We're looking forward to your reply.

 

MSI 5870 BIOS Update

Still can't reproduce. Could you please post the exact BIOSes that produce the issue?