[SOLVED] Plagued by seemingly random BSOD

May 23, 2019
12
0
10
For awhile now, I've been getting what seems like random crashes with different error messages. Most common messages are "IRQL_NOT_GREATER_OR_EQUAL ", "INTERRUPT_EXCEPTION_NOT_HANDLED" , and recently "MEMORY_CORRUPTION". They can happen at anytime, but seem to be more frequent when I am playing a game. I've been replacing parts after these crashes have started happening. I replaced my Motherboard, Power Supply, and RAM. I have reinstalled all of my network drivers, my graphics drivers, and chipset drivers. I don't know if there is some driver that is causing this, or if it is hardware based. I have done a clean install of windows earlier at one point after the crashes started, but it is still happening (that's what led me to believe it is a hardware issue). The following is an analysis on the latest crash that happened while playing a game.

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the bugcheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the bugcheck
Arg4: ffffc780d18ecc80, Reserved

Debugging Details:
------------------

Page 120eb9 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 10

Key : Analysis.Elapsed.Sec
Value: 11

Key : Analysis.Memory.CommitPeak.Mb
Value: 64


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.20

BIOS_DATE: 01/12/2016

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: 970A-G/3.1

BASEBOARD_VERSION:

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: ffffc780d18ecc80

TRAP_FRAME: 0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD: 0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

CPU_COUNT: 8

CPU_MHZ: fa0

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x139

PROCESS_NAME: Risk of Rain 2.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: BIGBOSS

ANALYSIS_SESSION_TIME: 05-22-2019 22:01:20.0173

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

BAD_STACK_POINTER: ffffc780d18ec498

LAST_CONTROL_TRANSFER: from fffff8073286167b to fffff80732858ef0

STACK_TEXT:
ffffc780d18ec498 fffff8073286167b : 0000000000000139 0000000000000000 0000000000000000 0000000000000000 : nt!KeBugCheckEx
ffffc780d18ec4a0 fffff807328619f2 : fffff80732c009e0 ffff82ec8565c000 0000012000001000 000000000010001f : nt!guard_icall_handler+0x1b
ffffc780d18ec4d0 fffff807327ba3a0 : ffffc780d18ecb20 0000000000000000 ffffc780d18eca40 fffff80732a8e240 : nt!RtlpExecuteHandlerForException+0x12
ffffc780d18ec500 fffff807326c7bb4 : ffffc780d18ed438 ffffc780d18ed180 ffffc780d18ed438 ffffaf8e7b0a2080 : nt!RtlDispatchException+0x430
ffffc780d18ecc50 fffff8073286a742 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchException+0x144
ffffc780d18ed300 fffff80732864f8e : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0xc2
ffffc780d18ed4e0 fffff8073285fe72 : ffff8300d6cd7180 ffffc780d18ed870 ffffaf8e7985b080 ffffaf8e7b0a2080 : nt!KiInvalidOpcodeFault+0x30e
ffffc780d18ed670 fffff8073285fcd8 : ffff8300d6cd7180 0000000000000000 ffffc78000000000 0000000000000000 : nt!SwapContext+0xf2
ffffc780d18ed6b0 fffff8073285f23c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxDispatchInterrupt+0x138
ffffc780d18ed7f0 ffff82ec8565c44a : ffffa9b559609948 ffff72fd67e00000 ffffaf8e7b5dc140 ffff82ec854140af : nt!KiDpcInterrupt+0x2dc
ffffc780d18ed980 ffff82ec854140af : ffffaf8e7b5dc140 0000000000da7a64 0000000000000001 0000000000000000 : 0xffff82ec8565c44a
ffffc780
d18ed9a0 ffff82ec85cbbf66 : ffffaf8e7b0a2080 0000000000000001 000000000003026a fffff8073260962a : win32kbase!EnterCrit+0xef
ffffc780
d18eda80 fffff8073286a088 : ffffaf8e7b0a2080 ffffaf8e7b0a2080 ffffc780d18edb80 00000000032f7e80 : win32kfull!NtUserPostMessage+0x36
ffffc780
d18edb00 00007ff857e6f644 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
00000000
00b1e048 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff857e6f644


THREAD_SHA1_HASH_MOD_FUNC: cdda841c1940a2ab4dd3a7352eedec446108a4ac

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: fa921223c58cc42e009f9f8756776ad3a9672ff8

THREAD_SHA1_HASH_MOD: bef471c2464f19dee4237f109846ca30a75d0408

