F5F Stay Refreshed Software Operating Systems The ntoskrnl.exe is experiencing crashes and problems.

The ntoskrnl.exe is experiencing crashes and problems.

The ntoskrnl.exe is experiencing crashes and problems.

M
M4sh
Member
148
02-06-2017, 07:46 AM
#1
for the past few months I've faced recurring crashes and freezes while gaming, especially when using any GPU-intensive applications. I also experienced blue screens a couple of times every two weeks. At first, I dismissed the BSOD as a random glitch or spilled spaghetti, but after reinstalling Windows and updating all drivers, the issues persisted. This situation is really frustrating. On another forum post, someone shared two minidumps from after the Windows reinstall, which I've attached here. My current system includes: an AMD Ryzen 5 1600 with 3.20 GHz, 8GB G.Skill Aegis DDR4-2400 RAM, an ASRock A320M-HDV R4 motherboard, Crucial BX500 SSD, and a Corsair CX 550 PSU. I haven't overclocked anything. The files referenced are: 042521-14078-01.dmp and 042521-15734-01.dmp.
M
M4sh
02-06-2017, 07:46 AM #1

for the past few months I've faced recurring crashes and freezes while gaming, especially when using any GPU-intensive applications. I also experienced blue screens a couple of times every two weeks. At first, I dismissed the BSOD as a random glitch or spilled spaghetti, but after reinstalling Windows and updating all drivers, the issues persisted. This situation is really frustrating. On another forum post, someone shared two minidumps from after the Windows reinstall, which I've attached here. My current system includes: an AMD Ryzen 5 1600 with 3.20 GHz, 8GB G.Skill Aegis DDR4-2400 RAM, an ASRock A320M-HDV R4 motherboard, Crucial BX500 SSD, and a Corsair CX 550 PSU. I haven't overclocked anything. The files referenced are: 042521-14078-01.dmp and 042521-15734-01.dmp.

N
Nashiko57
Senior Member
485
02-06-2017, 09:06 AM
#2
Please share your crash dump files, and I'll analyze them to identify the issues
N
Nashiko57
02-06-2017, 09:06 AM #2

Please share your crash dump files, and I'll analyze them to identify the issues

K
ko94
Member
222
02-18-2017, 09:33 AM
#3
I hope it succeeded, I just accidentally posted my first message by pressing my keyboard with my fingers.
K
ko94
02-18-2017, 09:33 AM #3

I hope it succeeded, I just accidentally posted my first message by pressing my keyboard with my fingers.

A
ATacticalCat_
Member
201
02-18-2017, 06:26 PM
#4
Take a pause to examine the list and identify the relevant items
A
ATacticalCat_
02-18-2017, 06:26 PM #4

Take a pause to examine the list and identify the relevant items

M
MBpvpEXPERT
Junior Member
17
02-18-2017, 06:52 PM
#5
Ok, what I'm going to do, is post some relevant details from the crashes, then my thoughts at the end ___ SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8013ed3773f, The address that the exception occurred at Arg3: ffffde88384c3218, Exception Record Address Arg4: ffffbd80607ee920, Context Record Address BUGCHECK_CODE: 7e PROCESS_NAME: System SYMBOL_NAME: ks!CKsPin::TransferKsIrp+6d MODULE_NAME: ks IMAGE_NAME: ks.sys ___ SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80120e60ae8, Address of the instruction which caused the bugcheck Arg3: ffffa1810bd9b200, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_CODE: 3b CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: LeagueClientUxRender.exe SYMBOL_NAME: win32kbase!ReleaseCacheDC+2f6 MODULE_NAME: win32kbase IMAGE_NAME: win32kbase.sys ___ Ok, so, two non-repeating crashes. Makes it a little harder to figure things out, but there are some steps we can take: (1) Test your RAM with MemTest86. Typically non-repeating crashes are due to massive software corruption, OR bad RAM. (2) Check your CPU and GPU temps at idle and under load. I like CPUTemp and GPUTemp because they are simple and don't take up much resident RAM, and sit nicely in the taskbar so you can always see them. (3) If enabled in BIOS, turn off XMP. Seems to cause more issues than it solves. (4) Update all drivers and BIOS on the mobo. (your mobo manufacturer will have the latest drivers and BIOS, no need to go anywhere else) This should give you enough to start with, report back on your results.
M
MBpvpEXPERT
02-18-2017, 06:52 PM #5

