Windows 10 May 2020 Update is causing issues with Intel Optane

There are many issues with 2004. I experienced BSODs on my X570 build doing nothing but sitting on the desktop wallpaper. Yes, I did a clean install, even then it gave me BSODs.

Reference (Dutch): https://answers.microsoft.com/nl-nl...-c7f7-4c0d-b93e-019bcad45cf2?tm=1591699295392
Reference 2: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004

 

people mistake "my pc doesn't work with XX os" with "xx os doesn't work with my pc""

Yours is the former.

Maybe RMA the cpu or reconfigure your system so its stable (by changing hardware such as ram) since its known to have bsod and idle reset issues instead of blaming the OS.

See below for offending drivers

Both your crashes are centered around standard windows storage drivers, which i can tell you now - are unlikely to be a bug in the OS, your issue is either the cpu cache or memory controller, or the pcie controller.

That the older OS works is irrelevant.

PS: If you want actual help with this bsod, use sysnative or sysinternal forums, the microsoft answers site is staffed by script reading know-nothings.

This crash is caused by Memory corruption through hardware malfunction or a faulty nvme or ahci driver or filter.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff8004b40001a, Virtual address for the attempted write.
Arg2: 0000000005c00121, PTE contents.
Arg3: ffffcb09b1532f80, (reserved)
Arg4: 000000000000000a, (reserved)

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

*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406

SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  X570 AORUS MASTER

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  -CF

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F11

BIOS_DATE:  12/06/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  X570 AORUS MASTER

BASEBOARD_VERSION:  Default string

DUMP_TYPE:  2

BUGCHECK_P1: fffff8004b40001a

BUGCHECK_P2: 5c00121

BUGCHECK_P3: ffffcb09b1532f80

BUGCHECK_P4: a

CPU_COUNT: 18

CPU_MHZ: ed8

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:

