CmdKookie

Reputable
May 9, 2017
3
0
4,510
0
Good morning, midday, evening or even night,


Like all good problems start, I've built a new pc.

Specs are the following:
Motherboard - b450 gaming plus max
Gpu – Gigabyte GeForce RTX 2060 OC – 6GB
Cpu - Ryzen 5 3600 4, 2GHz AM4 35MB Cache
Ram - Corsair Vengeance LPX 16GB (2x8GB) DDR4 3000MHz C16 XMP 2.0
PSU - Corsair cx series 650 watt 80 plus bronze certified
SSD – Corsair Force MP510 240 GB NVMe PCIe Gen 3 x4 M.2-SSD & Samsung evo 500 GB SSD

After a while I started having some nasty BSODs, the main one being ‘memory management’, but I’ve also seen system files crashing with the BSOD ‘system service exception’. On top of that games start randomly quitting without message and google chrome started having a error called ‘status access violation’.

So I’ve started my investigation into the main BSOD, and followed almost every step by step guide to try fix this annoying thing, hindering me of playing games and doing work.
Sadly I’m still here which means none of these solutions worked for me. I’ve tried al the following things:
  1. Running memory diagnostic tool from windows, which returned with no errors in the event viewer
  2. Running a sfc /scannow command in a elevated control panel, which also didn’t give any corrupted files as result
  3. I’ve updated my graphic card drivers, reinstalled them and again and again, no change
  4. I’ve switched my RAM from slots on the motherboard, but still no positive results
  5. Even reinstalled windows, but there it was again, the BSOD to piss me off
  6. Used every driver tool thinkable of and update all my drivers still BSOD
  7. Even checked for viruses (not the Covid-one) and there it is again
I’ve probably did even more than this, I did so much trying to get it work but there’s absolutely no change.
As a last resort, I come to all of you, hoping one of you got the final epic, working solution.

This is what the event viewer showed me what happened right before the crash:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041792, 0xffffefbffc79e1a8, 0x0000000000002000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: d47e6a1f-3f51-4cb7-adc8-a0b8b3a914fa.


Running a .dmp-file reader on the dump file gave me this:

Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 18362 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff80546c00000 PsLoadedModuleList = 0xfffff80547048170

Debug session time: Tue May 26 09:46:32.925 2020 (UTC - 7:00)

System Uptime: 0 days 1:13:36.595

Loading Kernel Symbols

...............................................................

................................................................

......Page 1328aa not present in the dump file. Type ".hh dbgerr004" for details

..................................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 0000009cef136018). Type ".hh dbgerr001" for details

Loading unloaded module list

...............

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff805
46dc2390 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc80eccd5f70=000000000000001a

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of

the PTE. Parameters 3/4 contain the low/high parts of the PTE.

Arg2: ffffefbffc79e1a8

Arg3: 0000000000002000

Arg4: 0000000000000000

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec

Value: 2

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-R2SAKK1

Key : Analysis.DebugData

Value: CreateObject

Key : Analysis.DebugModel

Value: CreateObject

Key : Analysis.Elapsed.Sec

Value: 12

Key : Analysis.Memory.CommitPeak.Mb

Value: 60

Key : Analysis.System

Value: CreateObject

ADDITIONAL_XML: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffefbffc79e1a8

BUGCHECK_P3: 2000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: smartscreen.exe

STACK_TEXT:

fffffc80
eccd5f68 fffff80546e502b8 : 000000000000001a 0000000000041792 ffffefbffc79e1a8 0000000000002000 : nt!KeBugCheckEx

fffffc80
eccd5f70 fffff80546ce3d07 : ffffd9094e4e35c0 ffffefbffc79e1a8 0000000000000000 0000000000000000 : nt!MiDeleteVa+0x16a7b8

fffffc80
eccd6080 fffff80546ce41c1 : fffffc80eccd64d0 ffffeff7dffe3cf0 0000000000000000 0a000003416e2867 : nt!MiWalkPageTablesRecursively+0x1e7

fffffc80
eccd6140 fffff80546ce41c1 : fffffc80eccd64d0 ffffeff7fbefff18 0000000000000000 0a000002eefda867 : nt!MiWalkPageTablesRecursively+0x6a1

fffffc80
eccd6200 fffff80546ce41c1 : fffffc80eccd64d0 ffffeff7fbfdf7f8 ffffeff700000000 0a000001567d2867 : nt!MiWalkPageTablesRecursively+0x6a1

fffffc80
eccd62c0 fffff80546ce394c : fffffc80eccd64d0 0000000000000000 fffffc8000000000 fffffc80eccd6449 : nt!MiWalkPageTablesRecursively+0x6a1

fffffc80
eccd6380 fffff80546ce1db8 : fffffc80eccd64d0 0000000000000002 0000000000000001 0000000000000000 : nt!MiWalkPageTables+0x36c

fffffc80
eccd6480 fffff80546ceff10 : ffffffffffffffff ffffd9094e4e3438 fffffc8000000001 0000000000000000 : nt!MiDeletePagablePteRange+0x268

fffffc80
eccd6820 fffff80547279a0d : ffffd909539f7040 ffffd909539f7040 ffffd9095bb0bea0 ffffd9094e4e3430 : nt!MiDeleteVad+0x860

fffffc80
eccd69e0 fffff80547288740 : ffffd9095bb0bea0 ffffd909560df010 ffffd909539f7040 0000000000000000 : nt!MiUnmapVad+0x49

fffffc80
eccd6a10 fffff80547287caf : ffffd9095bb0bf40 ffffd9095bb0bf40 ffffd9094e4e30c0 fffff8054706a440 : nt!MiCleanVad+0x30

fffffc80
eccd6a40 fffff805471de6d9 : ffffffff00000000 ffffffffffffffff 0000000000000001 ffffd9094e4e30c0 : nt!MmCleanProcessAddressSpace+0x137

fffffc80
eccd6ac0 fffff805474cb8f2 : 0000000000000700 ffffd9094e4e30c0 fffff805474cb8c0 ffffd9094768a250 : nt!PspRundownSingleProcess+0x139

fffffc80
eccd6b40 fffff80546cf43b5 : ffffd909539f7040 ffffd909539f7000 fffff80546c59900 ffffd9094768a250 : nt!PspProcessRundownWorkerSingle+0x32

fffffc80
eccd6b70 fffff80546c6bcd5 : ffffd909539f7040 0000000000000080 ffffd90947671380 0000000000beef00 : nt!ExpWorkerThread+0x105

fffffc80
eccd6c10 fffff80546dc9998 : ffffa60038080180 ffffd909539f7040 fffff80546c6bc80 4364657465677261 : nt!PspSystemThreadStartup+0x55

fffffc80
eccd6c60 0000000000000000 : fffffc80eccd7000 fffffc80eccd1000 0000000000000000 00000000`00000000 : nt!KiStartSystemThread+0x28

MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner

---------

Since I’m not a expect on bug files and dump files, I came here.

I sincerely hope somebody can help me,
Kind regards,
Dries
 

ASK THE COMMUNITY

TRENDING THREADS