bsod Started getting memory-related BSOD's while playing

[tmunited99]

I need your guys' thoughts on this. So I'm playing GTA story mode right, so I play for a long time. GTA is a demanding game, graphically, and I started getting BSOD's related to memory. I initially thought my RAM was breaking down, but I think it's my GPU, actually...

 

First BSOD was MEMORY_MANAGEMENT, the second one was ATTEMPTED_WRITE_TO_READONLY_MEMORY.

Now, why do I think it's the GPU?

 

1. When playing videos on YT, I started to one day just get seemingly randomly timed graphical glitches, where one half of the screen went green, and the other pink and stuff, and it'd just last for a second or so

 

2. Whenever I boot back from the GTA BSOD, my GPU fans go nuts for a sec or two, which if I kill csrss.exe, or use any other method to cause a BSOD, doesn't happen

 

3. Windows Memory Diag said there's nothing wrong

 

4. It only happens when I play GTA, a graphically demanding game

 

 

My GPU, an RX470, has been used for a year as a crypto-currency mining device before I got it, and benchmarks say it performs below the expected average my GPU model should. I don't have it OC'd. Is the GPU the problem?

[Radium_Angel]

11 minutes ago, tmunited99 said:

randomly timed graphical glitches, where one half of the screen went green

My money is on bad GPU.

11 minutes ago, tmunited99 said:

3. Windows Memory Diag said there's nothing wrong

Useless program, use MemTest86 if you want to be certain your RAM is good.

[tmunited99]

4 minutes ago, Radium_Angel said:

My money is on bad GPU.

Useless program, use MemTest86 if you want to be certain your RAM is good.

The GPU glitches also started for no reason overnight.

[Radium_Angel]

1 minute ago, tmunited99 said:

The GPU glitches also started for no reason overnight.

Yup, GPU cards going bad will do that, one day they are fine, next day, poof, bad.

Start with the MemTest86, just to ensure it's not badly corrupted RAM.

 

If you have the BSoD crash dumps, I can de-construct them and see what's going on as well.

[tmunited99]

1 minute ago, Radium_Angel said:

Yup, GPU cards going bad will do that, one day they are fine, next day, poof, bad.

Start with the MemTest86, just to ensure it's not badly corrupted RAM.

 

If you have the BSoD crash dumps, I can de-construct them and see what's going on as well.

Where are BSOD crash logs dumped?

[Radium_Angel]

1 minute ago, tmunited99 said:

Where are BSOD crash logs dumped?

Typically, here: c:\windows\minidump

[tmunited99]

3 minutes ago, Radium_Angel said:

Typically, here: c:\windows\minidump

Here

010521-35031-01.dmp

[Radium_Angel]

1 minute ago, tmunited99 said:

Here

010521-35031-01.dmp 963.22 kB · 0 downloads

Ok, give me a few to look it over.

[tmunited99]

9 minutes ago, Radium_Angel said:

Yup, GPU cards going bad will do that, one day they are fine, next day, poof, bad.

Start with the MemTest86, just to ensure it's not badly corrupted RAM.

 

If you have the BSoD crash dumps, I can de-construct them and see what's going on as well.

Anything other than MemTest86? I don't want to format my whole pen drive.

[Radium_Angel]

Just now, tmunited99 said:

Anything other than MemTest86? I don't want to format my whole pen drive.

Not that I know of, that's the gold standard for RAM testing

[DailyProcrastinator]

4 minutes ago, tmunited99 said:

Anything other than MemTest86? I don't want to format my whole pen drive.

Running MemTest86 is step 1. This will rule out whether or not your memory is the issue. 

[Radium_Angel]

7 minutes ago, tmunited99 said:

Here

010521-35031-01.dmp 963.22 kB · 1 download

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: ffffec0018824208, Virtual address for the attempted write.
Arg2: 8a000000d8900021, PTE contents.
Arg3: ffffcf8f6f2ead80, (reserved)
Arg4: 000000000000000a, (reserved)
 

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-HDJ0CJJ

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 7

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

    Key  : Analysis.System
    Value: CreateObject

