BSOD, dxgmms1.sys & cdd.dll crashes while under heavy load

[MarioIP]

I've had problems with BSODs and random reboots for MONTHS now and after spending over 100EUR and leaving it at the shop for almost 2 weeks it STILL has problems. I don't know if it's a RAM problem - I ran memtest for 4 passes with no errors - or if it's PSU that's defective but the lads at the shop said it was a temperature problem because my PC was dusty... yeah I don't think so at this point seeing as the problems are just the same as before.

I'll attach a txt file with 4 BSOD dumps exported from Blue Screen Viewer. If any other info is needed then just ask.

 

[axe0]

What PSU do you use?

I suggest you focus for now on the GPU, reinstall the current drivers and install a few older drivers if the reinstallation doesn't help.
I'd also suggest to stress test the GPU, ensure it isn't overclocked, proper seated and adequate cooled.

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
View attachment 386109

Diagnostic test

 GPU TEST

Run Furmark to test your GPU. Furmark tutorial

   Note

Run Furmark for around 30 minutes

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

0: kd> kC
 # Call Site
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiSystemServiceHandler
03 nt!RtlpExecuteHandlerForException
04 nt!RtlDispatchException
05 nt!KiDispatchException
06 nt!KiExceptionDispatch
07 nt!KiGeneralProtectionFault
08 dxgmms1![COLOR="red"]VIDMM_SEGMENT[/COLOR]::MarkResourcesForEviction
09 dxgmms1![COLOR="red"]VIDMM_GLOBAL[/COLOR]::NotifyAllocationEviction

4: kd> kC
 # Call Site
00 dxgmms1![COLOR="Red"]VIDMM_GLOBAL[/COLOR]::ReferenceAllocationForPreparation
01 dxgmms1![COLOR="red"]VIDMM_GLOBAL[/COLOR]::PrepareDmaBuffer
02 dxgmms1!VidSchiSubmitRenderCommand
03 dxgmms1!VidSchiSubmitQueueCommand
04 dxgmms1!VidSchiWorkerThread
05 nt!PspSystemThreadStartup
06 nt!KiStartSystemThread

 

[MarioIP]

Hey Axe

Thanks for the reply and assistance, I've done as you've said with Furmark and the drivers. I don't know if it's pertinent but I have actually done the clean install, in the way you instructed, several times before per the suggestion of Nvidia customer support and the problems have persisted over several months despite clean drivers, old and new.

If you wanted the Furmark temp log then you're gonna have to tell me where I can find it because I have no idea.

 

[axe0]

I prefer to know if Furmark did find any errors and what the max temperature was
I've seen only once Furmark giving an error indicating that the GPU was faulty, but in most occasions it is the temperature that causes the problem.

Have you tried seating the GPU into different slots?

 

[MarioIP]

Oh ok, Furmark didn't find any errors and the max temperature was 68 Celsius.

Regarding the seating, I'm veeeeeery scared of touching anything inside my PC, i've never built one myself before and I use it very frequently throughout the day on a daily basis so I want to avoid any prolonged period without it. If I were to reseat the GPU or anything like that then it would be my LAST resort. If you think that reseating is the best troubleshoot then I'll give it some thought but if you think there are other equally valid methods then just let me know what they are and I'll let you know if i've tried them.

 

[axe0]

Going inside shouldn't always be a last resort, now it is a next step as changing drivers in the current slot doesn't help.