System crashes due to memory issues, but diagnostics report normal status.
System crashes due to memory issues, but diagnostics report normal status.
Hello, I encountered a RAM problem on my old system I use for daily tasks since I reinstalled Windows in September 2022. When I use all four RAM modules (16GB), I get a BSOD during memory management after stress testing and opening apps like Chrome. Everything works fine with just two modules (8GB). It doesn’t matter which slots they’re in. This is my self-built desktop setup: some components are refurbished, but the overall specs stayed consistent. CPU: Intel Core i5-6600 3.3 GHz Quad-Core Motherboard: MSI Z170-A PRO ATX LGA1151 Memory: G.Skill Ripjaws V 8 GB (2 x 4 GB) DDR4-2133 CL15 RAM – I have two more, but that’s the problem Video Card: MSI AERO ITX OC GeForce GTX 1060 6GB 6 GB Video Card Power Supply: be quiet! Dark Power Pro 10 650 W 80+ Gold Certified Semi-modular ATX Power Supply Case: Thermaltake Versa G2 ATX Mid Tower Case OS Edition Windows 10 Pro 64bit Version 22H2 Betriebssystembuild 19045.2486 Leistung Windows Feature Experience Pack 120.2212.4190.0 Installed Sep 2022 I also tried every RAM bar: (using the MemoryDiagnostic tool) LaunchType Manual CompletionType Pass MemorySize 8155 TestType 12 TestDuration 1073 TestCount 22 NumPagesTested 2086523 NumPagesUnTested 1257 Here are the Dump Files from today’s testing and back in September: https://drive.google.com/drive/folders/1...sp=sharing but the process doesn’t finish (I ran it for half an hour now). Sorry. Could this be related to the MB or the memory controller? How can I check that?
The Perfmon GUI appears to hang when launched via the Windows icon, yet the report is still generated. Consider executing it from the command prompt in admin mode. Using memtest86 might work better since it can run from a bootable disk, minimizing Windows interference during testing. The built-in memory diagnostic tool isn't reliable. You may want to re-seat your CPU or inspect the cooler mounting. Also verify your disks—run without using the pagefile initially, then create one and retest.