Jump to content

PC crashes after playing a game then red artifacts on screen during Windows loading screen

fuzedzn

In the last 2 days my pc has been crashing when i play games after about a minute or two. All inputs stop working and i can't even change something like Caps lock on my keyboard.

To reset the PC i have to use the reset button and then during boot i get small red artifacts (this screen). The artifacts then go and i never see them apart from on that screen..

 

I have tried uninstalling and re-installing drivers, I've made sure there is no unstable OC on the gpu and that temps are good.

 

My system is 

 

AMD FX 6100

Corsair H80i

XFX 7870 Core

AsRock 970 Extreme 3

8GB Corsair Vengence

Corsair CX600

 

Any ideas as to what it could be?

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

Roll back GPU drivers if you're running the latest.

run a GPU bench to see if it's your GPU. 

Run memtest to test ram, Prime 95 to test CPU

Motherboard - Gigabyte P67A-UD5 Processor - Intel Core i7-2600K RAM - G.Skill Ripjaws @1600 8GB Graphics Cards  - MSI and EVGA GeForce GTX 580 SLI PSU - Cooler Master Silent Pro 1,000w SSD - OCZ Vertex 3 120GB x2 HDD - WD Caviar Black 1TB Case - Corsair Obsidian 600D Audio - Asus Xonar DG


   Hail Sithis!

Link to comment
Share on other sites

Link to post
Share on other sites

Roll back GPU drivers if you're running the latest.

run a GPU bench to see if it's your GPU. 

Run memtest to test ram, Prime 95 to test CPU

I'll do them now.. Im using the 13.11 Beta driver and have been for a while.. Problem has only started in the last 1/2 days

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

any luck?

Motherboard - Gigabyte P67A-UD5 Processor - Intel Core i7-2600K RAM - G.Skill Ripjaws @1600 8GB Graphics Cards  - MSI and EVGA GeForce GTX 580 SLI PSU - Cooler Master Silent Pro 1,000w SSD - OCZ Vertex 3 120GB x2 HDD - WD Caviar Black 1TB Case - Corsair Obsidian 600D Audio - Asus Xonar DG


   Hail Sithis!

Link to comment
Share on other sites

Link to post
Share on other sites

any luck?

Still running Prime95 atm.. I want to leave it running for a few more minutes to make sure

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

any luck?

Ok, Ran Prime95.. No crashes.. Ran 3DMark, MSI Kombuster and Unigine Valley Benchmark still crashes. Also done Memtest and came out with no errors

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

Did is BSOD? If so you can post the minidump files and I can take a look at them.

 

Edit: The dump files are located under "%systemroot%\minidump"

You can copy them to a temporary folder and then zip them.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Did is BSOD? If so you can post the minidump files and I can take a look at them.

Didn't BSOD.. Just freezes the PC and nothing happens.. Not even BSOD.

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

Didn't BSOD.. Just freezes the PC and nothing happens.. Not even BSOD.

Can you still check the "%systemroot%\minidump" directory for any dump files, even if it didn't bring up a BSOD, sometimes they get created without the actual bluescreen showing up.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Can you still check the "%systemroot%\minidump" directory for any dump files, even if it didn't bring up a BSOD, sometimes they get created without the actual bluescreen showing up.

Ok here is the last dump file. http://www.mediafire.com/download/p7btypgs7v0nl2w/BSOD%20File%20FuzeDzn.zip

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

It is the AMD driver causing the issue

 

 

Go ahead and follow the guide here to clean uninstall the AMD drivers:http://support.amd.com/en-us/kb-articles/Pages/GPU57RemoveOldGraphicsDrivers.aspx

After that re-install the AMD video driver. 

 