BUGCHECK_CODE:  be

BUGCHECK_P1: ffffec0018824208

BUGCHECK_P2: 8a000000d8900021

BUGCHECK_P3: ffffcf8f6f2ead80

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  GTA5.exe
 

SYMBOL_NAME:  nt!MiRaisedIrqlFault+16caac

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  16caac

FAILURE_BUCKET_ID:  0xBE_nt!MiRaisedIrqlFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}

Followup:     MachineOwner
_________________________________________________________________________

 

End result, GTA5 crashed (duh, we know that right?) because it attempted to write to RAM that was non-writeable. Couple that with the graphical glitches, I'm going to make the assumption it was your video card it was trying to write to, while the RAM on the card was in use.

Barring the actual mobo RAM being bad, I'm gonna go with new video card time...

 

 

 

 

[tmunited99]

1 minute ago, Radium_Angel said:

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: ffffec0018824208, Virtual address for the attempted write.
Arg2: 8a000000d8900021, PTE contents.
Arg3: ffffcf8f6f2ead80, (reserved)
Arg4: 000000000000000a, (reserved)
 

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-HDJ0CJJ

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 7

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

    Key  : Analysis.System
    Value: CreateObject

BUGCHECK_CODE:  be

BUGCHECK_P1: ffffec0018824208

BUGCHECK_P2: 8a000000d8900021

BUGCHECK_P3: ffffcf8f6f2ead80

BUGCHECK_P4: a

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  GTA5.exe
 

SYMBOL_NAME:  nt!MiRaisedIrqlFault+16caac

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.685

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  16caac

FAILURE_BUCKET_ID:  0xBE_nt!MiRaisedIrqlFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1c5b4d11-09e0-def3-d2d0-70a11d69b92d}

Followup:     MachineOwner
_________________________________________________________________________

 

End result, GTA5 crashed (duh, we know that right?) because it attempted to write to RAM that was non-writeable. Couple that with the graphical glitches, I'm going to make the assumption it was your video card it was trying to write to, while the RAM on the card was in use.

Barring the actual mobo RAM being bad, I'm gonna go with new video card time...

 

 

 

 

Dang... I just got this GPU about quite literally one year ago

[Radium_Angel]

1 minute ago, tmunited99 said:

Dang... I just got this GPU about quite literally one year ago

Right, but it was a mining GPU, who knows what kind of life it had mining?

[tmunited99]

Just now, Radium_Angel said:

Right, but it was a mining GPU, who knows what kind of life it had mining?

True that

[tmunited99]

4 hours ago, Radium_Angel said:

Right, but it was a mining GPU, who knows what kind of life it had mining?

Oh yeah, and for reference, this is what it does to YT videos for about a second everytime I fullscreen or scroll down and back up in fullscreen:

[Radium_Angel]

11 hours ago, tmunited99 said:

YT videos for about a second everytime I fullscreen or scroll down and back up in fullscreen:

The problem is you are watching a Tesla YT video on non-tesla video card! Of course it's going to mess up 

[tmunited99]

On 1/6/2021 at 1:28 PM, Radium_Angel said:

The problem is you are watching a Tesla YT video on non-tesla video card! Of course it's going to mess up 

New discoveries! Reinstalling my GPU driver, it fixed the bluescreens, and I found out the graphical glitches while watching videos only happens with Google Chrome, when watching at 1080p, my native resolution. Does this change anything?

[Radium_Angel]

1 hour ago, tmunited99 said:

New discoveries! Reinstalling my GPU driver, it fixed the bluescreens, and I found out the graphical glitches while watching videos only happens with Google Chrome, when watching at 1080p, my native resolution. Does this change anything?

You could try a LiveUSB of a Linux Mint (very windows like) environment, and see if the issues persist under that. If they do, it's a hardware thing, if they don't, then it's a windows thing