Windows 10 Frequent Crashes and BSOD Due to Memory Corruption During Gaming - Help Needed!

matthew123 · Jun 1, 2017

please help me I don't know what else to do just tell me whats wrong with my computer it restarts for no reason and crashes when I'm play games!! help please!!!
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8036e99a42a, Address of the instruction which caused the bugcheck
Arg3: ffffe700f7c63a50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!RtlGetRvaListIteratorState+32
fffff803`6e99a42a 480fa30f bt qword ptr [rdi],rcx

CONTEXT: ffffe700f7c63a50 -- (.cxr 0xffffe700f7c63a50)
rax=ffffd707d1c7bfa0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=000000001fff1ab3 rdi=0000000000000000
rip=fffff8036e99a42a rsp=ffffe700f7c64458 rbp=ffffe700f7c64501
r8=0000000000000000 r9=0000000000000002 r10=ffffd707d1c7bf60
r11=0000000000000000 r12=0000000000000003 r13=0000000000000000
r14=000000000000f200 r15=0000000000001e40
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!RtlGetRvaListIteratorState+0x32:
fffff803`6e99a42a 480fa30f bt qword ptr [rdi],rcx ds:002b:00000000`00000000=0000000000000000
Resetting default scope

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x3B

PROCESS_NAME: ByteFence.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8036e99a3e2 to fffff8036e99a42a

STACK_TEXT:
ffffe700`f7c64458 fffff803`6e99a3e2 : ffffe700`f7c644f8 ffffe700`f7c644d0 ffffe700`f7c64488 00000000`00000018 : nt!RtlGetRvaListIteratorState+0x32
ffffe700`f7c64460 fffff803`6e99c0a6 : ffffd707`d1c7bf60 fffff803`6e8010c0 00000000`00000003 ffffc50f`c2400000 : nt!RtlEnumRvaListFirst+0x36
ffffe700`f7c64490 fffff803`6e99ae27 : ffffd707`d059e058 00000000`00000128 ffffd707`d059e010 00000000`00000079 : nt!MiUpdateCfgSystemWideBitmapWorker+0x156
ffffe700`f7c64560 fffff803`6e9a09cc : 00000000`00000023 ffffe700`f7c647d9 00000001`80000000 00000000`00000000 : nt!MiUpdateCfgSystemWideBitmap+0x83
ffffe700`f7c645a0 fffff803`6e99e2a9 : ffffe700`f7c64990 ffffe700`f7c64990 ffffe700`f7c647d9 ffffe700`f7c64990 : nt!MiRelocateImage+0x30c
ffffe700`f7c64700 fffff803`6e9046b9 : fffffffe`00000000 ffffe700`f7c64990 ffffe700`f7c64990 ffffc50f`c6a5a650 : nt!MiCreateNewSection+0x3ad
ffffe700`f7c64840 fffff803`6e903e32 : ffffe700`f7c64870 ffffd707`bff78b20 ffffc50f`c6a5a650 00000000`00f800d8 : nt!MiCreateImageOrDataSection+0x289
ffffe700`f7c64920 fffff803`6e9049b2 : 00000000`11000000 00000000`00000000 ffffd707`bfa687c0 fffff803`6e8f6309 : nt!MiCreateSection+0xd2
ffffe700`f7c64a60 fffff803`6e5fb213 : ffffc50f`c4bf3700 ffffb158`00000005 00000000`00000000 00000000`2007e6f8 : nt!NtCreateSection+0x1e2
ffffe700`f7c64b10 00007ffc`84635cf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`2007e6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffc`84635cf4

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

STACK_COMMAND: .cxr 0xffffe700f7c63a50 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption

kemical · Jun 2, 2017

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8036e99a42a, ffffe700f7c63a50, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

...

Neemobeer · Jun 1, 2017

Upload the dump file(s).

matthew123 · Jun 1, 2017

here it is

matthew123 · Jun 1, 2017

Neemobeer said:
Upload the dump file(s).

matthew123 · Jun 1, 2017

Neemobeer said:
Upload the dump file(s).

kemical · Jun 2, 2017

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8036e99a42a, ffffe700f7c63a50, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

Hi,
you have a number of different dump files which relate to memory exceptions although I doubt this is down to your hardware. One of your dump files was a bugcheck 50.
Bugcheck 50 can be caused by a number of things including AV suites. I also notice that the dump file posted above was running ByteFence.exe.

ByteFence.exe is usually bundled with other software and is a re-branded version of Reason Core security. Please remove to test it's not the cause of the blue screen.

Once it's removed try running a scan of Malwarebytes This app also works great alongside Defender and many of us here use that config.

These scans should clear any corruption within the system:

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

The other thing i noticed is your bios:
BiosVendor = American Megatrends Inc.
BiosVersion = P1.60
BiosReleaseDate = 02/10/2017
BaseBoardManufacturer = ASRock
BaseBoardProduct = B250M-HDV
ASRock - BIOS Upgrade Instruction Guide

I checked your support page at the ASRock website and current bios version stands at 2.20 with updates for memory compatibility.

If your unsure on how to flash the bios then it's probably best left until you can either get a friend or shop to do it for you although I have included the instructions above on how to install the windows version.

If the bsod continues then you'll need to test your RAM. Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool

Please post any new dump files

matthew123 · Jun 2, 2017

kemical said:
Code:

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8036e99a42a, ffffe700f7c63a50, 0} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption ---------

Hi,
you have a number of different dump files which relate to memory exceptions although I doubt this is down to your hardware. One of your dump files was a bugcheck 50.
Bugcheck 50 can be caused by a number of things including AV suites. I also notice that the dump file posted above was running ByteFence.exe.

ByteFence.exe is usually bundled with other software and is a re-branded version of Reason Core security. Please remove to test it's not the cause of the blue screen.

Once it's removed try running a scan of Malwarebytes This app also works great alongside Defender and many of us here use that config.

These scans should clear any corruption within the system:

File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results

In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).

If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.

The other thing i noticed is your bios:
BiosVendor = American Megatrends Inc.
BiosVersion = P1.60
BiosReleaseDate = 02/10/2017
BaseBoardManufacturer = ASRock
BaseBoardProduct = B250M-HDV
ASRock - BIOS Upgrade Instruction Guide

I checked your support page at the ASRock website and current bios version stands at 2.20 with updates for memory compatibility.

If your unsure on how to flash the bios then it's probably best left until you can either get a friend or shop to do it for you although I have included the instructions above on how to install the windows version.

If the bsod continues then you'll need to test your RAM. Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool

Please post any new dump files

Thanks I'll be sure to try this and get back to you as soon as possible.

kemical · Jun 2, 2017

Hope all goes well Matthew!

kemical · Jun 7, 2017

Any news Matthew?

Windows 10 Frequent Crashes and BSOD Due to Memory Corruption During Gaming - Help Needed!

matthew123

New Member

kemical

Neemobeer

Cloud Security Engineer

matthew123

New Member

Attachments

matthew123

New Member

matthew123

New Member

Attachments

kemical

Essential Member

matthew123

New Member

kemical

Essential Member

kemical

Essential Member

Similar threads