Post deleted by User.
Blue Screen Of Death Every Other Day, Memtest Fine |
||
|
Blue screen of death every other day, memtest fine
you need to use windbg on the bluescreen file
system32 memory.dmp or system32/minidump if you have a fancier setup inside windbg you really dont need to know what you are looking at only a guesstimate itll point you at a driver or something and you can get a better idea feed most of it into an ai like copilot and it will give you some pretty good pointers come back with the main fault/error that pops up on the bluescreen I mean. Whats the code on your BSOD. That's where you start.
3 posts in one minute all same answer. Well played fellas. I guess I can expand. The 2 times I've had consistant bsods were the HDD was dying, and the psu was dying. Don't remember the error for hdd, but the psu kept throwing kernal error. ? Option 1: Disable via Xbox Game Bar Settings
- Go to Settings > Gaming > Captures. - Turn off "Record what happened" and other capture options. - Go to Settings > Gaming > Xbox Game Bar and disable it. ? Option 2: Disable the Service (Advanced) - Press Win + R, type services.msc, and press Enter. - Look for Broadcast DVR User Service (with a suffix). - Right-click > Properties > Set Startup type to Disabled. do both, but I don't recall that name popping up when I was looking for gamebar. uh don't try to strip game bar out it doesn't go well. also gamebar gives autohdr Its easy to point at ram but when everything is in ram its not always that easy. Bluescreens are the kernel's way of tell you something didn't line up as expected. Do not be surprised if it happens again after this as this is a process and there are layers to peel back do not get discouraged Fenrir.Jinxs said: » uh don't try to strip game bar out it doesn't go well. First thing I do to any install is to forcibly remove game bar. Code Get-AppxPackage -PackageTypeFilter Bundle -Name "*Microsoft.XboxGamingOverlay*" | Remove-AppxPackage K123 said: » I thought BSoD was always RAM related? In other news: Windows is getting rid of the Blue Screen of Death after 40 years Microsoft is saying hello to the Black Screen of Death error message instead. Black somehow seems more appropriate. Garuda.Chanti said: » K123 said: » I thought BSoD was always RAM related? Typically it's RAM related, but can also be memory controller on the CPU. Garuda.Chanti said: » Black somehow seems more appropriate. I've seen it thousands of times and always wondered why it wasn't red. I'd think that would be the obvious choice for errors /shrug Can also be drive related. Had an issue with BSOD after computer came back up from sleep, turns out it was SDD that neded replacing.
Time to set a budget and build a new one?
Just to clarify some things on BSOD. The screen is caused by your computer entering an irrecoverable state. That can be from basically any component in the computer or even any piece of software running on the computer. The BSOD is basically your OS/Kernel crashing. The error display indicates the cause of the crash and where the crash occurred. This doesn't mean that the place that it indicates the root cause though. A failing piece of hardware can cause a crash in another component leading you on a false trail.
As I mentioned software can also be to blame. Excel around 2010 had a beautiful bug where if you accidentally triple click to open excel the 3rd click (if you were slightly slow at clicking) would end up clicking on a cell before the app actually loaded causing a BSOD due to a null pointer. This was a 100% repro lol I normally use two Apps to help find out what BSOD i have and they are
WhoCrashed and BlueScreenView Never change anything until they make you. That's how that ***happens.
Works fine. Forced update. Everything goes to ***. Could be something hardware related at this point
Any of your ***beat to hell? reading your post, reminded me of similar issue i had with my intel build, root cause was the core performance boost or something like that i forgot the exact term, see if you can disable it in the bios
It's hardware that predates the major Intel defect issues, but still. If you exhaust other options, and have another CPU to try swapping in, I would try that.
I tend to be suspicious because when I had that sort of issue, it did end up being the CPU that was the problem (Ryzen 3700X). |
||
|
All FFXI content and images © 2002-2025 SQUARE ENIX CO., LTD. FINAL
FANTASY is a registered trademark of Square Enix Co., Ltd.
|
||