BSOD WIN8_DRIVER_FAULT Windows 10

[kitoyski]

hi, ive just built a new PC with AMD Ryzen 3 2200g / MSI A320 m Pro VH Plus / 16gb ddr 4 team elite

and im getting this error even after updating teh drivers, etc.

any help is much appreciated. thanks
--

FAULTING_IP:
nt!MmCheckCachedPageStates+1f6
fffff802`ad2be506 488b01 mov rax,qword ptr [rcx]

CONTEXT: ffffaa0ec3f94730 -- (.cxr 0xffffaa0ec3f94730)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffd04d003b0600 rdi=ffffd068341a0000
rip=fffff802ad2be506 rsp=ffffaa0ec3f95120 rbp=ffffaa0ec3f95220
r8=ffffd068341a07f8 r9=000000000017915d r10=ffff9400046b4170
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=ffffd04d003b0600 r15=0000000000000000
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!MmCheckCachedPageStates+0x1f6:
fffff802`ad2be506 488b01 mov rax,qword ptr [rcx] ds:002b:00000000`00000000=000000000000581c
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

BAD_PAGES_DETECTED: 581c

LAST_CONTROL_TRANSFER: from fffff802ad2be23d to fffff802ad2be506

STACK_TEXT:
ffffaa0e`c3f95120 fffff802`ad2be23d : ffff97a8`1873fff0 00000000`00000000 00000000`00000001 ffffd604`fce4c180 : nt!MmCheckCachedPageStates+0x1f6
ffffaa0e`c3f95300 fffff802`ad71a183 : 00000000`00000001 00000000`00000001 ffffaa0e`c3f95301 ffffaa0e`00000000 : nt!CcMapAndRead+0xdd
ffffaa0e`c3f95360 fffff800`455de110 : ffffd604`fd102dd8 ffffd605`025e6dc8 ffffd605`025e6dc8 ffffd605`00040000 : nt!CcMapData+0x93
ffffaa0e`c3f953d0 fffff800`455def29 : 00000000`00008000 ffffd605`025e6dc8 00000000`00a80000 00000000`00000202 : Ntfs!NtfsMapStream+0x60
ffffaa0e`c3f95420 fffff800`456f2adb : ffffd605`025e6dc8 ffff9a00`760c0000 ffffd604`fe34d880 00000000`04000000 : Ntfs!NtfsMapOrPinPageInBitmap+0x79
ffffaa0e`c3f95460 fffff800`456ae899 : ffffd605`025e6dc8 fffff800`4553f900 00000000`00000000 ffffd604`00800008 : Ntfs!NtfsGetVolumeBitmap+0x30f
ffffaa0e`c3f95540 fffff800`455ed0eb : ffffd605`025e6dc8 00000000`00000001 00000000`00000000 00000000`00000000 : Ntfs!NtfsUserFsRequest+0xc14e9
ffffaa0e`c3f955c0 fffff802`ad289189 : ffffd605`0245bbf0 ffffaa0e`c3f957c0 ffffd604`fdeee6d0 fffff800`44af629c : Ntfs!NtfsFsdFileSystemControl+0x13b
ffffaa0e`c3f956f0 fffff800`44af7207 : ffffaa0e`c3f957c0 fffff800`44af53b4 00000000`00000000 00000000`0000000d : nt!IofCallDriver+0x59
ffffaa0e`c3f95730 fffff800`44b2aed0 : ffffaa0e`c3f957c0 ffffd605`0234fef0 ffffd605`0234fef0 ffffd604`fe1a1660 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x157
ffffaa0e`c3f957a0 fffff802`ad289189 : ffffd604`fdeee6d0 ffffd605`0234fef0 00000000`00000001 00000000`00000000 : FLTMGR!FltpFsControl+0x110
ffffaa0e`c3f95800 fffff802`ad6fc2eb : ffffd604`fdeee6d0 ffffaa0e`c3f95b80 00000000`00000001 00000000`00000000 : nt!IofCallDriver+0x59
ffffaa0e`c3f95840 fffff802`ad70822f : ffffd605`00000000 ffffd605`0234ff40 00000000`00000000 ffffaa0e`c3f95b80 : nt!IopSynchronousServiceTail+0x1ab
ffffaa0e`c3f958f0 fffff802`ad7a49f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x66f
ffffaa0e`c3f95a20 fffff802`ad3ad943 : ffff8200`7690ea60 fffff802`ad707add 00000000`00000000 00007ff8`5bd1d3c0 : nt!NtFsControlFile+0x56
ffffaa0e`c3f95a90 00007ff8`5bc5a5d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000009c`6517e0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff8`5bc5a5d4


SYMBOL_NAME: PAGE_NOT_ZERO

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xffffaa0ec3f94730 ; kb

BUCKET_ID: PAGE_NOT_ZERO

Followup: MachineOwner
---------

*** Memory manager detected 22556 instance(s) of page corruption, target is likely to have memory corruption.

 

[johnbl]

check for motherboard bios updates and apply them, check for motherboard sata driver and chipset updates from the motherboard vendors website.

make sure you apply the current windows updates to get Microsoft cpu specific patches for fixing known bugs in the new cpus.

also check for firmware updates if you have a ssd. use crystaldiskinfo.exe to read firmware version and smart data from drive.

I would turn off the virtual memory and then turn it back on to delete the c:\pagefile.sys and create a new one.

bugcheck was in the cache manager related to the ntfs (file system)

you might disable lazy writes to you drive.

 

[kitoyski]

check for motherboard bios updates and apply them, check for motherboard sata driver and chipset updates from the motherboard vendors website.

make sure you apply the current windows updates to get Microsoft cpu specific patches for fixing known bugs in the new cpus.

also check for firmware updates if you have a ssd. use crystaldiskinfo.exe to read firmware version and smart data from drive.

I would turn off the virtual memory and then turn it back on to delete the c:\pagefile.sys and create a new one.

bugcheck was in the cache manager related to the ntfs (file system)

 

[kitoyski]

i think ive done all of these until i just found out that the RAM model isnt on the supported list of the mobo... maybe that explains the frequent BSOD...

thank you for your response, though. appreciate it.

 

[johnbl]

if you suspect ram, you should update the bios and boot and run memtest86 to confirm the bios memory timings are ok.
if should fail quickly if the timings are incorrect.

i think ive done all of these until i just found out that the RAM model isnt on the supported list of the mobo... maybe that explains the frequent BSOD...

thank you for your response, though. appreciate it.

 

[kitoyski]

everything is updated. ive just found out that the RAM modules are not on the supported list of my mobo. is there any solution apart from changing the parts?

 

[johnbl]

update the bios to get the best new memory timing defaults. Then run memtest86 on its own boot image to see if you get any memory errors. if you do get memory errors you will have to look up the ram module primary and secondary timings and enter them in to bios. Most vendors do not name all of the varous modules in their qualified vendor list.
they do update the timing defaults in bios with out listing the changes. it is pretty common for a vendor to test with faster ram and use fast default timings . if all else fails I would set the secondary timing for command rate to 2n or 2T
(it is a common problem)

everything is updated. ive just found out that the RAM modules are not on the supported list of my mobo. is there any solution apart from changing the parts?