Windows 10 Crashes With Graphics Drivers Installed On New Motherboard

E

El Xando

New member
Joined
Feb 4, 2018
Posts
4
Hi All,

Recently decided to miniaturize my PC by buying a new motherboard and case. Here are my specs:

CPU: i7 2600k
RAM: 16GB DDR3
GPU: Gigabyte GTX 970
Old Motherboard: Gigabyte GA-P67A-UD4-B3
New Motherboard: Intel DQ67EP

So I took all the old components out and put them in the new motherboard and freshly installed Windows 10. Shortly after Windows automatically found a graphics card driver and automatically set the resolution to 1920x1080, the PC crashed by the video freezing for a second, and then rebooting. No blue screen annoyingly. Now whenever a graphics card driver is in use with the GTX 970, the PC will at some point crash. Sometimes it's right after Windows does it's first spinning circle, sometimes it lasts a few minutes and I can even run something like UserBenchmark without it crashing. But eventually it does. I'm running in safe mode now and have even set the resolution back to 1920x1080 and it's completely stable. It also works fine if I take out the GPU and use the integrated graphics. Windows Event Viewer doesn't have any useful information other than the PC was shut down incorrectly. I've just put Ultimate Boot CD on a USB and both a CPU stress and Video Card Memory Stress test passed with no errors. Obviously the most likely candidate for the problem seems to be the new motherboard, but it's almost seeming like a graphics or power issue.

Is there any way to debug this crash? What's my next step?

Thanks.
 

Attachments

Age of the hardware is missed, seeing the eventlog it's quite important to know
Code: 
2018-02-04T12:26:53.336		Dump file creation failed due to error during dump creation.
2018-02-04T11:48:13.376		Dump file creation failed due to error during dump creation.
2018-02-04T09:45:38.367		Crash dump initialization failed!
2018-02-04T09:45:38.367		Dump file creation failed due to error during dump creation.
2018-02-03T18:28:59.149		Crash dump initialization failed!
2018-02-03T18:07:25.274		Dump file creation failed due to error during dump creation.
2018-02-03T18:04:13.384		Dump file creation failed due to error during dump creation.
2018-02-03T17:52:36.654		Dump file creation failed due to error during dump creation.
2018-02-03T17:51:32.838		Dump file creation failed due to error during dump creation.
 
axe0 said:
Age of the hardware is missed, seeing the eventlog it's quite important to know
Code: 
2018-02-04T12:26:53.336        Dump file creation failed due to error during dump creation.
2018-02-04T11:48:13.376        Dump file creation failed due to error during dump creation.
2018-02-04T09:45:38.367        Crash dump initialization failed!
2018-02-04T09:45:38.367        Dump file creation failed due to error during dump creation.
2018-02-03T18:28:59.149        Crash dump initialization failed!
2018-02-03T18:07:25.274        Dump file creation failed due to error during dump creation.
2018-02-03T18:04:13.384        Dump file creation failed due to error during dump creation.
2018-02-03T17:52:36.654        Dump file creation failed due to error during dump creation.
2018-02-03T17:51:32.838        Dump file creation failed due to error during dump creation.
Click to expand...

Ah, sorry.

CPU and PSU were bought Jan 2011 so just over 7 years.
RAM is about 3 years old
GPU is just over 2 years old
Motherboard must have been manufactured in 2011, but no idea how much use it's had since.

However I seem to have narrowed it down to definitely a faulty motherboard. My GPU works fine in other systems and the system still crashes when a different PSU is used.
 
Keep in mind, even though hardware has worked fine for ages, or has performed perfect under difficult circumstances, it can fail afterwards.
 
This error is reoccurring in the event logs "DCOM got error "1084" attempting to start the service ShellHWDetection." Doing some Googling I'm finding this can be malware. Have you run a Malwarebytes scan? If nothing is found I'd try to restore your system to a point before all this happened. Since the Fall Creator Update many are having trouble with System Restore
 
From what I see, I think it's more that many of those users don't know much about safely working with Windows without getting infected rather than that event is actually related to malware (though I don't know much about the Shell Hardware Detection service with the description "provides notifications for autoplay hardware events").

Of course, if you're worried you might be infected, visit https://www.sysnative.com/forums/security-arena/
 
After doing more research I find ShellHWDetection deals with media files on removable disks. This would explain why the graphic driver would be involved. Let's try to reinstall the driver a different way.

First go to the device manager click on display and then right click and uninstall the driver. Then right click and choose Update Driver. Then click on Browse my computer for driver software. Now click Let me pick from a list of available drivers on my computer. You should find the driver you downloaded. Click on it and then Next. This should properly install the driver. Hopefully they'll play nice again.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top