Sign in with
Sign up | Sign in
Your question
Solved

Can a bad motherboard ruin a CPU

Last response: in CPUs
Share
April 22, 2012 12:09:11 AM

So I built my own computer about a year and a half ago, and have had pretty consistent problems ever since. I would like to try to determine the cause of the problems before I start replacing parts.

My original build was an Asus motherboard, a 460 GTX MSI video card, a Phenom ii X2, with a 700W PS. After a few weeks with this set-up, I decided I wanted more powerful CPU, so I bought and installed an X4. This set-up worked fine for about a month before I experienced my first BSOD. I thought it was a bad program or driver that caused it, so I tried updating drivers and the BIOS and uninstalled programs, but nothing seemed to work. During all this, the computer would randomly BSOD, but was usable.

During this period, the computer started to act up another way. It would randomly partially shut-down, the screen would shut off, and all connected devices would turn off, but the case fans would stay on, and the power/hard drive activity LED's would turn on. I figured out part of the motherboard was getting very hot just before the shut-offs. So I put a fan in the case slot above the part that was overheating and turned it all the way up. After that, no more partial shut-downs.

After that fix, the computer slowly began to blue screen more often. At first it was just during heavy usage, games mostly, then it started happening during regular usage and even during start-up. It got to a point where it would BSOD in safe mode.

I then read somewhere that a bad CPU can cause BSODs. I still had my old X2, so I decided to put it back in, no more BSOD. Great right? No. It's been about a month since I re-installed the X2, and the BSOD started up again. Right now it's only during heavy usage, but I expect it to get worse.

Any help trying to diagnoses the problem would be appreciated.
a c 113 à CPUs
a c 234 V Motherboard
April 22, 2012 12:17:43 AM

A flaky PSU can also cause BSODs.
m
0
l
a b à CPUs
a b V Motherboard
April 22, 2012 5:04:18 PM

A complete list of components would be helpful. An inexpensive or underpowered psu, as GhislainG mentioned, might be the cause. So could memory or timings. Do you overclock? Anything?
m
0
l
Related resources
Can't find your answer ? Ask !

Best solution

a c 116 à CPUs
a b V Motherboard
April 22, 2012 5:48:48 PM

i suggest looking at timings, temps and voltages... looking at the event logs may also help...
try operating the pc with 1 stick of ram then 2. if the ram is mixed timings and latencies then that could well be the route cause of the problem and can cause the cpu's mmu to go bad causing the cpu to fail.
but we wont know for sure until you start testing .....
to read your bsod files get bluescreen view. http://www.nirsoft.net/utils/blue_screen_view.html the download link is near the bottom of the page.
Share
April 22, 2012 6:06:16 PM

I would be inclined to suspect the RAM timings or the power supply, like suteck and GhislainG said. I personally have experience with low amperage on the 3.3volt rails causing freeze-ups and all sorts of trouble. Is there any way you can reliably duplicate the problem? For example, does your computer always BSOD when running prime95, or some other stress test software? That would make it easier to diagnose what is wrong. My recommendation would be to restore any overclocking/RAM timings to their defaults (assuming you changed them). I would also run memtest to see if you get any errors there. I don't think it's the CPU, since it BSOD's on both the x2 and the x4. However, the x4 uses a lot more power, which could account for the increase in BSOD's if your PSU is to blame. It is weird though that it didn't BSOD for a month after you installed the x2... Also, a more complete list of specs (including temps, if you can) would be helpful.
m
0
l
a b à CPUs
a b V Motherboard
April 22, 2012 6:11:25 PM

And what is the BSD code(s) that you get? xo:101 124 check it the next time it does it. It will be the last set of digits after the trillion lines of 00000000X0 an so forth
m
0
l
April 24, 2012 9:44:31 PM