Post back with what happens.

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Ion\Desktop\122913-36426-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response                         Time (ms)     LocationDeferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03216000 PsLoadedModuleList = 0xfffff800`034596d0Debug session time: Sat Dec 28 20:43:52.450 2013 (UTC - 8:00)System Uptime: 0 days 0:47:59.543Loading Kernel Symbols.............................................................................................................................................................................Loading User SymbolsLoading unloaded module list......*** WARNING: Unable to verify timestamp for atikmdag.sys*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck A0000001, {5, 0, 0, 0}Probably caused by : atikmdag.sys ( atikmdag+2779e )Followup: MachineOwner---------1: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Unknown bugcheck code (a0000001)Unknown bugcheck descriptionArguments:Arg1: 0000000000000005Arg2: 0000000000000000Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xA0000001PROCESS_NAME:  Valley.exeCURRENT_IRQL:  aANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64freLAST_CONTROL_TRANSFER:  from fffff8801107879e to fffff8000328bbc0STACK_TEXT:  fffff880`0cdee6f8 fffff880`1107879e : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckExfffff880`0cdee700 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x2779efffff880`0cdee708 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa0000001fffff880`0cdee710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5STACK_COMMAND:  kbFOLLOWUP_IP: atikmdag+2779efffff880`1107879e ??              ???SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  atikmdag+2779eFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: atikmdagIMAGE_NAME:  atikmdag.sysDEBUG_FLR_IMAGE_TIMESTAMP:  52702ec4FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+2779eBUCKET_ID:  X64_0xA0000001_atikmdag+2779eANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0xa0000001_atikmdag+2779eFAILURE_ID_HASH:  {1b9fab32-bba2-c274-b73d-699b456826df}Followup: MachineOwner---------1: kd> lmvm atikmdagstart             end                 module namefffff880`11051000 fffff880`11d3e000   atikmdag T (no symbols)               Loaded symbol image file: atikmdag.sys    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys    Image name: atikmdag.sys    Timestamp:        Tue Oct 29 14:55:16 2013 (52702EC4)    CheckSum:         00CA459E    ImageSize:        00CED000    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

It is the AMD driver causing the issue

 

 

Go ahead and follow the guide here to clean uninstall the AMD drivers:http://support.amd.com/en-us/kb-articles/Pages/GPU57RemoveOldGraphicsDrivers.aspx

After that re-install the AMD video driver. 

 

Post back with what happens.

Hmm, thats interesting because i did that before after the first crash but it still continued to do it.. I will however do another uninstall and install and post back when done

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Ion\Desktop\122913-36426-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Symbol Path validation summary **************Response                         Time (ms)     LocationDeferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532Machine Name:Kernel base = 0xfffff800`03216000 PsLoadedModuleList = 0xfffff800`034596d0Debug session time: Sat Dec 28 20:43:52.450 2013 (UTC - 8:00)System Uptime: 0 days 0:47:59.543Loading Kernel Symbols.............................................................................................................................................................................Loading User SymbolsLoading unloaded module list......*** WARNING: Unable to verify timestamp for atikmdag.sys*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck A0000001, {5, 0, 0, 0}Probably caused by : atikmdag.sys ( atikmdag+2779e )Followup: MachineOwner---------1: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Unknown bugcheck code (a0000001)Unknown bugcheck descriptionArguments:Arg1: 0000000000000005Arg2: 0000000000000000Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0xA0000001PROCESS_NAME:  Valley.exeCURRENT_IRQL:  aANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64freLAST_CONTROL_TRANSFER:  from fffff8801107879e to fffff8000328bbc0STACK_TEXT:  fffff880`0cdee6f8 fffff880`1107879e : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckExfffff880`0cdee700 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x2779efffff880`0cdee708 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa0000001fffff880`0cdee710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5STACK_COMMAND:  kbFOLLOWUP_IP: atikmdag+2779efffff880`1107879e ??              ???SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  atikmdag+2779eFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: atikmdagIMAGE_NAME:  atikmdag.sysDEBUG_FLR_IMAGE_TIMESTAMP:  52702ec4FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+2779eBUCKET_ID:  X64_0xA0000001_atikmdag+2779eANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:x64_0xa0000001_atikmdag+2779eFAILURE_ID_HASH:  {1b9fab32-bba2-c274-b73d-699b456826df}Followup: MachineOwner---------1: kd> lmvm atikmdagstart             end                 module namefffff880`11051000 fffff880`11d3e000   atikmdag T (no symbols)               Loaded symbol image file: atikmdag.sys    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys    Image name: atikmdag.sys    Timestamp:        Tue Oct 29 14:55:16 2013 (52702EC4)    CheckSum:         00CA459E    ImageSize:        00CED000    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4 

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

Hmm, thats interesting because i did that before after the first crash but it still continued to do it.. I will however do another uninstall and install and post back when done

What driver versions are you using? Don't use 12.11 or 12.12 as I personally had issues with those on my 7950.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

What driver versions are you using? Don't use 12.11 or 12.12 as I personally had issues with those on my 7950.

Using the 13.11 Beta driver.. Been using it for a while and had no problems.

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

Using the 13.11 Beta driver.. Been using it for a while and had no problems.

They're "beta" for a reason. It wouldn't hurt to try 12.10

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

They're "beta" for a reason. It wouldn't hurt to try 12.10

ahaha yeah i guess... Looking at the amd website.. The next stable driver is 13.12 (guess they have finished it now).. Should i try use that or find the 12.10 driver?

AMD Ryzen 7 5800X
32GB Corsair Vengeance DDR4
EVGA GTX 1080Ti FTW3

Link to comment
Share on other sites

Link to post
Share on other sites

ahaha yeah i guess... Looking at the amd website.. The next stable driver is 13.12 (guess they have finished it now).. Should i try use that or find the 12.10 driver?

I personally had issues with the 12.10 driver and my 7950. You could try it, and see what happens.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×