BSOD attempted to write to readonly memory

Toggle sidebar Toggle sidebar
H

Hender

Commendable
Aug 10, 2017
15
0
1,510
hello im not English will try by best to explain

1 week ago bought new pc parts since first day been having BSOD attempted to write to readonly memory.
pc its up to date, some times takes 1h others 10h to crash always same error.
already tried to reformat install only chipset Drivers still gave me error
already run memtest86 both sticks passed 2h test 4/4 "40tests"

pc details:
Windows 10
msi z270 pro carbon
msi gtx 1080 gaming X
i7 7700k
Samsung M.2 NVMe 960 evo 250GB
Gskill F4-3000C15D-16GVKB

im new to this crash dump things if someone can gimme some help

Debugging Details:

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xBE

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2


MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

BUCKET_ID: MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_large

FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
 
win 10 debugger reports all errors as memory corruption now ever since win 10 started compressing memory. One day they might fix it

Can you follow option one 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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and

someone with right software to read them will decode them for us so we can help you fix it :)

its likely to be an old driver, we just have to find it :)
 
waiting for another BSOD using pc normally even made some stress tests to warm up the pc! already set Small Memory Dump! the strange thing is: takes time for BSOD to start but when it starts doesn't stop infinite loop: BSOD restart Login into windows BSOD again "Repeat LOOP"
When BSOD happens i will decode with WinDBG to see"/post" if the info its the same
 
Hi Hender, I ran the dump files through the debugger and some special software that I've created in order to clean up the debugger results and make them more presentable. I also got a list of the drivers from the dump file which Colif can help you with. Here are the results: https://pastebin.com/5qD7UKLr

File: 081117-5531-01.dmp (Fri Aug 11 15:56:28 2017)
BugCheck: [ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)] {ffffe6fffcffff28, 8a00000003b00121, ffff8380ddc45dc0, a}
Probably caused by: memory_corruption (Process: svchost.exe)

File: 081117-4750-01.dmp (Fri Aug 11 15:58:40 2017)
BugCheck: [ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)] {fffffb7ff9ffff28, 8a00000003900121, ffffc2007c038dc0, a}
Probably caused by: memory_corruption (Process: svchost.exe)

I can't help you with this. Wait for Colif or someone else to reply. Good luck.
 


will wait since i dont understand 😀 ths
 
once i got past all the kapersky files...

cfosspeed6.sys (Dated Fri Nov 11 2016) - Internet accelerator?
I2cHkBurn.sys (Dated Mon Feb 17 2014) - FINTEK Corp. FitGpBus Device Driver (suffers de ja vu), this is part of a MSI program, maybe to do with CPU temps
(download and run live update 6, it will confirm all the drivers on PC are up to date)
 


everything its uptodate not a single driver appears in live update! error still appears! seems to be a driver that comes with win10
last night booted the pc in safe mode for 10h and error doesn't appear

cfosspeed6.sys (Dated Fri Nov 11 2016) part of MSI gaming lan manager to let me speedtest

(created 2 partitions and installed windows 7"no support for 7gen" and its working just fine! i downloaded the windows 10 from Microsoft, and installed in other partition without Ethernet! error still pops. windows 10 must have some faulty drivers in installation ) or i have damaged hardware
 


can y decoded this two?
https://mega.nz/#!A7R2ESRA!kh5Mo78Bp35a5ZTBd_6THX2RfGipcXolL_5x1mzmxyM
Fresh install nothing installed
 
I ran the dump files through the debugger and got the following information: https://pastebin.com/tvjpCVZu

File: 081317-2140-01.dmp (Sat Aug 12 20:12:56 2017)
BugCheck: [ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)] {ffffbeffef4fff28, 8a00000003400121, ffffe6011f608dc0, a}
Probably caused by: memory_corruption (Process: svchost.exe)

File: 081317-2109-01.dmp (Sat Aug 12 20:11:50 2017)
BugCheck: [ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)] {ffff967ff0cfff28, 8a00000003600121, ffffc1803ad74dc0, a}
Probably caused by: memory_corruption (Process: svchost.exe)

I can't help you with this. Wait for someone else to reply. Good luck.
 
The only driver mentioned there is the Intel NIC drivers

e1i63x64.sys (Dated Fri Mar 4 2016) - Intel® Ethernet driver