FOLLOWUP_IP:
win32kbase!EnterCrit+ef
ffff82ec`854140af 488bd8 mov rbx,rax

FAULT_INSTR_CODE: 48d88b48

SYMBOL_STACK_INDEX: b

SYMBOL_NAME: win32kbase!EnterCrit+ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: ef

FAILURE_BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_STACKPTR_ERROR_win32kbase!EnterCrit

BUCKET_ID: 0x139_0_LEGACY_GS_VIOLATION_STACKPTR_ERROR_win32kbase!EnterCrit

PRIMARY_PROBLEM_CLASS: 0x139_0_LEGACY_GS_VIOLATION_STACKPTR_ERROR_win32kbase!EnterCrit

TARGET_TIME: 2019-05-23T03:34:39.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2021-07-31 08:45:35

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 2baf

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_0_legacy_gs_violation_stackptr_error_win32kbase!entercrit

FAILURE_ID_HASH: {28f0ff2d-e506-ff27-02fd-346c496db1c0}

Followup: MachineOwner
---------
 

Colif

Titan
Moderator
3 things:
1. Can you give us specs of PC? I can tell its an AMD with an asrock motherboard

2.Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read

3. Can you download driverview, run it and in its options, set it to not show Microsoft drivers. upload screenshot to an image sharing website and show link here. Its likely an old driver, just need to see which one.

error caused win32kbase.sys to crash, it is part of the Windows kernel. It is not cause
 
May 23, 2019
12
0
10
Processor: AMD FX 8350
Memory: 16GB
Graphics: Radeon RX 480
PSU: 850W
MotherBoard: ASRock 970A-G/3.1

I setup minidumps, so on my next crash I will upload that to my dropbox. I will also try driverview. I have run driver easy in the past, but I don't know if they are comparable.
 
Last edited:
May 23, 2019
12
0
10
3 things:
1. Can you give us specs of PC? I can tell its an AMD with an asrock motherboard

2.Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read

3. Can you download driverview, run it and in its options, set it to not show Microsoft drivers. upload screenshot to an image sharing website and show link here. Its likely an old driver, just need to see which one.

error caused win32kbase.sys to crash, it is part of the Windows kernel. It is not cause
View: https://imgur.com/Fzl2sQp


There's a screenshot of my non-microsoft drivers.
 

Colif

Titan
Moderator
driver easy is a software updater, driver view (as you can see) just shows what drivers are installed. You shouldn't need driver easy as the Asrock App Store would find the newest drivers for your board, Your sound and LAN drivers are newer than what Asrock have on their site.

Might want to remove App Charger off, its from 2011
AMD Overdrive is old too (2015) - if its part of Asrock Extreme tuning utility, there is a newer version on website
your razer driver is pretty old as well (2016)

Atheros drivers can also cause BSOD but you seem to have the newest. (those are lan drivers)

there is only 1 bios so thats not an option

https://www.asrock.com/mb/AMD/970A-G3.1/#Download
 
May 23, 2019
12
0
10
3 things:
1. Can you give us specs of PC? I can tell its an AMD with an asrock motherboard

2.Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read

3. Can you download driverview, run it and in its options, set it to not show Microsoft drivers. upload screenshot to an image sharing website and show link here. Its likely an old driver, just need to see which one.

error caused win32kbase.sys to crash, it is part of the Windows kernel. It is not cause
https://www.dropbox.com/s/tc1fozyok3i85fw/052419-10343-01.dmp?dl=0

There's a link to the minidump from my latest crash.
 

gardenman

Admirable
Herald
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/RQot.html

File information:052419-10343-01.dmp (May 24 2019 - 17:47:41)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: Warhammer2.exe)
Uptime:1 Day(s), 16 Hour(s), 48 Min(s), and 49 Sec(s)

Comment: The overclocking driver "AxtuDrv.sys" was found on your system. (Intel Extreme Tuning Utility)

Comment: The overclocking driver "AODDriver2.sys" was found on your system. (AMD Overdrive)

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.
 

Colif

Titan
Moderator
On top of the drivers that i mentioned already (should remove if you don't use them), I would think about removing
May 19 2014 AsrRamDisk.sys ASRock RAM Disk driver (ASRock Inc.)

Do you use WIFI or Ethernet?
You can get newer WIFI drivers from: https://support.killernetworking.com/download/killer-drivers-installation-64bit/

Hey, Gardenman, this seems to be wrong -
Comment: The overclocking driver "AxtuDrv.sys" was found on your system. (Intel Extreme Tuning Utility)
as your own file shows it as
Dec 25 2015 AxtuDrv.sys ASROCK RW-Everything Read & Write driver

so something's gone wrong somewhere :)
unlikely to be intel on an AMD system :)
 

Colif

Titan
Moderator
I wouldn't say I am sure, I was just going from the description in the file. Seems a conflict there

I can find different sites showing both results. Its unclear which is right. Its possible the driver is part of both?

we could ask op to find file on system and show properties. or they could just remove Asrock extreme tuning and see if it disappears.
 
May 23, 2019
12
0
10
I wouldn't say I am sure, I was just going from the description in the file. Seems a conflict there

I can find different sites showing both results. Its unclear which is right. Its possible the driver is part of both?

we could ask op to find file on system and show properties. or they could just remove Asrock extreme tuning and see if it disappears.
I've removed AsrRamDisk.sys, reinstalled all my Razer device drivers, and reinstalled all the Asrock drivers. I'll keep an eye out for another crash, though at this point I'm kinda suspecting it's a hardware issue, maybe with the CPU?
 

gardenman

Admirable
Herald
I ran the dump file through the debugger and got the following information: https://pste.eu/p/Ldgp.html

File information:052619-10359-01.dmp (May 26 2019 - 15:02:00)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: RazerCortex.ex)
Uptime:0 Day(s), 0 Hour(s), 23 Min(s), and 53 Sec(s)

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.
 

Satan-IR

Honorable
I ran the dumps and the two processes names are warhammer2.exe and RazerCortex.exe, as said by gardenman.

I'd also suggest the OP check RAM modules with memtest, one stick at a time, 4 passes at least.
 
Last edited:
May 23, 2019
12
0
10
I ran the dumps and the two processes names are warhammer2.exe and RazerCortex.exe, as said by gardenman.

I'd also suggest the OP check RAM modules with memtest, one stick at a time, 4 passes at least.
I've done memtest already, that was the first thing I thought was wrong. Even though I had no errors, I went ahead and upgraded my RAM anyways but the problem still exists. The processes listed I don't think are causes of the crash as they just list whatever I was using at the time of the crash.
 
May 23, 2019
12
0
10
to check your suspicion it is CPU, I would run this: https://www.mersenne.org/download/
So I did the RAM test and the CPU test separately to see if either were the problem. I let the RAM test run for quite awhile and no problems were ever detected in any of the workers. However, when I ran the Small test (which tests the CPU) every worker said there was a hardware failure. So to me that sounds like my CPU is bad?
 

Satan-IR

Honorable
I've done memtest already, that was the first thing I thought was wrong. Even though I had no errors, I went ahead and upgraded my RAM anyways but the problem still exists. The processes listed I don't think are causes of the crash as they just list whatever I was using at the time of the crash.

Sometimes the processes named are the culprits.

Sometimes it's the drivers they're engaging and there's some kind of conflict with other process that might use that driver at the same time or drivers attempt to read/write to addresses in memory that they're not supposed to etc.

So far so good, you have eliminated faulty RAM as a probable cause.
 

Colif

Titan
Moderator
I did see a mention of voltages being a possible way to fix fft errors.BIOS updates are suggested fixes as well except you on latest now.

Small FFTs
The Small FFTs description in the dialog box says maximum FPU stress, data fits in L2 Cache and RAM not tested. This is what the Small FFTs configuration is. If you select this configuration, the Prime95 will select a FFT size that is suitable for your CPY L2 cache. Since this FFT is small and fits in your CPU cache, this will result in almost no or very few main memory accesses.
https://appuals.com/how-to-run-a-cpu-stress-test-using-prime95/

Small FFTs maximizes stress on the FPU, caches, power supply, cooling system. RAM is little used.
https://www.mersenneforum.org/showthread.php?t=19528

I am hesitant to blame CPU as it isn't a common cause, but I would be stupid to ignore it as well. Shame AMD don't have a CPU testing tool I could use to get a 2nd opinion, unlike Intel.

what is in the stress.txt file? it should be in the prime95 folder or maybe documents.

what brand PSU is it?

What memory speed are you running at?
 
Last edited:
May 23, 2019
12
0
10
So after toying around with my cpu voltage, I seem to have gotten a setting that is stable for me. I upped my CPU voltage to 1.4125V and me CPU NB Voltage to 1.3875. Since doing this last night, I did not experience any BSOD since, so it does seem to be stable (at least for the moment). I will check back in after a couple days or if I still get another BSOD.
 

ASK THE COMMUNITY

TRENDING THREADS