Several BSODs with Windows 10

[Penelope79]

Hello everyone,
a couple of weeks ago I finally installed Windows 10 on my PC (I upgraded from Windows 7). However, I already run into the BSODs apparently for several different reasons, which are preventing me to use the computer normally (for instance, the last BSOD appeared when I tried to plug my iPhone 8 to the PC: it was the first time since I installed Windows 10 and, for the life of me, I can't get the iPhone recognized by the PC or, if it does, the BSOD shows up again).

I tried to find out more by letting WhoCrashed check the dump files. These are the results occurred on different occasions:

On Mon 27/05/2019 16:45:52 GMT your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\052719-36843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8047CC93B77)
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.



On Mon 27/05/2019 16:45:52 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xBEB7)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8047CC93B77)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
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 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 Thu 30/05/2019 21:23:10 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\053019-39734-01.dmp
This was probably caused by the following module: asrappcharger.sys (AsrAppCharger+0x1730)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80516538676, 0xFFFFF506A2DA81E8, 0xFFFFF506A2DA7A30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\asrappcharger.sys
product: Windows ® Win 7 DDK driver
company: Windows ® Win 7 DDK provider
description: ASRock App Charger Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: asrappcharger.sys (ASRock App Charger Driver, Windows ® Win 7 DDK provider).
Google query: asrappcharger.sys Windows ® Win 7 DDK provider SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 30/05/2019 21:23:10 GMT your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: asrappcharger.sys (AsrAppCharger+0x1730)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80516538676, 0xFFFFF506A2DA81E8, 0xFFFFF506A2DA7A30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\asrappcharger.sys
product: Windows ® Win 7 DDK driver
company: Windows ® Win 7 DDK provider
description: ASRock App Charger Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: asrappcharger.sys (ASRock App Charger Driver, Windows ® Win 7 DDK provider).
Google query: asrappcharger.sys Windows ® Win 7 DDK provider SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

CHDSK/Scannow didn't find any error, the same goes for WhySoSlow. I also tried Dism /Online /Cleanup-Image /RestoreHealth.
I also attach my specs, just in case:

OS
Windows 10 Pro 64-bit
CPU
AMD FX-8320E 34 °C Vishera 32nm
RAM
16,0GB DDR3 @ 799 MHz (10-10-10-30)
Motherboard
ASRock 970A-G/3.1 (CPUSocket) 33 °C
Graphics
HP 27es (1920x1080@59Hz)
2048 MBATI AMD Radeon R7 360 Series (Sapphire/PCPartner) 49 °C
RAM
465GB Seagate ST3500413AS ATA Device (SATA) 42 °C
931GB Western Digital WD Elements 1042 USB Device (USB (SATA)) 38 °C
Optical drives
ASUS DRW-24F1MT ATA Device
Audio
Realtek High Definition Audio

Any help will be very much appreciated. Thank you so much in advance!

 

[Trouble]

Have you addressed the problem identified in your post above.
As is often the case, motherboard utilities included on the disk that comes with the motherboard are generally junk and often cause issues.
Yours seems to point to your ASRock - AppCharger Driver
Uninstall it, along with all the other superfluous motherboard utilities that you might have loaded
OR
find asrappcharger.sys in C:\Windows\System32\Drivers and break it by renaming it to asrappcharger.OLD

 

[Penelope79]

Hey Trouble,
thank you so much for your reply.
I followed your suggestion and renamed the asrappcharger file into asrappcharger.OLD: now I can finally plug my iPhone to the PC, thanks!

Unfortunately though, I still get BSOD, though for a different reason:

On Mon 03/06/2019 18:54:40 GMT your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x7DE9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803405D9BF7, 0xFFFFB5800E660A10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.

Do you have any further suggestion? Thank you!

 

[Trouble]

Go to the C:\Windows\MEMORY.DMP file that your crash is producing.
Right click it and choose "Send to" from the context menu and then "Compressed (zipped) folder" from the send to options presented.

Attach that (the zipped product) to your next post and we'll see if there is anything in there that stands out as a possible problem.

 

[Penelope79]

thank you Trouble!

I am adding a link: file is apparently too big to attach.

 

[Trouble]

Yep, that can sometimes happen, although they are basically just text files and will generally compress quite nicely.
I have found it a good idea to use this instead.....

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

The detail of the report is not as robust but the "small" memory dump is quick and easy to work with.

IF you get a chance, do that switch around and after you get a couple new dump files attach them to your next post.

In the meantime no link has appeared as you suggested above.

 

[Penelope79]

Hi Trouble,
thanks for your reply. I followed your suggestions and I attached the latest 2 dumps.
I'm also adding the again the link to the bigger file, just in case: LINK

 

[Trouble]

