Question multiple BSOD/ crashes

Feb 8, 2020
13
0
10
0
Dear all,

For the last year i have had on and off trouble with my PC. Sometimes the problem is gone for a few weeks/months, making me believe I solved it, but then the issue comes back again, and it is driving me crazy.

During usage my pc ramdomly crashes, in around 50% of the cases I get a BSOD screen, the most common being Kmode_exception_not_handled, which I let windows handle it till it goes to restart. The other half of the time everything freezes, and my screen (either goes black, or stuck on what it was displaying, but jumping around over the screen) and sound start freaking out, and the only solution is to cut the power. In both cases the PC refuses to restart (fans start running, screen activates but stays black, fans calm down and nothing happens anymore till i cut the power again, I won't even get the Asus screen) till half a hour to (worst case) 2 days later.

Things I tried to fix the issue:
disabled fast start-up
SFC-scan - no errors
replaced afd.sys (since who-chrashed said it was the culprit on one occasion)
Windows memory diagnostics - no errors
Memtest86 - 8 passes - no errors
fully updated the OS using windows update
re-install of win10
manually updated every driver using device manager->search online for best driver
manually updated my Intel-drivers using their site (since it said somewhere that the Intel networkdriver was the most likely culprit.

I tried using Tweakbits driverupdater, but my antivirus (NOD32) kept nagging me about it en it didnt seem to work since it detected exactly 0 drivers on my pc.

System:
ASUS all-in-one Z240IC PC series

Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: Z240IC-H170, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 8440692736 bytes (7,9GB)
NVIDIA GeForce GTX 960m
BIOS Version/Date: American Megatrends Inc. 0704, 7-3-2016

note: I can't open up my pc as it is an all-in-one, and opening it up would damage the system (critical designflaw by asus IMO, didnt know this till after I had bought the system :( )

Who crashed error analysis:
On Sat 8-2-2020 10:33:11 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020820-31359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3D (0xFFFFF80167669D28, 0xFFFFF80167669570, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8-2-2020 10:33:11 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!KeSetEventBoostPriority+0x55)
Bugcheck code: 0x3D (0xFFFFF80167669D28, 0xFFFFF80167669570, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2-2-2020 02:33:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020220-31203-01.dmp
This was probably caused by the following module: unknown_module_0000000000010000.sys (0xFFFFFFFFFFFFFFFF)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8073D7C82C5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error.
Google query: unknown_module_0000000000010000.sys KMODE_EXCEPTION_NOT_HANDLED



On Tue 21-1-2020 21:54:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012120-30906-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF8047F9687A6)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8047F9687A6, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 13-1-2020 21:24:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011320-29046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1C7 (0x0, 0xFFFFAA0AE17A3000, 0x3185C547, 0x237DA3)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

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 2-12-2019 22:40:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120219-28140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x139 (0x3, 0xFFFFAC814BC5F5A0, 0xFFFFAC814BC5F4F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 26-11-2019 15:08:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112619-20375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0xFFFFD783DF20E6B8, 0x2, 0x0, 0xFFFFF802662338B3)
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 Tue 26-11-2019 12:32:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112619-23281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8056864AFD3, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 26-11-2019 12:12:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112619-25828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073F845D9D, 0xFFFF90877E096A70, 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.

Dumpfiles:
dumpfiles on filebin

My thanks in advance for the help, I hope we can solve it fast.
Kind regards
-Maarten
 
Last edited:
Feb 8, 2020
13
0
10
0
Neither, it is an all-in-one desktop, where evreything is put right behind the screen, like a imac, of the series in the link below

https://www.asus.com/Product-Compare/?products=HYS59NKaVb4GaqRR&b=0

Normally I would add more specific specs of the pc itself, but I don't know exactly and currently my pc refuses to start (it crashed while I tried to make the first post, hence the lack of dump info). I will add more info ASAP, as soon as my PC will start up again.
 
Feb 8, 2020
13
0
10
0
o, I noticed I put the wrong name in my attempted solutions, fixed it.

But yes, I ran memtest86 for 8 passes, had 0 errors
 
Feb 6, 2020
99
7
45
1
RAM memory corruption. Have you performed Memtest86?
For what it's worth, memory corruption doesn't always mean bad RAM. If you have a reliable trigger for it (like I sometimes do), it can more often than not point to a driver as the cause.

Fun fact: a driver trying to write to 0x0 (system-reserved NULL) is considered memory corruption by Windows.
 

Abhinav2005

Upstanding
Jan 1, 2020
392
104
370
3
For what it's worth, memory corruption doesn't always mean bad RAM. If you have a reliable trigger for it (like I sometimes do), it can more often than not point to a driver as the cause.

Fun fact: a driver trying to write to 0x0 (system-reserved NULL) is considered memory corruption by Windows.
I know that memory corruption doesn't always mean bad RAM. I just want to be confirm.
SSD or HDD health?
 
Reactions: TejasAnand

Colif

Win 10 Master
Moderator
have to love those custom errors. I sent dumps to a friend as majority of time BSOD blame ntoskrnl as its a placeholder and it can't tell. If the windows kernel was that flakey we would have noticed by now.

afd.sys = Ancillary Function Driver for WinSock. It is related to Internet functions.
System specs show it has Realtek LAN - here are the newest drivers - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

I can't tell with the rest but the dumps should show more.
 
Reactions: maretan
Feb 8, 2020
13
0
10
0
I know that memory corruption doesn't always mean bad RAM. I just want to be confirm.
SSD or HDD health?
checking using wmic says the status is OK

have to love those custom errors. I sent dumps to a friend as majority of time BSOD blame ntoskrnl as its a placeholder and it can't tell. If the windows kernel was that flakey we would have noticed by now.

afd.sys = Ancillary Function Driver for WinSock. It is related to Internet functions.
System specs show it has Realtek LAN - here are the newest drivers - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

I can't tell with the rest but the dumps should show more.
thanks, used their auto-installer to reinstall all of their drivers, just to be sure. Let me know if you get more info out of the other dumps
 

gardenman

Admirable
Ambassador
Hi, I ran the dump files through the debugger and got the following information: https://menstrualtapir.htmlpasta.com/
File information:011320-29046-01_-_Copy.dmp (Jan 13 2020 - 15:24:09)
Bugcheck:STORE_DATA_STRUCTURE_CORRUPTION (1C7)
Probably caused by:memory_corruption (Process: MemCompression)
Uptime:0 Day(s), 1 Hour(s), 22 Min(s), and 06 Sec(s)

File information:012120-30906-01_-_Copy.dmp (Jan 21 2020 - 15:54:56)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 1 Hour(s), 55 Min(s), and 44 Sec(s)

File information:020220-31203-01_-_Copy.dmp (Feb 1 2020 - 20:33:27)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Driver warnings:*** WARNING: Unable to verify timestamp for Unknown_Module_e3b430a4`0000002a
Probably caused by:Unknown_Image (Process: ?)
Uptime:0 Day(s), 15 Hour(s), 21 Min(s), and 16 Sec(s)

File information:020820-31359-01_-_Copy.dmp (Feb 8 2020 - 04:33:11)
Bugcheck:INTERRUPT_EXCEPTION_NOT_HANDLED (3D)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 09 Min(s), and 04 Sec(s)

File information:101619-26562-01_-_Copy.dmp (Oct 15 2019 - 21:34:15)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 18 Hour(s), 40 Min(s), and 26 Sec(s)

File information:110519-30593-01_-_Copy.dmp (Nov 5 2019 - 14:42:12)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 5 Hour(s), 59 Min(s), and 27 Sec(s)

File information:112619-20375-01_-_Copy.dmp (Nov 26 2019 - 09:08:29)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Driver warnings:*** WARNING: Unable to verify timestamp for igdkmd64.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 1 Hour(s), 43 Min(s), and 27 Sec(s)

File information:112619-23281-01_-_Copy.dmp (Nov 26 2019 - 06:32:37)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 19 Min(s), and 11 Sec(s)

File information:112619-25828-01_-_Copy.dmp (Nov 26 2019 - 06:12:42)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: RiotClientServices.exe)
Uptime:0 Day(s), 1 Hour(s), 22 Min(s), and 15 Sec(s)

File information:120219-28140-01_-_Copy.dmp (Dec 2 2019 - 16:40:27)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 1 Hour(s), 44 Min(s), and 56 Sec(s)
Possible Motherboard page: https://www.asus.com/us/All-in-One-PCs/Zen-AiO-Pro-Z240IC/specifications/
There is a BIOS update available for your system. You are using version 704 and the latest is version 805. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

That paste site really needs to choose better words for the addresses they provide.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: maretan
Feb 8, 2020
13
0
10
0
Windows Memory Diagnostics isn't the most accurate; make a USB stick with memtest86+ and test each stick at least 4 passes. This will eliminate Windows as a possible problem area.
Wasn't that to test the RAM? He asked if I could check my SSD/HDD health, to which google said I could use wmic in the command-line.

For the RAM I did use memtest86 for 8 passes (as stated in my openingpost and as an answer before) but on the whole RAM package at once as I have no way to physically access the hardware due to the way ASUS constructed the model without sending the PC to the manufacturer.
 
Feb 6, 2020
99
7
45
1
Wasn't that to test the RAM? He asked if I could check my SSD/HDD health, to which google said I could use wmic in the command-line.

For the RAM I did use memtest86 for 8 passes (as stated in my openingpost and as an answer before) but on the whole RAM package at once as I have no way to physically access the hardware due to the way ASUS constructed the model without sending the PC to the manufacturer.
Ah yikes, my bad. I misunderstood what wmic does.

I don't know why Asus have decided to lock users out of servicing their own hardware; a friend of mine had an Asus desktop with a GTX 650 in it that was literally soldered to the PCIe slot, it's so odd.

Did memtest86 turn up anything?
 

Colif

Win 10 Master
Moderator
Error from Jan 13 - Dump txt is talking about virtual memory
Error on 22 Jan mentions AFD.sys which is related to Internet activities so I would update LAN drivers
Error on 1 Feb is the unknown module that even debugger doesn't know.

one BSOD blamed the Intel graphics drivers - igdkmd64.sys - although that was in November. There are newer versions on the Asus website below.

Jul 09 2015rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver
update this - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

i won't tell you to update nvidia drivers as if they work, stick with them. Newer ones aren't any better.

could update BIOS, there are several since your version - https://www.asus.com/us/All-in-One-PCs/Zen-AiO-Pro-Z240IC/HelpDesk_Download/
 
Reactions: maretan
Feb 8, 2020
13
0
10
0

gardenman

Admirable
Ambassador
According to the dump file, you have:
MOTHERBOARD: ASUSTeK COMPUTER INC. Z240IC-H170
BIOS: American Megatrends Inc. 0704 (03/07/2016)

It looks like you stated above you have the 960m. Try the 5th one down.
Version 0805 2017/01/036.99 MBytes
Update Z240IC-H170 GTX960M BIOS Version 0805
Improve System Stability

Verify and double check everything I've typed above before trying it.

 
Reactions: maretan
Feb 8, 2020
13
0
10
0
Thanks a lot, after double checking it works now.

I kinda feel dumb now for not realizing how it was structured, but I never worked with bios before
 
Feb 8, 2020
13
0
10
0
Lets see if BIOS and LAN update fix it?
This was exactly my idea, so I started using my pc like normal (a.k.a I started gaming with youtube in the background) after the updates, but within an hour a new crash occured. A new BSOD-code for me, System thread exception not handled. According to google a problem with the drivers. Unfortunatly no dump files were generated, as my pc fully froze right when the BSOD popped up.

I just did the double check, BIOS, Lan driver and Intel graphics driver all have the new versions.

EDIT: second hard crash just happened an hour ago
 
Last edited:
Feb 8, 2020
13
0
10
0
Well it seems it didn't help, have had around 4 or 5 new crashes these last two days, pretty fast after startup now, around 10 to 15min up time on average. I only got a BSOD twice, both on which the PC instantly froze en refused to go into recovery, and therefore not generating any minidumps. I got one System thread exception not handled, and one Kmode exception not handled.

What worries me most is that I am unable to reboot the pc after a crash and have to wait a few hours before my PC gives a reaction. Is this normal for this kind of chrashes?
All my pc does when i try to turn it on is spin up the fans, and it starts to power my screen (it flashes brightly for 1 or 2 frames and then you get a black screen again, but you can tell it is powered). And thats it, it won't even show a factory screen or allow me to go into bios.

Any suggestions on what to try, possible sollutions or other diagnostics I can use to help shed light on this matter?
 

gardenman

Admirable
Ambassador
2 things you said describe typical heat related problems:
#1. It crashes 10 to 15 minutes after boot up.
#2. It takes a few hours before it will boot again.

Do you have any way to monitor temperatures for both CPU and GPU and if so, what are the temps like?
 
Feb 8, 2020
13
0
10
0
Well seems my pc is completly dead right now. Last crash happened thursday and still zero response on boot. I guess I am sending it back to Asus to let them replace the motherboard.

Thanks for the help guys, and lets hope I can get it fixed soon. Will keep you guys posted.
 

ASK THE COMMUNITY

TRENDING THREADS