F5F Stay Refreshed Hardware Desktop Error occurred when handling kmode exception, leading to system crash.

Error occurred when handling kmode exception, leading to system crash.

Error occurred when handling kmode exception, leading to system crash.

L
Lips
Senior Member
624
11-28-2021, 06:05 PM
#1
Hello, I recently assembled a new PC four days ago and have been experiencing random BSODs lately. Sometimes it happens after just three hours yesterday, while other times it occurs even after 32 hours. I've upgraded all my drivers, run a memtest four times with no issues, performed a clean install, removed the old SSD, and cleaned up everything. My hardware includes a 12700KF 3060 TI, ASUS 650W, Straight Power, Bequiet PRIME Z690-P with D4-CSM BIOS, CL16, G.Skill Ripjaws V SSD, and M.2 Samsung 980. The system runs Windows version 19044.1288 21H2. A dumpfile is attached for reference. Please let me know if you need further help (sorry, I’m not a native speaker). Thanks in advance. 091722-6218-01.rar
L
Lips
11-28-2021, 06:05 PM #1

Hello, I recently assembled a new PC four days ago and have been experiencing random BSODs lately. Sometimes it happens after just three hours yesterday, while other times it occurs even after 32 hours. I've upgraded all my drivers, run a memtest four times with no issues, performed a clean install, removed the old SSD, and cleaned up everything. My hardware includes a 12700KF 3060 TI, ASUS 650W, Straight Power, Bequiet PRIME Z690-P with D4-CSM BIOS, CL16, G.Skill Ripjaws V SSD, and M.2 Samsung 980. The system runs Windows version 19044.1288 21H2. A dumpfile is attached for reference. Please let me know if you need further help (sorry, I’m not a native speaker). Thanks in advance. 091722-6218-01.rar

F
FilhoDoZuko88
Member
64
11-28-2021, 07:25 PM
#2
Did you verify your RAM placement according to the manual? If correct, consider using the scannow console command to detect and fix any damaged system drivers. Launch the Command Prompt as an administrator and enter: sfc /scannow. Any corrupt files detected will be reported during the process. This should help!
F
FilhoDoZuko88
11-28-2021, 07:25 PM #2

Did you verify your RAM placement according to the manual? If correct, consider using the scannow console command to detect and fix any damaged system drivers. Launch the Command Prompt as an administrator and enter: sfc /scannow. Any corrupt files detected will be reported during the process. This should help!

C
ChibiXibi
Junior Member
1
12-11-2021, 06:31 PM
#3
The correctly installed Scannow detected some issues that need verification. The likelihood of RAM being faulty remains uncertain despite passing memtest.
C
ChibiXibi
12-11-2021, 06:31 PM #3

The correctly installed Scannow detected some issues that need verification. The likelihood of RAM being faulty remains uncertain despite passing memtest.

S
Silverr94
Member
60
12-12-2021, 02:02 AM
#4
When I see error messages, I naturally want to look at RAM, but those kinds of warnings usually mean "page fault in non-paged area." Likely your RAM is okay. Now that the issues have been resolved, just run your computer as usual and any further problems will point to something else.
S
Silverr94
12-12-2021, 02:02 AM #4

When I see error messages, I naturally want to look at RAM, but those kinds of warnings usually mean "page fault in non-paged area." Likely your RAM is okay. Now that the issues have been resolved, just run your computer as usual and any further problems will point to something else.