and looking at the Intel web site for that controller, the drivers they have are a lower version that what are showing on the MSI web site (MSI shows 22.4.16.1)

what version does it show as installed? I wonder if its a driver that comes with windows as I seen this before with intel drivers recently. That sys file has been around since 2015 in various forms.
 
that last 2 mini dumps its only drivers of the windows install" made installation without Ethernet and didn't install anything".
my intel ethernet connection (2)I219-V in device manager shows as version 12.15.22.6
even removed my GPU to check if was GPU problem still error
 


updated all drivers from msi! atm running memtest64 to warmup and check both sticks at same time 10 loops and no errors!
is possible processor dmged from delid? its to strange 3h+ to get BSOD after quickly power off / power up pc!
if restart without power off BSOD wont stop
screenshot memtest64 and 100% processor usage http://
 


other two dumps! https://mega.nz/#!U7QwnRgI!1KmTRJYDpGBrW3ZZLvlbwg1E2Jji5a5i-mmpriNPniw
i was running memtest64 and got a different error
 
I ran the 2 new dump files through the debugger and got the following information: https://pastebin.com/0egSNNgm

File: 081317-2359-01.dmp (Sun Aug 13 13:20:32 2017)
BugCheck: [DRIVER_OVERRAN_STACK_BUFFER (F7)] {7600711f83c0, bdafbde7e409, ffff425042181bf6, 0}
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)

File: 081317-2125-01.dmp (Sun Aug 13 13:22:35 2017)
BugCheck: [ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)] {ffffafffffcfff28, 8a00000003a00121, ffff9a00983bcdc0, a}
Probably caused by: memory_corruption (Process: svchost.exe)

I can't help you with this. Wait for someone else to reply. Good luck.
 
did you de lid the CPU yourself or just curious?

When you run it, you should run memtest on 1 stick at a time, if you did get an error with 2 you still wouldn't know which stick was the cause and would have to run it one stick at a time anyway.

I would suggest running Intel Processor Diagnostic Tool and see what it finds

The only drivers showing are the Intel Management Engine Interface, the Intel GPU Audio driver, the Intel GPU driver and the Intel NIC driver.

Only other file is realtek HD Audio.
 


yup delided my self 😀
sweet and stable temps at 100% load
i already run memtest86 in both rams 1 at time! ATM runing in both at same time! 2/4 pass without errors will let it run till 4/4(40tests) -5/4 to make sure it works great!
downloaded all the drivers from MSI ! and few minutes ago they replied to me :
its hard to determine what causes the issue from the error message,and about the drivers at MSI Website,we have tested these drivers before we released it,in theory,they will not cause the BSOD and we consulted the relevant department,we did not receive the similar issue from other users.

can the problem be from PSU?
XFX 750W Black Edition Full Modular PSU Gold 80+
removed M.2 and plugged in HDD and still BSOD after 2/3 hours
the time it takes for BSOD its strange! if restart keeps BSODing
if power off and on"fast to make sure its not temp" no more BSOD for 2/3h
will run that Intel Processor Diagnostic Tool when memtest86 ends
 
went to the shop where i bought the pc parts and at first they changed motherboard! i went home installed motherboard 2 hours later BSOD went to shop again and came home with new processor! 1 day two new parts mobo and processor! still no BSOD only kernel security check failure during windows install"kinda normal i guess"
 
What it shouldn't be caused by:
New Motherboard (possible but unlikely)
New CPU (see same as mobo)
Ram tested with memtest and no errors
Not hdd as tried hdd/nvme

Possible causes:
ISO might be corrupt, did you make a 2nd one?
PSU as you guessed already (only as everything else is new) - hard to test PSU as like motherboard, they are often identified through a process of elimination like above. I don't like suggesting PSU as I am often wrong :)
Is ram on motherboard supported list? Is it in xmp mode?
I assume CPU isn't overclocked?

unlikely causes:
GPU
Case
 


downloaded another windows cleaned flashdrive(with diskpart) and worked like a charm! cpu at 45, ram at 3000!
went to both msi and gskill to check my ram, its supported
 
ok today got exactly the same error only thing left to change its memory ram/PSU! tomorrow will go to the chop again! with all hardware lets see what they say/change memory! i installed different version of windows!
strange thing took exactly 2H to get the error (same time as other hardware last few times"motherboard and processor") so the problem can only be ram after being warm gets error shutdown reset"reading starts from beginning(i guess)"
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom