I got the dump files
#got a friend with a i7 13700f and it is doing the 14th gen thingy
tardy citrus
@modern berry The latest Windows 11 patch doesn't have debugging symbols for the Windows kernel so most of them just give this nonsense
All of them are DPC_Watchdog_Violation though so it's likely not the Intel issue.
You usually have debugging symbols for your own machine (If you are on the latest Win11 patch you might be able to read others on that patch as well). So if someone else or your friend could run these in a debugger and paste the output to text files for each dump, I could have a look.
Also want the commands !dpcs and !dpcwatchdog ran, but they often don't work properly on minidumps because Windows has discarded most of the data here.
modern berry
dam
tardy citrus
Because it's a DPC issue, it's usually drivers. It can be hardware, but when it's hardware it's usually things you plug in. USB, PCIe. Usually not motherboard/CPU.
modern berry
he got his first BSOD after 2 months and is now getting more and more
tardy citrus
@modern berry Did you have him check if he has a kernel dump? Have him open that in the debugger and see if that also gives wrong_symbols
modern berry
umm, well how do i find those?
tardy citrus
C:\Windows
Memory.dmp
The default dump configuration in Windows should be Automatic Memory Dump which creates a kernel and minidump on each crash. Kernel dumps are huge so they get overwritten, so you only have one.
They contain lots of stuff from RAM so there are some privacy issues with dealing with them, but with DPC crashes you kind of have to a lot of the time.
Things that are in plain text is readable. Like if you are on a website. The stuff in plain text like the article and tab names are readable.
modern berry
Memory.dmp
modern berry
he got another BSOD when using DDU