nightrunner

Glad I could help! 😃

Ok, I grabbed a few screen shots for you as well. Here is a site that will link you to MEBx setup that enables AMT: http://h10032.www1.hp.com/ctg/Manual/c03883429

When power on your ProDesk G3, you can access the MEBx setup by pressing Ctrl+P or they also say F6 or Escape will get you there. Intel AMT runs on a different IP address than what your OS gets. You can assign DHCP or a static IP address and setup your admin password. You can then access the portal from http://ipaddress:16992 There should be a method of access what would show on the screen through a KVM like access but I use MeshCentral for that so I couldn't tell you how to do it without.

Hopefully, that gives you a start. Feel free to reach back out if you have any questions. Thank you!

I’m not in front of my computer atm, but I think I have something that can help you out. I have a 3-node Lenovo Thin client cluster that I manage their KVMs using the Intel vPro. I even went a step further using MeshCentral running on a VM to centralize my KVM access since I have 3 of them, but that’s another story.

Anyway, I’ll see if I can grab you some URLs in the morning if someone else doesn’t beat me to it or you find it on your own running google queries.

Ok, so looking at the BSOD minidumps, the BSOD from 2/13/24 and 1/10/2024 give a bug check event that is typically driver related. My recommendation would be to download prime95 and use the "Blend" test for a couple of hours to try and recreate the BSOD. If you don't get anything you can try running 3DMark to force it. It's easier when you can "recreate" the problem on purpose instead of waiting for it to happen. Once you reproduce the BSOD you can try and go through the Event Log and determine which driver was the cause since there will be an Application Error usually present.

If you can't find anything in the logs, you can always pull out all peripherals and use prime95 for another couple of hours making sure that the issue is gone. If you still get a BSOD, you've got other hardware causing the issue. (or you could have a combination of both)

If you can't reproduce the BSOD after unplugging the peripherals, plug one back in at a time stress testing to determine which peripheral is causing it. But you should be able to find it in the event log. I hope this helps.

I should be able to take a look tomorrow morning. I had a similar issue with an Intel Raptor Lake build. So I’ll let you know what I did to narrow it down.

2024 - Mexicans at the border (you know it’s already happening)

Lots of fluids and sleep. Remember the more she vomits, the more dehydrated she could get. So more water than normal.

For next time, if anyone takes too much go find some CBD. That will really help a person sober up in regards to THC.

There is a BSOD viewer by Nirsoft that is free located here: https://www.nirsoft.net/utils/blue_screen_view.html

This will allow you to take a look at the dump files that were created with each BSOD and typically give you the file name that typically is involved. Can you get that information and let us know what it gives you. This will give you a better idea of what the cause is.

3-Node ESXi cluster with 10 Debian VMs, 3 Windows VMs, and one FreeBSD VM

Examples: ServiceNow, Connectwise, Jira Service Desk

Look into getting a CMDB and keep track of all of your hardware. That can store the hostname / IPs of your KVM / OS or virtualization layer, vkernels, storage adapter IPs, your vCenters and so on and so forth. If your data is getting so big that spreadsheets are getting tough to manage, then you probable need a more enterprise method of storing it.

I couldn’t see it the wrong way at all until I really stared at it. Then once I saw it, I couldn’t unsee it. lol