BSOD while browsing/playing (Windows 10)

[DevM]

So I have been having some weird issues lately, google chrome randomly crashes and a lot of BSOD, today I had two for example, one of them I was just browsing google chrome while listening to music and the other was while playing League of legends. Here is the files that are required from what I read and I also attached the two files from the BSOD (sorry for those 2 stupid names). Additionally I should add that this is nothing "new" since I have had my PC go to the store to fix before because of BSOD that were caused by the RAMs , it was fixed when it came back and now im having these BSOD's again so maybe its related but Im not sure ( just thought I would add this here because it might be important).

Any help is appreciated, its really getting on my nerves :/.

 

[lifetec]

Only 1 dumpfile: from 22-12-2015

BugCheck D1, {48, 2, 0, fffff8019e31cdb8}
*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8019e31cdb8, address which referenced memory

cmudaxp.sys Driver Description: ASUS Xonar DG Audio Interface driver
Support Center | ASUS Global
cmudaxp Tue Jun 02 11:11:20 2015
As you can see this is the driver for your Asus Xonar Devices.
Update to the latest windows 10 driver.
If this already the latest windows 10 compatible driver, the driver may be corrupted. Remove and reinstall the driver.
If there are no windows 10 driver, the driver may be not compatible with windows 10.

 

[DevM]

Well I formatted the PC and did what you said, that BSOD in specific didnt happen but another happened.
Here is the dump file:

 

[lifetec]

This dumpfile was

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8015f086384, 1, 4196bf3c}
Probably caused by : win32kbase.sys ( win32kbase!CTokenManager::ProcessTokens+11e )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8015f086384, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 000000004196bf3c, Parameter 1 of the exception

Did you use a Tokenmanager to backup your windows registration key.

The win32kbase.sys is a windows systemdriver and these are normally not the problem,
Did you updated all your Windows Updates.

 

[DevM]

Yea I did, no more updates to download. I didnt use a token as far as I know. Although I did format with the Windows 10 option so maybe it has to do with that.

 

[DevM]

Yet another crash, the errors are all over it seems..

 

[lifetec]

The dump is a

Use !analyze -v to get detailed debugging information.
BugCheck BE, {fffffa80676d2ae8, 8000000001000121, ffffd000244297d0, a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4418b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffffa80676d2ae8, Virtual address for the attempted write.
Arg2: 8000000001000121, PTE contents.
Arg3: ffffd000244297d0, (reserved)
Arg4: 000000000000000a, (reserved)
Debugging Details:
------------------

CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  System
CURRENT_IRQL:  2

Usual causes: Device driver, Memory

As i can not find any specific clues from this dump.
And the BSOD are all so different.


Please start with diagnosing the system RAM first. You can use the free tool "Memtest86+"to stress test the RAM.

How to run "Memtest" - RAM - Test with Memtest86+ - Windows 7Help Forums

Make sure you are using the latest version 5.01 - Memtest86+- Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 7-10 passes and post a screenshot with next reply. 7 passes is the recommended bare minimum but more passes will give better result.

If Memtest gives no errors, than you can run Driver Verifier

"Verifier"is a Microsoft's own tool to stress test third party drivers and find the buggyone. If it detects a violation, a blue screen will be created immediately andthe dump will give us the name of offending driver straight forward. After enabling"Verifier" , system will be a bit slow and laggy dur to thebackground verification process. After you got two or more blue screens, pleaseupload the new crash dumps and we will know whether the issue is caused bythird party drivers or low level hardware (a verifier enabled dump which blamesWindows system files is a clear confirmation of hardware problem).

"Verfier"should be only used to monitor third party drivers. Selecting Microsoft systemdrivers is totally unnecessary and doing so may make the system non bootable.First read instructions from the below link and set "Windows" to write"Small Memory dumps".

Set MiniDump

Then enable "verfier" and select all non-Microsoft drivers.

Run Driver Verifier according to these instructions to see if we can force it to name a driver: Driver Verifier Settings