• Now's your chance win big! Join our community and get entered to win a RTX 2060 GPU, plus more! Join here.

    Meet Stan Dmitriev of SurrogateTV on the Pi Cast TODAY! The show is live August 11th at 2:30 pm ET (7:30 PM BST). Watch live right here!

    Professional PC modder Mike Petereyns joins Scharon on the Tom's Hardware Show live on Thursday, August 13th at 3:00 pm ET (8:00 PM BST). Click here!

Question BSOD occurs, different errors each time.

Jun 1, 2020
8
1
15
0
I have here, a friends high end gaming PC, couldn't tell you the specs on the spot. However, I can give you the dump files from the past 2 BSOD events, that happened today. If anyone can assist that would be greatly appreciated. We're all out of ideas.

Check out the drop box link, they will both be in a separate word doc.

https://www.dropbox.com/sh/80okap0z73ewrka/AAByhyfzavtu3XqLXxvbf3Xka?dl=0

Again, thank you and stay safe, I look forward to any suggestions on what could be causing this so frequently.

Edit: As of now, he is running an app called MemTest86+ to check for any memory issues.
 
Jun 1, 2020
8
1
15
0
Hi, please upload the actual minidumps from the C:\Windows\minidump folder as I can get more information from them such as the full driver list.
Thank you for responding, I'm working on that as we speak. Sorry for the late reply, would you like the full specs also?

Thanks again,

Jordan.
 
Jun 1, 2020
8
1
15
0
Hi, please upload the actual minidumps from the C:\Windows\minidump folder as I can get more information from them such as the full driver list.
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.
* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff8003acb1000 PsLoadedModuleList = 0xfffff8003b0cb6f0
Debug session time: Tue Jun 2 13:42:05.520 2020 (UTC + 1:00)
System Uptime: 0 days 0:22:28.198
Loading Kernel Symbols
....................................Page 20081cbd6 too large to be in the dump file.
Page 20081cbd5 too large to be in the dump file.
...........................
................................................................
.................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000011c7018). Type ".hh dbgerr001" for details
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800
3ae68ab0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff3089a30f270=0000000000000050
1: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff63cc45ae770, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff697dae386ef, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Page 20081a87a too large to be in the dump file.
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-U38I538
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 10
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 50
BUGCHECK_P1: fffff63cc45ae770
BUGCHECK_P2: 0
BUGCHECK_P3: fffff697dae386ef
BUGCHECK_P4: 2
READ_ADDRESS: fffff63cc45ae770
MM_INTERNAL_CODE: 2
IMAGE_NAME: win32kfull.sys
MODULE_NAME: win32kfull
FAULTING_MODULE: fffff697dae00000 win32kfull
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
PROCESS_NAME: iCUE.exe
TRAP_FRAME: fffff3089a30f550 -- (.trap 0xfffff3089a30f550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff6b6c62518a0 rbx=0000000000000000 rcx=fffff63cc45ae730
rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000
rip=fffff697dae386ef rsp=fffff3089a30f6e0 rbp=fffff3089a30fa80
r8=0000000000000003 r9=0000000000000001 r10=0000000000000003
r11=fffff3089a30f920 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32kfull!PhkFirstValid+0x17:
fffff697
dae386ef 8b4140 mov eax,dword ptr [rcx+40h] ds:fffff63cc45ae770=????????
Resetting default scope
STACK_TEXT:
fffff308
9a30f268 fffff8003ae94b73 : 0000000000000050 fffff63cc45ae770 0000000000000000 fffff3089a30f550 : nt!KeBugCheckEx
fffff308
9a30f270 fffff8003ad61c68 : 0000000000000000 ffff800000000000 0000000000003dff fffff63cc45ae770 : nt!MiSystemFault+0x1b9673
fffff308
9a30f3b0 fffff8003ae765c9 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!MmAccessFault+0x1d8
fffff308
9a30f550 fffff697dae386ef : ffffdf83abed7710 fffff8003ad6f0de ffffc9f1559e898b fffff697db1a334b : nt!KiPageFault+0x349
fffff308
9a30f6e0 fffff697daf4eeff : fffff3089a30f920 0000000000000400 0000000000000000 0000000000000001 : win32kfull!PhkFirstValid+0x17
fffff308
9a30f710 fffff697dae6ba2f : fffff6b6c62518a0 fffff3089a30fa80 0000000000003dff 0000000000060001 : win32kfull!xxxCallHook+0x57
fffff308
9a30f750 fffff697dae6a9b7 : fffff3089a30f920 fffff3089a303dbf 0000000000000000 0000000000000f33 : win32kfull!xxxRealInternalGetMessage+0xfff
fffff308
9a30f8e0 fffff8003ae7a23e : 0000000000f1e0c0 ffffdf83b09a2080 fffff3089a30f9a8 00000000011c9000 : win32kfull!NtUserPeekMessage+0x157
fffff308
9a30f990 00007ffc0304f4e4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x2b9
00000000
00f1e088 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc0304f4e4
SYMBOL_NAME: win32kfull!PhkFirstValid+17
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 17
FAILURE_BUCKET_ID: AV_R_INVALID_win32kfull!PhkFirstValid
OS_VERSION: 10.0.17763.1
BUILDLAB_STR: rs5_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8745698e-47c5-9b39-b84d-d9bbc955dbf1}
Followup: MachineOwner
---------