I'm seeing some indication that there may be an issue with Bitdefender a couple drivers are mentioned in the dump files
gzflt.sys and atc.sys
You may want to consider uninstalling that for a while and see how your system gets on with just the native Windows Defender and Windows Firewall products.

Uninstall Bitdefender

Uninstall Bitdefender

www.bitdefender.com

One of the dump files calls out the following driver
athurx.sys

STACK_TEXT:
fffff30d`128a7728 fffff805`407cd2a8 : 00000000`000001ce ffffdd01`cdad0200 ffffcc8e`2f2dc080 00000000`00000000 : nt!KeBugCheckEx
fffff30d`128a7730 fffff805`407ccaa6 : 00000000`00000000 fffff805`4070e674 fffff805`3f1a2180 fffff805`3f1a2180 : nt!SwapContext+0x528
fffff30d`128a7770 fffff805`406ebf47 : ffffcc8e`2f2dc080 00000000`00000000 ffffdd01`cdad0200 00000000`00000000 : nt!KiSwapContext+0x76
fffff30d`128a78b0 fffff805`406ebab9 : 00000000`00000000 00001f80`00e90080 ffffcc8e`2f2dc180 fffff805`40699528 : nt!KiSwapThread+0x297
fffff30d`128a7970 fffff805`406ea840 : ffffdd01`cdac0100 fffff805`00000000 00000000`00000000 fffff30d`128a7a81 : nt!KiCommitThreadWait+0x549
fffff30d`128a7a10 fffff805`43f6f597 : fffff30d`128a7b10 00000000`00000000 00000000`00000000 fffff805`468d2500 : nt!KeWaitForSingleObject+0x520
fffff30d`128a7ae0 fffff805`46816f8e : ffffcc8e`2dca5030 00000000`00000010 fffff30d`128a7ba0 00000000`00000000 : ndis!NdisMSleep+0x67
fffff30d`128a7b60 ffffcc8e`2dca5030 : 00000000`00000010 fffff30d`128a7ba0 00000000`00000000 00000000`00000000 : athurx+0x6f8e
fffff30d`128a7b68 00000000`00000010 : fffff30d`128a7ba0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffcc8e`2dca5030
fffff30d`128a7b70 fffff30d`128a7ba0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000052`00000000 : 0x10
fffff30d`128a7b78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000052`00000000 ffffcc8e`2dca5030 : 0xfffff30d`128a7ba0

It has a pretty old time stamp of 4/20/2011
I believe I would definitely address that by either updating the driver if possible or acquiring a new network adapter with certified Windows 10 support.

Athurx.sys is a type of SYS file associated with Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter developed by Atheros Communications, Inc.

Additionally I still see a couple drivers associated with your motherboard manufacturer.
AsrRamDisk.sys and AsrVDrive.sys
I'm not at all familiar with either of these two drivers nor how they came to be installed on your system.
I have no way of knowing if they are in some way essential (although I suspect not) so I'll leave their final disposition up to you after you do some research.
You can try some general Google searches but you may find more help on the ASRock boards.

 

[Penelope79]

Thank you so much Trouble.
I found out AsrRamDisk.sys and AsrVDrive.sys to be both Windows 7 ddk driver related (as well as AsrAppCharger.sys) but I couldn't find any further information, hence I don't know if they can be updated, uninstalled or renamed them into .OLD, too.
I will definitively try to uninstall Bitdefender and see what happens (although unfortunately I paid for the full version, it is not the free one ).

 

[Trouble]

My preference is to break them by finding them in C:\Windows\System32\Drivers folder and removing the .sys extension and replacing it with .OLD
Of course, I am generally fearless as I always have a current full system image to fall back on in case something unintended happens
OR
I boot to the Recovery Environment with my Windows 10 boot media and drop to a DOS command prompt and revert my changes but that's a little old school.

As far as Bitdefender is concerned I've been reading a lot of stuff on the web that suggests that it might be having some problems keeping up with all the Windows 10 updates. They probably have their own support board where you might do some light researching.
You can generally always reinstall it at a later point once you have confirmed that it is not an issue.

Unfortunately this is often a lot of hunt and peck, trial and error and unfortunately there is nothing in your dump files thus far that set of any lights and sirens.

Seems each of your crashes was moaning about something different and it might be an accumulation of bad drivers taking turns.

What did you decide to do about the Atheros Network adapter?

 

[Penelope79]

Thank you so much for your help, Trouble. I would break the files too by removing and replacing the .sys/.OLD extension, but since I have yet to find other info about those two files I need to be careful. I'll research even further and hopefully, I'll find something.
As for the TP-LINK adapter, I think I will buy a new one in the near future: apparently, the one I have is not fully supported by Windows 10, although I suspect it is not the main cause to the issues I'm encountering since so far it's been a one-time occurrence.