Numerous blue screens appearing, each displaying unique error messages.
Numerous blue screens appearing, each displaying unique error messages.
I've encountered frequent blue screens recently. Common examples include: PAGE FAULT, KERNEL SECURITY CHECK FAILURE, and SYSTEM SERVICE EXCEPTION. I've checked the memory and SSD—both passed—and updated drivers, even reinstalling Windows. I've shared two recent minidump files here: https://files.catbox.moe/v3is7e.rar. Additional details: these crashes typically occur during shutdown or restart attempts, happening roughly 70% of the time when the system is actively running. They usually happen about three times in a while. The codes I recall are: SYSTEM SERVICE EXCEPTION, KERNEL SECURITY CHECK FAILURE, and possibly KMODE EXCEPTION NOT HANDLED. My setup includes an i3-10105F GTX 1650 i5 motherboard, BIOS up to date, 16 GB DDR4 RAM, Gigabyte gp-gsm2ne3512gntd memory, and a M.2 SSD. Any guidance would be greatly appreciated.
When you restored Windows, did you switch to another USB drive and download the installation files again? Occasionally problems continue if you reuse the same USB and install media. 2) If changing the USB and files doesn’t help, try disconnecting each part one by one—without opening Windows—and check if the problem remains with every component removed.
I didn't switch to another boot source, I'll give it a shot later. 2. Should the first one not work, I'll attempt the same. A new problem just appeared. Right now my Discord was abruptly closed and won't reopen. In the event log it reads: 'Faulting application name: Discord.exe, version: 1.0.9008.0, time stamp: 0x6255d9bd Faulting module name: Discord.exe, version: 1.0.9008.0, time stamp: 0x6255d9bd Exception code: 0xc0000005 Fault offset: 0x01b36402 Faulting process id: 0x2748 Faulting application start time: 0x01d91c3b93324182 Faulting application path: C:\Users\xx\AppData\Local\Discord\app-1.0.9008\Discord.exe Faulting module path: C:\Users\xx\AppData\Local\Discord\app-1.0.9008\Discord.exe Report Id: 09f3505d-9a72-46e1-9808-867137110ed9 Faulting package full name: Faulting package-relative application ID: ' This suggests it might be an OS or driver issue rather than hardware, or there are clues pointing to hardware problems. Another app crashed too—related to Razer. Event log notes: The THXService service ended unexpectedly, only once.'
I didn't test an SSD myself, but I can describe how someone typically tests one.
On the label reads: 3200MHz C22 PC4-25600 1.2V 235Y MD4U0832220BB1ST B
Additionally, I had a doubt about what would happen if I tried to restart again—it actually did. The system crashed after a restart. This summary comes from the report: Microsoft ® Windows Debugger Version 10.0.20348.1 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\123022-6171-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`58400000 PsLoadedModuleList = 0xfffff805`5902a290 Debug session time: Fri Dec 30 05:59:54.697 2022 (UTC - 5:00) System Uptime: 0 days 0:44:19.345 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ... Loading User Symbols Loading unloaded module list ...... For analysis of this file, run !analyze -v 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be checked individually. 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: ffff92800001c7d0 Arg3: 0000000000020000 Arg4: 0000000000000000 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2139 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-P74VIKK Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 2116 Key : Analysis.Init.CPU.mSec Value: 749 Key : Analysis.Init.Elapsed.mSec Value: 24834 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 1a BUGCHECK_P1: 41792 BUGCHECK_P2: ffff92800001c7d0 BUGCHECK_P3: 20000 BUGCHECK_P4: 0 MEMORY_CORRUPTOR: ONE_BIT BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: explorer.exe STACK_TEXT: fffff58f`aadf6c48 fffff805`586c5f8a : 00000000`0000001a 00000000`00041792 ffff9280`0001c7d0 00000000`00020000 : nt!KeBugCheckEx fffff58f`aadf6c50 fffff805`58638ac6 : 00000000`00000000 00000000`00000000 00000000`00000000 0000001e ffff9280`0001c7d0 : nt!MiDeleteVa+0x153a fffff58f`aadf6d50 fffff805`58638bdb : fffff92c9`400000e0 ffff828d`09b5e700 fffff58f00000000 fffff58f`00000000 fffff58f`aadf71c0 : nt!MiWalkPageTablesRecursively+0x776 fffff58f`aadf6df0 fffff805`58638bdb : fffff92c9`00000000 ffff828d`09b5e700 fffff58f`00000001 fffff58f`aadf71d0 : nt!MiWalkPageTablesRecursively+0x88b fffff58f`aadf6e90 fffff805`58638bdb : fffff92c9`64a00000 ffff828d`09b5e700 fffff58f`00000002 fffff58f`aadf71e0 : nt!MiWalkPageTablesRecursively+0x88b fffff58f`aadf6f30 fffff805`5860b83b : 00000000`00000000 ffff828d`09b5e700 00000000`00000003 fffff58f`aadf71f0 : nt!MiWalkPageTablesRecursively+0x88b fffff58f`aadf6fd0 fffff805`58638bdb : fffff92c9`64a00000 ffff828d`09b5e700 fffff58f`00000001 fffff58f`aadf71d0 : nt!MiWalkPageTables+0x36b fffff58f`aadf70d0 fffff805`58638bdb : fffff92c9`00000000 ffff828d`09b5e700 ffffc680`93a78770 fffff58f`aadf7820 00000000`00000000 : nt!PspRundownSingleProcess+0x20c fffff58f`aadf7660 fffff805`58b012c8 : 00000000`40010004 00000000`00000001 00000000`00000000 00000000`008c6000 : nt!PspExitThread+0x5f6 fffff58f`aadf7760 fffff805`58615877 : 00000000`00000000 00000000`00000000 00000000 00000000`00000000 00000000 : nt!KiSchedulerApcTerminate+0x38 fffff58f`aadf77a0 fffff805`587fe6f0 : 00000000`0e6b7438 fffff58f`aadf7850 00000000`00000000 00000000`00000000`00000000`00000000`00000000`00000000`00000000`00000000`00000000`3f06a104` 00000000`00000000 00000000`00000000`00000000`3f06a104 MODULE_NAME: hardware IMAGE_NAME: memory_corruption STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7} Followup: MachineOwner --------- 4: kd> lmvm hardware Browse full module list start end module name