Hey everybody, thanks for the tips. I don't do any overclocking. This was my first build and I got preoccupied trying to solve the blue screens. I've done memtests in the past, and nothing came up. I'll try removing memory sticks and see if that helps. The problem doesn't seem to be reliably reproducible, I got two in one night and then nothing since then (~3 days) with heavy game use. And I can't find where the BSD code is.

Here is a more complete list of components.

-Western Digital Caviar Black 1TB 7200 RPM
-G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
-G.SKILL Ripjaws Series 4GB 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) (2-Sticks)
-Rosewill RV2-700 700W ATX12V v2.3 / EPS12V SLI Ready Power Supply
-ASUS M4A87TD EVO AM3 AMD 870 SATA 6Gb/s USB 3.0 ATX AMD Motherboard
-MSI N460GTX Cyclone GeForce GTX 460 (Fermi) 768MB 192-bit GDDR5
-AMD Phenom II X4 965 Black Edition Deneb 3.4GHz
-AMD Phenom II X2 555 Black Edition Callisto 3.2GHz


-First BSOD using X2, second BSOD did not leave memory dump.

Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x0000001e
Parameter1: 00000000`00000000
Parameter2: 00000000`00000000
Parameter3: 00000000`00000000
Parameter4: 00000000`00000000
Caused By Address: ntoskrnl.exe+7cc50
Crash Address: ntoskrnl.exe+7cc50

-BSODs while using the X4. These are the recurring blue screens, each of them happened multiple times (Same Bug Check String/Code).

Bug Check String: SYSTEM_SERVICE_EXCEPTION
Bug Check Code: 0x0000003b
Parameter1: 00000000`c0000005
Parameter2: fffff800`027abba1
Parameter3: fffff880`064a1f30
Parameter4: 00000000`00000000
Caused By Address: hal.dll+4a56
Crash Address: ntoskrnl.exe+7cc40

Bug Check String: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x1000007e
Parameter1: ffffffff`c0000005
Parameter2: fffff880`04fc4599
Parameter3: fffff880`033af9e8
Parameter4: fffff880`033af240
Caused By Address: Wdf01000.sys+406fb
Crash Address: xusb21.sys+a599

Bug Check String: KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code: 0x0000001e
Parameter1: 00000000`00000000
Parameter2: 00000000`00000000
Parameter3: 00000000`00000000
Parameter4: 00000000`00000000
Caused By Address: ntoskrnl.exe+7cc10
Crash Address: ntoskrnl.exe+7cc10

Bug Check String: NTFS_FILE_SYSTEM
Bug Check Code: 0x00000024
Parameter1: 00000000`001904fb
Parameter2: fffff880`0b203e58
Parameter3: fffff880`0b2036b0
Parameter4: fffff800`030c9b65
Caused By Address: Ntfs.sys+5a88
Crash Address: ntoskrnl.exe+7cc40
m
0
l
a b à CPUs
a b V Motherboard
April 25, 2012 2:14:02 AM

Found this in the windows section - You are consistently receiving a KMODE_EXCEPTION_NOT_HANDLED Stop Error, but a problematic third party driver was not named as causing the crash.

There are quite a few older drivers on the system so, at this point, you may want to consider turning on the Driver Verifier against all non-Microsoft drivers to stress test them and try to flush out a problematic driver:

Start > type verifier in the Search programs and files box and press "Enter" > Create standard settings > Next > Select driver names from a list > then select all non-Microsoft drivers > Finish

Restart the computer.

Continue to use the computer normally but if you experience any BSODs make available the minidump files.

If after enabling the Driver Verifier and restarting the computer you receive a BSOD on startup and cannot start Windows, restart the computer in "Safe Mode" and do the following:

Start > type verifier in the Search programs and files box and press "Enter" > Delete existing settings > Finish

Restart the computer, log into Normal Mode, and make available any resulting minidump file.

Give it a try and see if it helps.

I still think it's probably faulty ram. Can you borrow some from a friend and give it a try?
m
0
l
May 2, 2012 12:05:34 AM

Best answer selected by Bigs_07.
m
0
l
!