Ok, what I'm going to do, is post some relevant details from the crashes, then my thoughts at the end ___ SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8013ed3773f, The address that the exception occurred at Arg3: ffffde88384c3218, Exception Record Address Arg4: ffffbd80607ee920, Context Record Address BUGCHECK_CODE: 7e PROCESS_NAME: System SYMBOL_NAME: ks!CKsPin::TransferKsIrp+6d MODULE_NAME: ks IMAGE_NAME: ks.sys ___ SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80120e60ae8, Address of the instruction which caused the bugcheck Arg3: ffffa1810bd9b200, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. BUGCHECK_CODE: 3b CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: LeagueClientUxRender.exe SYMBOL_NAME: win32kbase!ReleaseCacheDC+2f6 MODULE_NAME: win32kbase IMAGE_NAME: win32kbase.sys ___ Ok, so, two non-repeating crashes. Makes it a little harder to figure things out, but there are some steps we can take: (1) Test your RAM with MemTest86. Typically non-repeating crashes are due to massive software corruption, OR bad RAM. (2) Check your CPU and GPU temps at idle and under load. I like CPUTemp and GPUTemp because they are simple and don't take up much resident RAM, and sit nicely in the taskbar so you can always see them. (3) If enabled in BIOS, turn off XMP. Seems to cause more issues than it solves. (4) Update all drivers and BIOS on the mobo. (your mobo manufacturer will have the latest drivers and BIOS, no need to go anywhere else) This should give you enough to start with, report back on your results.

L
LAX_BRA
Junior Member
4
02-22-2017, 04:27 AM
#6
I was testing deep rock galactic, which kept both the GPU and CPU under manageable temperatures—around 75°C for the GPU and 60°C for the CPU. During a bios update, another Bsod occurred, and a minidump file was attached. 042821-7640-01.dmp
L
LAX_BRA
02-22-2017, 04:27 AM #6

I was testing deep rock galactic, which kept both the GPU and CPU under manageable temperatures—around 75°C for the GPU and 60°C for the CPU. During a bios update, another Bsod occurred, and a minidump file was attached. 042821-7640-01.dmp

V
Valkxz
Member
212
02-25-2017, 04:21 PM
#7
I noticed you stopped mid-explanation. Could you clarify what you were referring to in each column?
V
Valkxz
02-25-2017, 04:21 PM #7

I noticed you stopped mid-explanation. Could you clarify what you were referring to in each column?

D
Demonsss91
Posting Freak
767
02-26-2017, 12:49 AM
#8
because of my ADS I didn’t complete the full memtest for both RAM sticks—one ran for an hour and 20 minutes while the other for 35 minutes—and nothing showed up as errors. If I really need to extend the test beyond an hour, I’ll let it run while I’m away tomorrow. I updated my BIOS to a newer version, but not the latest (from 3.30 to 3.40). Does this have any impact? And finally, how do I disable XMP on my motherboard? I only have the choice between “auto” or creating a profile, which I’m not sure how to set up either.
D
Demonsss91
02-26-2017, 12:49 AM #8

because of my ADS I didn’t complete the full memtest for both RAM sticks—one ran for an hour and 20 minutes while the other for 35 minutes—and nothing showed up as errors. If I really need to extend the test beyond an hour, I’ll let it run while I’m away tomorrow. I updated my BIOS to a newer version, but not the latest (from 3.30 to 3.40). Does this have any impact? And finally, how do I disable XMP on my motherboard? I only have the choice between “auto” or creating a profile, which I’m not sure how to set up either.