PC gone mad

[Jogi6]

2 months old PC:

 

MBO: Asus B85M-G
CPU: Intel Core i5-4670
RAM: 2x Corsair DDR3 1600MHz 4GB
GPU: Sapphire AMD Radeon R9 270X 2G GDDR5 DUAL-X WITH BOOST & OC      VERSION 1020MHz/1400MHz
HDD1: old one not sure of a specs, currently os drive
HDD2: 1TB SATAIII WD Caviar Black 7.200 rpm 64MB, WD1002FAEX
PSU: Corsair GS Series 600W

CPU COOLER: COLER MASTER Seidon 120V

OS: Windows 7 Ultimate 64

 

“…he needed to restore windows to last known working configuration every time after any BSOD.”

 

Two days ago my friend got a BSOD

==================================================
Dump File         : 010414-27222-01.dmp
Crash Time        : 4.1.2014. 15:13:15
Bug Check String  : ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug Check Code    : 0x000000be
Parameter 1       : fffff880`09ec3188
Parameter 2       : 80000002`0fcbd121
Parameter 3       : fffff800`00b9bf70
Parameter 4       : 00000000`0000000a
Caused By Driver  : USBSTOR.SYS
Caused By Address : USBSTOR.SYS+a188
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010414-27222-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 296.984
Dump File Time    : 4.1.2014. 16:53:39
==================================================

 

After this he could not turn on PC
I suspected memory or hdd, told him to pull out hdd and memory one by one and try turning on pc after each step. After some playing with that, crossing the ram slots and RAM his PC worked at all tests so I told him to put it all back together and turn on pc.
When he came online, I give him Memtest86 and told him to run it….. after 7hours memory was fine.

 

 

Then next day another bsod and pc is not working again.

==================================================
Dump File         : 010614-24008-01.dmp
Crash Time        : 6.1.2014. 1:00:46
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff880`083cde2f
Parameter 3       : fffff880`04ab5568
Parameter 4       : fffff880`04ab4dc0
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+1dff7
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : dxgmms1.sys+20e2f
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010614-24008-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 296.984
Dump File Time    : 6.1.2014. 1:12:04
==================================================

 

5 minutes later this one

 

 

Then after some testing of PC using AIDA64, prime95, and Temps were like 50°C on CPU and 72 GPU. He had another BSOD

==================================================
Dump File         : 010614-18267-01.dmp
Crash Time        : 6.1.2014. 2:06:04
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff6fc`c0087e00
Parameter 2       : 00000000`00000000
Parameter 3       : fffff800`02ea1156
Parameter 4       : 00000000`00000009
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+24e80
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\010614-18267-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 296.984
Dump File Time    : 6.1.2014. 3:04:33
==================================================

 

and PC was turning on and off, after he couldn’t enter bios, he unplugged both hdd’ and still couldn’t  enter bios. after some self turning off and on, pc started “working”
1st got to this screen and froze

 

strange blue lines are new

 

2nd windows loading and froze
After some freezing PC started working again but he needed to restore windows to last known working configuration every time after any bsod

So becose of strange blue lines on the picture above and dxgmms.sys driver error I told him to remove GPU and try CPU graphics
PC booted and immediately after we installed Intel graphics driver witch we downloaded of the MBO site we got another BSOD

 

 

20 minutes later another one

 

and another one

 

[AlwaysFSX]

Maybe you got so unlucky EVERYTHING has a problem?

[nokturrduk84]

lol title

[T.Vengeance]

Could be a motherboard issue.

[Sheldon]

Maybe try reinstalling the OS?

[Jogi6]

I think maybe it is MBO, and OS reinstal I will try tomorow, The problem with that is that I can't stay in this OS long enough so I can instal acrons disk director, resize HDD2 1TB into two particions so my friend can reinstai os. I am phisicly in another city and I can't come with bootable cd and do it myself.

 

Going to slleep now (06:00 hrs in the morning in Croatia) I will read you'r ideas later. and I need some good ones.

[Advent]

Memtest should be ran for 24 hours. The test only tested 37%, that leaves a lot of areas for errors to hide. You want to make sure 100% of the RAM has been tested.

Run Memtest for 24 hours with ALL RAM in. Making sure that they are in the proper slots. Remove the GPU and any other components beside the CPU. Disconnect all cables from the motherboard minus power and on/reset. 

If this passes then it is either Motherboard or CPU.

[xaeleep]

Well, I've always been told to run memtest uninterrupted for 8 passes, specifying the total time spent in memtest is rather pointless since it says nothing of how much actual testing has been performed. 

 

Just uploading a screenshot of the bluescreen isn't really that helpful I'm afraid, uploading the .dmp file in  C:\Windows\Minidump with driver verifier enabled would be a better idea. 

Now, I'd run this through answers.microsoft.com instead, since the people-knowing-what-they're-talking-about ratio is somewhat higher there. 

 

Best of luck. 

[Mooshi]

Pagefault does make me think either system drive or ram. Be glad you didn't get the lolidunno 124 error code.

[Guest Brunozipt]

have you tried turning it off and on again ?

[LogicalDrm]

Stucking into POST screen may be just random BIOS bug. New windows install will propably fix page file issues unless OS drive is dying.

[Jogi6]

Memtest should be ran for 24 hours. The test only tested 37%, that leaves a lot of areas for errors to hide. You want to make sure 100% of the RAM has been tested.

Run Memtest for 24 hours with ALL RAM in. Making sure that they are in the proper slots. Remove the GPU and any other components beside the CPU. Disconnect all cables from the motherboard minus power and on/reset. 

If this passes then it is either Motherboard or CPU.

 

Look at the picture in 7 hours it run thru 8 passes... 0 errors, so it ran thru all of RAM

[Jogi6]

Well, I've always been told to run memtest uninterrupted for 8 passes, specifying the total time spent in memtest is rather pointless since it says nothing of how much actual testing has been performed. 

 

Just uploading a screenshot of the bluescreen isn't really that helpful I'm afraid, uploading the .dmp file in  C:\Windows\Minidump with driver verifier enabled would be a better idea. 

Now, I'd run this through answers.microsoft.com instead, since the people-knowing-what-they're-talking-about ratio is somewhat higher there. 

 

Best of luck. 

 

again look at the picture 8 passes 0 errors

[Jogi6]

Stucking into POST screen may be just random BIOS bug. New windows install will propably fix page file issues unless OS drive is dying.

 

Maybe it is OS drive because it is old, I will try to make new particion on 1TB drive and get him to reinstall the OS…

[Jogi6]

so an update i posted an question on answers.microsoft.com (http://answers.microsoft.com/en-us/windows/forum/windows_7-system/pc-bsods-pc-gone-mad/45f514e5-3b49-4348-86d3-79ec9a73bd27?tm=1389018276302)

 

Minidumps.

https://skydrive.live.com/redir?resid=6A8FAC1451A347E5%21987

 

and sthing new:

 

could it be PSU. He has Corsair GS600 600W PSU, and the fan is not spinning. I was like that is normal psu is build this way fan only spins under load. Few minutes ago PC died again and he called me and sad when he tries to turn on PC fan on PSU spins blows hot air and that PSU is hot to the touch.

 

[Advent]

so an update i posted an question on answers.microsoft.com (http://answers.microsoft.com/en-us/windows/forum/windows_7-system/pc-bsods-pc-gone-mad/45f514e5-3b49-4348-86d3-79ec9a73bd27?tm=1389018276302)

 

Minidumps.

https://skydrive.live.com/redir?resid=6A8FAC1451A347E5%21987

 

and sthing new:

 

could it be PSU. He has Corsair GS600 600W PSU, and the fan is not spinning. I was like that is normal psu is build this way fan only spins under load. Few minutes ago PC died again and he called me and sad when he tries to turn on PC fan on PSU spins blows hot air and that PSU is hot to the touch.

 

Sounds like a PSU issue.

[Jogi6]

Sounds like a PSU issue.

 

Beside the hot PSU (and I don’t know how hot it is, he said it is warm/hot but not burning) do you have any other evidence to conclude PSU malfunction.

[Advent]

Beside the hot PSU (and I don’t know how hot it is, he said it is warm/hot but not burning) do you have any other evidence to conclude PSU malfunction.

Well lets look at what we have ruled out:

It isn't the hard drives because it won't work properly with them disconnected.

It isn't the RAM because you tested it.

It isn't the GPU because it BSOD'd with onboard Intel graphics.

 

So that leaves the following: Motherboard, CPU or PSU.

The only way to determine which of these is causing issues it to swap them out for other components. Generally power supplies should not be that warm to the touch. If it is more than warm that can indicate issues. The only way to test this would be to get a volt meter or a CPU tester or swap out the PSU for another one.

Once you rule out PSU it is either CPU or Motherboard at that point. Since the motherboard can test the RAM fine it isn't the RAM slots on the board. The same goes for the GPU slot on the board since it BSOD'd with onboard graphics. That leaves chipset or socket on the motherboard or the CPU itself.

Generally if you have a bad CPU your computer will not do ANYTHING. It won't post or if it does post if gives you beep codes indicating a bad CPU. So I doubt it is the CPU. It is either Motherboard or PSU in my opinion.

[JohnnyGrey]

so an update i posted an question on answers.microsoft.com (http://answers.microsoft.com/en-us/windows/forum/windows_7-system/pc-bsods-pc-gone-mad/45f514e5-3b49-4348-86d3-79ec9a73bd27?tm=1389018276302)

 

Minidumps.

https://skydrive.live.com/redir?resid=6A8FAC1451A347E5%21987

 

and sthing new:

 

could it be PSU. He has Corsair GS600 600W PSU, and the fan is not spinning. I was like that is normal psu is build this way fan only spins under load. Few minutes ago PC died again and he called me and sad when he tries to turn on PC fan on PSU spins blows hot air and that PSU is hot to the touch.

 

I've never seen a PSU actually be physically hot to the touch, but then again, people's perception of what classifies as "hot" varies. Judging from this, it would seem like a PSU. I would put in a new PSU to be safe. The wide variety of BSOD's leads me to believe it's also a major motherboard failure. I can't see the motherboard crashing and artifacting at POST being a "bug."

[FlakeyBanana]

Be careful if its a bad psu they often toast other components when they die,!!

[Jogi6]

yah it is weird of PSU to be hot, and I am leaning to MBO problem. In any case PC will be coming to me in a day or two… then I will just connect everything peace by peace to my rig starting with GPU, then RAM, CPU and than all that remains is MBO. But firs I will connect my PSU to his PC. And as his PC was bought in my city I will take care of RMA.