Question BSOD --- "Your device ran in to a problem and needs to restart" ?

[fly_jack]

Hi All, first time posting here. Was playing MC and got a BSOD out of no where. Can't figure out what I need to do to remedy the error... seeking help.

BSOD and event viewer for that moment can be found here:

https://imgur.com/a/B7X95mY

View: https://imgur.com/a/B7X95mY


Computer Specs:
Case: iBUYPOWER Slate HAKO MR Tempered Glass ARGB
Processor: Intel® Core™ i7-11700KF Processor (8X 3.60GHz/16MB L3 Cache)
Motherboard: ASRock Z590-C/AC
Memory: 16GB [8GB x 2] DDR4-3600MHz RGB
Video Card: GeForce RTX 3060 Ti - 8GB GDDR6 (VR-Ready)
Power Supply: 600 Watt - 80 PLUS Gold CertifiedProcessor
Cooling: iBUYPOWER 240mm Addressable RGB Liquid Cooling System
Keyboard: iBUYPOWER RGB Gaming KeyboardMouse: iBUYPOWER Gaming Optical Mouse
Operating System: Windows 11 HomeStorage: 1TB Samsung 980 M.2 PCIe NVMe SSD

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[fly_jack]

Colif,

Thanks for the response! Here you go, does this work?
https://drive.google.com/file/d/1zjCSBVdATbCmXqUOBzQCbjxZt2_gO8CZ/view?usp=sharing

 

[Colif]

Colif,

Thanks for the response! Here you go, does this work?
https://drive.google.com/file/d/1zjCSBVdATbCmXqUOBzQCbjxZt2_gO8CZ/view?usp=sharing

can you share link with anyone who has it, right now you need access.

 

[fly_jack]

Woops... sorry about that.
https://drive.google.com/file/d/1zjCSBVdATbCmXqUOBzQCbjxZt2_gO8CZ/view?usp=sharing

 

[NiveusT]

Having a similar issue. Following this post. I think his .dmp file above is shared properly now.

 

[Colif]

there was a reason I asked for minidumps as well, they won't be 2gb in size.
I have to make space on my VM to download that file. And it will only show me as much as a Minidump will.

I thought @ubuysa might have looked at this before now. He would see more in it than I will.

once i work out why my vm thinks its full even after emptying windows update history, I will run the conversion

Sorry I took so long. I think I had looked at file size and knew that would be fun to install on my 32gb vm as it was running out of space. I hoped someone else would look.
I had to make a new VM to run it now, so 5 hours later... here is results...


report


File: MEMORY.DMP (Jun 15 2024 - 17:02:18)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: ntkrnlmp.exe (Process: WmiPrvSE.exe)
Uptime: 0 Day(s), 12 Hour(s), 45 Min(s), and 06 Sec(s)

Comment: 2 or more types of RAM are installed.

Memory: 16GB [8GB x 2] DDR4-3600MHz RGB

your ram description doesn't agree with what PC reports
8192MB 2000MHz Corsair CMK16GX4M2D3600C18
8192MB 2400MHz Team Group Inc TEAMGROUP-UD4-3600
8192MB 2000MHz Corsair CMK16GX4M2D3600C18
8192MB 2400MHz Team Group Inc TEAMGROUP-UD4-3600

Intel systems better running missmatching ram but it still can cause problems...
How long have you used both?

strange, you had no drivers loaded...

 

[fly_jack]

Apologies- I pulled the PC specs from when I purchased the machine. I did upgrade my RAM as you have it there. Sorry about that.

 

[fly_jack]

Adding- minidump incase it is still needed.
https://drive.google.com/file/d/16ufrSo0bCpr8_pcEKWZnMWZBDS-dqnpk/view?usp=sharing

 

[Colif]

How long ago did you change ram?
Was it a long time before errors started?

File: 061524-10421-01.dmp (Jun 15 2024 - 17:02:18)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: ntkrnlmp.exe (Process: WmiPrvSE.exe)
Uptime: 0 Day(s), 12 Hour(s), 45 Min(s), and 06 Sec(s)

report

Did this PC ever have an AMD GPU in it? If not, I have to wonder what IBuypower are doing.

Jul 24 2020	amdxe.sys	AMD Link Xinput Emulation driver
Feb 05 2021	amdkmpfd.sys	AMD Kernel Miniport Filter driver
Mar 20 2021	amdfendr.sys	AMD Crash Defender Service driver

these files are part of radeon graphics card drivers?

I would run DDU in safe mode, uninstall AMD drivers, and boot back into normal mode again.

How To - How to perform a CLEAN install of your video card drivers.

Updated 9-19-19 How to do a CLEAN install of your graphics card drivers using the Wagnard tools Display Driver Uninstaller A major issue on many systems is the presence of multiple graphics card drivers or drivers that have been incompletely uninstalled followed by the installation of...

forums.tomshardware.com

A PC with an Intel CPU and Nvidia GPU shouldn't have AMD drivers on it?

 

[ubuysa]

Sorry for my tardiness in replying, I'm still recovering from eye surgery and I have to limit my time on the PC.

The dump you uploaded shows that the BSOD happened because the instruction pointer was misaligned whilst running a Windows function. The trap frame shows the problem...

3: kd> .trap fffff58c2c315b60
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff58c2c317368 rbx=0000000000000000 rcx=0000000000000068
rdx=fffff58c2c316590 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804798e58d8 rsp=fffff58c2c315cf0 rbp=fffff58c2c315cf0
 r8=fffff58c2c317510  r9=fffff58c2c316550 r10=fffff8047944bfb0
r11=fffff58c2c3163a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PspGetContext+0x18c:
fffff804`798e58d8 82              ???

You can see that the instruction pointer (the RIP register) is pointing 0x18C bytes into the the Windows function nt!PspGetContext and at that address is an instruction with opcode 0x82 - this opcode doesn't exist, hence the BSOD. If I disassemble the relevant part of the nt!PspGetContext function you can see clearly that the instruction pointer is misaligned...

....
fffff804`798e58c5 488b82e0000000  mov     rax,qword ptr [rdx+0E0h]
fffff804`798e58cc 488b08          mov     rcx,qword ptr [rax]
fffff804`798e58cf 48898bd8000000  mov     qword ptr [rbx+0D8h],rcx
fffff804`798e58d6 488b82e8000000  mov     rax,qword ptr [rdx+0E8h]     <=== The RIP register is pointing two bytes further on than it should be!
fffff804`798e58dd 488b08          mov     rcx,qword ptr [rax]
...

This is not a problem with the nt!PspGetContext function because it's a native Windows function (it's part of the process and thread subsystem). In addition there are no third-party drivers referenced in the lead-up to the BSOD and that strongly suggests that this is most likely a hardware problem.

I can see from the dump that you have mixed RAM sticks. You have two TEAMGROUP-UD4-3600 sticks and two Corsair CMK16GX4M2D3600C18 sticks. They may look to have the same specs but mixing RAM sticks is a very common cause of problems. Whilst it's risky making a firm diagnosis based on one dump I would recommend removing one pair of RAM sticks (either the TeamGroup pair or the Corsair pair) and see whether the system is stable.

If you have other dumps please upload them all.

I can also see that an EasyAntiCheat driver unloaded immediately prior to the BSOD and that's always suspect. All the anti-cheat products cause multiple BSODs on many systems and EasyAntiCheat is certainly no exception. I still suspect that the mixed RAM is the most likely cause of what we see in this dump, but EasyAntiCheat cannot be discounted yet.

BTW. I agree with @Colif that those AMD drivers are curious - they're old too dating from 2020 and 2021. How did they get installed and why?