I apologize if this is posted in the wrong section So a brief explanation: Ive been getting random event id 41 kernel power errors and the dreaded nvlddmkm errors resulting in BSOD. this has been ongoing for a few months. It looks like its Nvidia related Things ive done: Uninstalled GPU via device manager and deleted uninstalled drivers Replaced Ram Cleaned Nvidia drivers using DDU Reseated GPU and Ram. Disabled fast startup (apparently can cause this error) Windows is updated to latest version. AMD chipset drivers upto date. Temperatures on both GPU/CPU well within TDP Ive enabled crashdumps and have a few files which ive viewed, from what i can see the crash dump files all point to Nvidia drivers being the issue. Ive had these errors, crashes with several different Nvidia drivers though. Im a little confused ive probably used around 7 different drivers versions and the errors persist Ive only recently turned on crash dumps otherwise i would have had a few months worth. Ive uploaded the crash dump files here : https://imgur.com/a/TZumOC7 Any help is greatly appreciated
Have you tried a spare GPU? Are you using XMP profile for memory? Ram errors can cause that BSOD and driver crashes. I know you replaced the RAM but insufficient voltages elsewhere can cause the ram to error.
Hi, I have not used a spare GPU. Im running ram @ XMP Profile 1 @ 3600mhz which its advertised as. I'm running the ram @ default voltages though? Would it worth increasing ram voltage? Im running a CPU overclock as well. but i ran at default speeds and still get the errors? Ive also updated Bios with every new version, around 3 i think and still get errors
Turn off XMP and see if it fixes it. XMP is an overclock. Otherwise you may run this program to see if there are any errors. https://www.overclock.net/threads/memory-testing-with-testmem5-tm5-with-custom-configs.1751608/ Link is in the first post. If no errors, you might try another PCIe slot.
Ok, ill turn off XMP and ill try the other tips thank you. The BSOD's are very random so it may take a few days
Are they not? They are mini-dump files from C:drive-Windows-mini-dump https://ibb.co/j5WQG0t https://www.computerhope.com/jargon/w/windump.htm The images are just screenshots from viewing the DMP files using a program called Bluescreen view
they are screenshots of output from a program that is known for being wrong about the faulting module, and even if it weren't, are otherwise useless to anyone who would be willing to assist you with the issue.
BlueScreenView Spoiler: Manual When you start BlueScreenView you’ll see that it will automatically identify where the minidumps are (if any) and the minidumps will be in the upper pane and the drivers involved in the crash will be listed in the lower pane. In the lower pane you’ll notice that some files will be highlighted in pink. Those files are the ones directly involved with the crash. All the other were loaded at that time, but Windows hasn’t identified them as part of the issue. If you double click on those files you’ll see more details: The same happens if you double click on the minidump itself in the upper pane: Please note the “Caused by” field that clearly states which drivers has caused the crash. Obviously we need to think that nay driver may fail not only because of a bug in its code, but it can fail because of a bug in the OS itself or in some other component’s code. This tool is very good in telling us which component has failed but this is the first step of troubleshooting. To be honest most of the times the identified culprit is the real one (a damaged file, a new driver, some test software installed). So we can restore a good copy of the file, or use a different version of the driver and the problem will disappear. In the menu “Options” you can configure what to see in the lower pane: “All Drivers”: see the list of all drivers loaded during the crash; “Only Drivers found in stack”: display all the drivers involved in the crash; “DumpChk Output”: Displays the output of DumpChk (that is the Microsoft tool used to troubleshoot the dumps; “Blue Screen in XP Style”: display the BSOD in a similar way it appeared when it happened: The last function we are going to see is the function to export the crash dump file list in html format. In the “View” menu, you can see the option to export to HTML so you can choose to export the whole list or just the ones you’ve highlighted. Author: Stefano Prenna
the nvidia exception bsods are of not much use to me as only nvidia has the symbols for their driver, the multimedia server bsod though occurs when binding a physical address and the argument suggests system memory corruption. Agent-A01 is probably spot on with the cause.
Ok thanks for the time. ive turned off XMP now, and im just running at 3600mhz on its own. ill see what happens. The only thing left is different GPU & PCIE Slot. Fresh OS install. Increase Ram voltage. Ill give a week or so. as its very random and i should know within the week i reckon. Appreciate all the help in the thread from everyone. You might see me back soon....