ANALYSIS_SESSION_TIME:  06-11-2020 03:19:27.0500

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME:  ffffcb09b1532f80 -- (.trap 0xffffcb09b1532f80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8004b400012 rbx=0000000000000000 rcx=ffffde09d51ec030
rdx=ffffde09e16497c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004b400004 rsp=ffffcb09b1533118 rbp=ffffcb09b15331a9
 r8=ffffde09e0c3cd00  r9=00000000ffffc000 r10=0000fffff8004b40
r11=ffffa7fc91800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
volsnap!VspWriteContextCompletionRoutine+0x4:
fffff800`4b400004 895808          mov     dword ptr [rax+8],ebx ds:fffff800`4b40001a=4c40ec83
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80049087340 to fffff80048fdda20

STACK_TEXT:
ffffcb09`b1532d88 fffff800`49087340 : 00000000`000000be fffff800`4b40001a 00000000`05c00121 ffffcb09`b1532f80 : nt!KeBugCheckEx
ffffcb09`b1532d90 fffff800`48e12dcf : 00000000`05c00121 00000000`00000003 ffffcb09`b1533000 00000000`00000000 : nt!MiRaisedIrqlFault+0x14baec
ffffcb09`b1532de0 fffff800`48febb1e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MmAccessFault+0x4ef
ffffcb09`b1532f80 fffff800`4b400004 : fffff800`48e3c7ce ffffde09`e16497c0 ffffde09`e16497c0 ffffde09`e16497c0 : nt!KiPageFault+0x35e
ffffcb09`b1533118 fffff800`48e3c7ce : ffffde09`e16497c0 ffffde09`e16497c0 ffffde09`e16497c0 ffffde09`cf5315c0 : volsnap!VspWriteContextCompletionRoutine+0x4
ffffcb09`b1533120 fffff800`48e3c697 : 00000000`00000000 ffffde09`e1649901 ffffde09`e16497c0 ffffde09`d5124080 : nt!IopfCompleteRequest+0x11e
ffffcb09`b1533210 fffff800`4b505843 : 00000078`e55b3985 00000000`00037401 ffffde09`d90f57b0 ffffde09`d90f57b0 : nt!IofCompleteRequest+0x17
ffffcb09`b1533240 fffff800`48e3c7ce : ffffde09`cf5ab000 00000000`00000000 00000000`00000000 00000000`00000000 : CLASSPNP!TransferPktComplete+0x5e3
ffffcb09`b1533450 fffff800`48e3c697 : 00000000`00000000 fffff800`58584001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x11e
ffffcb09`b1533540 fffff800`4a7c99e1 : ffffde09`cf5f31a0 ffffde09`e3a266c8 00000000`00000000 ffffde09`cf6348d0 : nt!IofCompleteRequest+0x17
ffffcb09`b1533570 fffff800`4a7c9354 : ffffde09`cf5ab020 ffffde09`cf5ab020 ffffcb09`b1533740 ffffde09`e3a26600 : storport!RaidCompleteRequestEx+0x91
ffffcb09`b1533640 fffff800`4a7d8d6b : 00000000`00000001 00000000`00000000 fffff780`00000320 ffffde09`cf5ab020 : storport!RaidUnitCompleteRequest+0xf64
ffffcb09`b15337c0 fffff800`48e3a69e : ffffcb09`b1533b20 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidpAdapterRedirectDpcRoutine+0x8b
ffffcb09`b1533860 fffff800`48e39984 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffcb09`b15339d0 fffff800`48fe158e : ffffffff`00000000 ffffb801`a8e80180 ffffb801`a8e8b640 ffffde09`e0ef2080 : nt!KiRetireDpcList+0x1f4
ffffcb09`b1533c60 00000000`00000000 : ffffcb09`b1534000 ffffcb09`b152e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


CHKIMG_EXTENSION: !chkimg -lo 50 -d !volsnap
    fffff8004b400002-fffff8004b400003  2 bytes - volsnap!VspWriteContextCompletionRoutine+2
   [ c4 48:34 12 ]
2 errors : !volsnap (fffff8004b400002-fffff8004b400003)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2020-06-09T09:07:36.000Z

OSBUILD:  19041

OSSERVICEPACK:  264

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  191206-1406

BUILDLAB_STR:  vb_release

BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME:  7750

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

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

Followup:     memory_corruption

amdpsp is from March

you have an out of date gigabyte kernel driver installed that is known to cause hell,
if you have rgb fusion installed or easytune, get rid of them, they are common factors in windows 10 update misbehaviors, not to mention security vulnerabilities.

Code:

fffff800`54840000 fffff800`5484b000   gdrv2      (deferred)        
    Image path: \??\C:\Windows\gdrv2.sys
    Image name: gdrv2.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 15 17:45:51 2019 (5CB436AF)
    CheckSum:         0000F92A
    ImageSize:        0000B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

https://www.reddit.com/r/gigabyte/comments/ddoh26/getting_blue_screens_from_the_gigabyte_software/

This means GVCIDrv64.sys is also present
https://answers.microsoft.com/en-us...hardware/2a214d33-8ad5-45aa-9d66-6743f8fec4db

ene.sys is also installed aka vanguard - piece of trash anticheat (you're really going for a trifecta on how to kill your pc here)

Out of date intel nic driver

Code:

fffff800`55900000 fffff800`5598e000   e1i65x64   (deferred)          
    Mapped memory image file: c:\symbols\win10_64\e1i65x64.sys\5B1EB8E28e000\e1i65x64.sys
    Image path: \SystemRoot\System32\drivers\e1i65x64.sys
    Image name: e1i65x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 12 04:01:06 2018 (5B1EB8E2)
    CheckSum:         0008A03D
    ImageSize:        0008E000
    File version:     12.17.10.8
    Product version:  10.0.10011.16384
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel(R) Gigabit Adapter
        InternalName:     e1i65x64.sys
        OriginalFilename: e1i65x64.sys
        ProductVersion:   12.17.10.8
        FileVersion:      12.17.10.8

out of date realtek gbe driver

Code:

fffff800`55990000 fffff800`55aa5000   rt640x64   (deferred)          
    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Dec  6 13:27:39 2018 (5C08891B)
    CheckSum:         001253EB
    ImageSize:        00115000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

older (but should still be ok) realtek audio driver

Code:

fffff800`55bb0000 fffff800`562c6000   RTKVHD64   (deferred)          
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Dec  3 22:09:10 2019 (5DE64256)
    CheckSum:         006E4F58
    ImageSize:        00716000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Intel Wifi driver

Code:

fffff800`562d0000 fffff800`56be0000   Netwtw08   (deferred)          
    Mapped memory image file: c:\symbols\win10_64\Netwtw08.sys\5CD9DF95910000\Netwtw08.sys
    Image path: \SystemRoot\System32\drivers\Netwtw08.sys
    Image name: Netwtw08.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue May 14 07:20:21 2019 (5CD9DF95)
    CheckSum:         008B6413
    ImageSize:        00910000
    File version:     21.10.2.2
    Product version:  1.0.1.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.6 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Intel Corporation
        ProductName:      Intel® Wireless WiFi Link Adapter
        InternalName:     .sys
        OriginalFilename: .sys
        FileVersion:      21.10.2.2
        FileDescription:  Intel® Wireless WiFi Link Driver
        LegalCopyright:   Copyright © Intel Corporation 2011
        Comments:         NDIS650_MINIPORT

you should also disable the Logitech system information plugin that disables cpu temps, its not a safe driver.

See what you find when you dig
https://answers.microsoft.com/en-us...rnvmesys/35ad2258-1311-47b2-881d-c228417190af

Gigabytes rainbow puke software corrupts the state of memory in this case those specific to storage and snapshot drivers.

 

I have put my RAM on 3200MHz so that it's stable. Are you saying that my RAM is not stable, even at 3200MHz? AMD specifies that 3200MHz should be stable for Ryzen 3. RGB Fusion might also be the cause and a few drivers? I just want the problems to be solved. Thanks for helping me.

 

It is highly likely to involve RGB Fusion's drivers corrupting the storage drivers..

There are also cases of the GDrv2 erasing entire disks
https://www.reddit.com/r/gigabytega...fusion_has_done_some_serious_damage_to_my_pc/

 

Okay, so I'm back on 2004 and I have uninstalled RGB Fusion. I'm gonna see if I still get BSODs. If I do I'll report back.

 

18:30
PC is on and still no BSODs with RGB Fusion uninstalled. It does seem like RGB Fusion caused the BSODs. Still I'm not entirely sure 2004 is running well. Hopefully I won't run into BSODs today. That would give me the confirmation that it really is RGB Fusion causing all the trouble.

20:00
Well, it's still running. I would like to thank forum users that informed me, so thanks!

 

Well, I thought I had fixed the issue, but now I also get a BSOD after waking up from sleep mode with the same error messages. RGB Fusion is already uninstalled as I said. Running 2004 is still unstable for me.

 

I think what would be best is a clean slate by updating your BIOS l (if it’s already updated, a CMOS reset), enforce UEFI in BIOS, completely wipe W10 and create a brand new W10 2004 ISO, install, grab the newest chipset, audio, LAN and GPU drivers etc, install and start again with all your regular software and try to avoid RGB/system tuning utility’s from manufacturers.

If it still crashes you may need to diagnose your components one by one.

 

Thanks for responding Nicked_Wicked. I have done everything you mentioned, but it still gives me trouble. I hope I can still RMA my components, because I have been using them for a couple months now. Week after week it gives me trouble. I try anything I can to make the system stable, but it doesn't matter. I'm just really sad, because it's a lot of money that I've spent. I hope I can RMA my CPU and motherboard, because I suspect them both of causing the problem. I also hope that it's just a problem related to build 2004 of Windows 10. I also have an issue overclocking the RAM on my system, it doesn't get to 3600MHz on XMP. I have to put it on 3200MHz. All this bull makes me want to go Intel and just be done with it. But leaving the red team would also not be good since the 3900x is way better than what Intel offers at the moment. I'm really sick and tired of this mess. I hope the store where I bought the 3900x and mobo offers me a new one (exchange), but the chance that happens is very small.

 

It might not be a hardware fault, if its only triggering after a wake from sleep/hibernate or fast startup boot it could be that an older samsung nvme driver is present (i did not see one at all when i looked through the drivers in the dump)

Samsung nvme 3.1 or later is required to resolve a bsod that occurs in windows 1809+

It could also be an issue with the mobo bios where incorrect memory settings are restored after resume from sleep.

You could have a 3900x with a weak memory controller, or faulty ram, so it could be either of those two as well

Bsods in storage drivers are really uncommon outside of using vendors own ahci packages or some firmware bug with the device.