that is all we got, since it has changed in that more detailed folder, because since last night it has occured again. Thank you for your time and help <3
 

gardenman

Admirable
Moderator
Upload the actual minidump file(s). Not a document or the debugger output. I can pull more info from dump files including full driver list, some hardware specs, BIOS info, and more. Note that you may have to copy them another folder first due to permissions.
 
Jun 1, 2020
8
1
15
0
Upload the actual minidump file(s). Not a document or the debugger output. I can pull more info from dump files including full driver list, some hardware specs, BIOS info, and more. Note that you may have to copy them another folder first due to permissions.
Oh sorry dude my bad, I'll get on that in the next 20 mins or so if that is okay? Just, he is away from his PC at the moment :)
 
Jun 1, 2020
8
1
15
0
Upload the actual minidump file(s). Not a document or the debugger output. I can pull more info from dump files including full driver list, some hardware specs, BIOS info, and more. Note that you may have to copy them another folder first due to permissions.
Bummer he just went to bed early, am I okay to post back here when he is able to send me the dump files, tomorrow? so it's the ones from C:\Windows\Minidump correct? :) thank you again for your time.
 

gardenman

Admirable
Moderator
I ran the dump files through the debugger and got the following information: https://pastebin.com/93jsis5x
File information:060220-14250-01.dmp (Jun 2 2020 - 17:02:21)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: obs64.exe)
Uptime:0 Day(s), 5 Hour(s), 10 Min(s), and 11 Sec(s)

File information:060220-13265-01.dmp (Jun 2 2020 - 08:42:05)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: iCUE.exe)
Uptime:0 Day(s), 0 Hour(s), 22 Min(s), and 28 Sec(s)

File information:060120-16593-01.dmp (Jun 1 2020 - 11:45:00)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: amd64_micr...)
Uptime:0 Day(s), 2 Hour(s), 18 Min(s), and 50 Sec(s)

File information:060120-13390-01.dmp (Jun 1 2020 - 17:31:02)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP (7F)
Driver warnings:*** WARNING: Unable to verify timestamp for BEDaisy.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 5 Hour(s), 14 Min(s), and 19 Sec(s)
Possible Motherboard page: https://www.asus.com/us/Motherboards/PRIME-Z270-K/
There is a BIOS update available for your system. You are using version 1002 and the latest is version 1207. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Colif may reply later today.
 
Jun 1, 2020
8
1
15
0
I ran the dump files through the debugger and got the following information: https://pastebin.com/93jsis5x
Possible Motherboard page: https://www.asus.com/us/Motherboards/PRIME-Z270-K/
There is a BIOS update available for your system. You are using version 1002 and the latest is version 1207. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

Colif may reply later today.
Thank you for the advice! We tried unplugging ram 1 by 1, they all tested okay, before that we had unplugged HDD and it didn't blue screen, so today after he has finished streaming we are planning on plugging the HDD back in, and will respond if it bluescreens again, thank you for thr response! also, will tyr updating BIOS
 
Reactions: gardenman

ASK THE COMMUNITY

TRENDING THREADS