Sign in with
Sign up | Sign in
Your question

Random crashes on newly built system

Last response: in Systems
Share
July 23, 2012 6:46:34 PM

Hello,

I built a new system recently and after installing windows 7, and doing my usual newly built computer routine, i experienced a freeze. I restarted, and again, experienced a freeze. The freezes occur anywhere from 1 minute-1 hour after booting. I've run windows memory diagnostic, as well as memtest+ and resulted in nothing being wrong. I've also formatted and reinstalled windows, just to ensure there wasnt a bad installation, and i still experience the freezes.

I'm curious what the most likely candidate to be causing this issue is. It shouldn't be the RAM (because it passed multiple testings), the graphics card i'm using was being used on a previous system of mine, and was working just fine. Leaves me with mobo, cpu, or PSU? I have a Wifi card as well, but i dont think it would be causing this problem. Ideas?


System build :
ASRock 970DE3 motherboard
AMD FX4100 am3+ 3.6ghz quad core
Nvidia GTX 460SE (not new, but was taken right out of a perfectly running computer)
8GB of PNY DDR3 1333 Ram
WDC 1TB HDD
630w Rosewill PSU
July 23, 2012 6:56:11 PM

Did you do a scan of the HDD to ensure there isn't any bad or weak sectors?
a b B Homebuilt system
July 23, 2012 6:58:20 PM

Are these freezes resulting in blue screens ? If not, check your cooling first.
Related resources
July 23, 2012 7:01:22 PM

kurjack said:
Did you do a scan of the HDD to ensure there isn't any bad or weak sectors?


I have not, but i will right now and report back with results.


Maxx_Power said:
Are these freezes resulting in blue screens ? If not, check your cooling first.


No blue screens. I've idled in the bios for over an hour to watch temperatures, and nothing came close to hot. I'll go download a constant reader and keep an eye on them while the computer is fully booted.
a b B Homebuilt system
July 23, 2012 7:08:20 PM

moonunit93 said:


No blue screens. I've idled in the bios for over an hour to watch temperatures, and nothing came close to hot. I'll go download a constant reader and keep an eye on them while the computer is fully booted.


This tells me that once the memory is loaded, something goes wrong. If the HDD's came out okay, I would suspect the memory or memory controller. Since you did Memtest already, how many passes did you run ?

I have seen AMD systems that can pass 20+ passes of Memtest but can't handle a load on both memory controller and CPU cores.

Did you overclock ?
a b B Homebuilt system
July 23, 2012 7:19:01 PM

Is the freezing correlated with some kind of activity on the computer ? Are you playing games, transferring files, etc ?
July 23, 2012 7:20:04 PM

Run the intel burn test.
a b B Homebuilt system
July 23, 2012 7:24:12 PM

Get UBCD (absolutely free from the net), boot from that and try the CPU stress tests like Prime 95. I suspect you already have UBCD, or Hiren since you did Memtest, unless you got the standalone ISO.
July 23, 2012 7:33:17 PM

what are the specs of your other computer? I would start trying to swap out components.
July 23, 2012 7:33:43 PM

I'm a bit new to using memtest, so i'm not sure how many "passes" it made, but i can tell you that it ran for 8 hours, found no errors.

The test on the HDD is currently running, and at the current rate is going to take 10-15 minutes to finish.

The freezes happen randomly. They happen anywhere from 1 minute - 1 hour after booting, and have occurred from me clicking the start bubble, installing drivers, doing windows updates, browsing the web, absolutely anything really.

After the computer boots back up i will try UBCD and see what we get there.
July 23, 2012 7:36:42 PM

DarkOutlaw said:
what are the specs of your other computer? I would start trying to swap out components.



After completing the HDD testing, and seeing what i get for results with UBCD, i'll start testing alternate parts. Everything from my other system will work in this one as well. And if i can exhaust all parts, then, i guess i could conclude it's a faulty mobo.
a b B Homebuilt system
July 23, 2012 7:39:00 PM

moonunit93 said:
I'm a bit new to using memtest, so i'm not sure how many "passes" it made, but i can tell you that it ran for 8 hours, found no errors.

The test on the HDD is currently running, and at the current rate is going to take 10-15 minutes to finish.

The freezes happen randomly. They happen anywhere from 1 minute - 1 hour after booting, and have occurred from me clicking the start bubble, installing drivers, doing windows updates, browsing the web, absolutely anything really.

After the computer boots back up i will try UBCD and see what we get there.


Let us know after.

Mean while, memtest passes depends on how much ram, and how fast that ram is accessed. Usually 10 passes without errors is sufficient. As for Prime 95, use the Blend setting, or you can use the Intel CPU Burn, whichever you fancy under UBCD.
a b B Homebuilt system
July 23, 2012 7:40:45 PM

OHHH, and since this is a new build, check the fan headers and heatsink placement inside the computer.

I know you said you saw the temperatures from the BIOS, BUT just to be sure, get a visual on the CPU FAN and try lightly jiggling the CPU heatsink to make sure the fan is indeed running while the computer is on, and the heatsink is securely attached with the locking mechanism engaged if using stock heatsink.
July 23, 2012 7:51:46 PM

This HDD scan is taking quite a while...

The fan is definitely seated securely, no give at all.

Some other information that could be interesting:

1. At one point while the computer was running nicely, for about 40 minutes or so, i went to listen to music and plugged headphones into the front panel audio jack. It caused an awful screeching/beeping sound effect, and if i move my mouse around the beeping/screeching will change pitches. This isn't an issue on the back panel audio though.

2. The crash/freeze that occurs when it does happen, is pretty abnormal from my experience. It doesn't just immediately freeze and i have to reboot. I usually lose mouse control (cursor dissapears sometimes, other times it'll sit still). After loosing mouse control i can still use my keyboard fully, and even receive full response on the monitor by opening new windows, or continuing to watch download bars increase. Though, within 1 or 2 minutes of losing mouse control the computer then fully locks up, no response from keyboard or mouse, no on screen movement.

(i've tested different mouses/keyboards so the issue isn't related to those specifically i dont believe)

update 4:25: HDD scan is 50% complete.....
a b B Homebuilt system
July 23, 2012 8:29:16 PM

moonunit93 said:
This HDD scan is taking quite a while...

The fan is definitely seated securely, no give at all.

Some other information that could be interesting:

1. At one point while the computer was running nicely, for about 40 minutes or so, i went to listen to music and plugged headphones into the front panel audio jack. It caused an awful screeching/beeping sound effect, and if i move my mouse around the beeping/screeching will change pitches. This isn't an issue on the back panel audio though.

2. The crash/freeze that occurs when it does happen, is pretty abnormal from my experience. It doesn't just immediately freeze and i have to reboot. I usually lose mouse control (cursor dissapears sometimes, other times it'll sit still). After loosing mouse control i can still use my keyboard fully, and even receive full response on the monitor by opening new windows, or continuing to watch download bars increase. Though, within 1 or 2 minutes of losing mouse control the computer then fully locks up, no response from keyboard or mouse, no on screen movement.

(i've tested different mouses/keyboards so the issue isn't related to those specifically i dont believe)

update 4:25: HDD scan is 50% complete.....


The audio thing shouldn't cause crashes. What you are seeing is crappy quality front panel connectors that are poorly shielded, so your digital transmissions on the USB are being picked up and intermodulated into audible sound on the audio lines. This is just interference, but shouldn't cause crashes (or I haven't seen a case of this causing crashes).

The 2nd point is interesting, to track this down, go to Windows' event viewer and see if you have a sequence of events under system just prior to the last crash logged in windows. That may have telltale signs of what is the first component to go down. Dig around in there, the entries are chronological.
July 23, 2012 8:41:10 PM

Maxx_Power said:
The 2nd point is interesting, to track this down, go to Windows' event viewer and see if you have a sequence of events under system just prior to the last crash logged in windows. That may have telltale signs of what is the first component to go down. Dig around in there, the entries are chronological.


I will dig around in windows' event viewer ASAP when the system finishes scanning the HDD(taking forever to scan the 238,424,801 free clusters). I'll postpone doing anything with UBCD until I've dug around in event viewer.
July 23, 2012 10:33:30 PM

I dont think event viewer is telling me anything of great importance. Every now and then i find a "critical" log, which states that "the system has rebooted without cleanly shutting down first...". A few logs before a critical log i find an "error" log which will state "the previous system shutdown at x:xx:xx PM on 7/23/2012 was unexpected.". The logs that occur before the "error" log, are never repeating with other logs before other error logs, thus it doesn't make me terribly suspicious about the logs before "error" occurs. The only thing that seems to be constant are the logs labeled as "warning". Every now and then a few "warning" logs occur, which are ALWAYS one of the following

1. "name resolution for the name isatap.oxfordnetworks.net timed out after none of the configured DNS servers responded."
2. "WLAN autoConfig service has successfully stopped.

I'll be gone for a few hours but i'll check back in later tonight. Also, Intel Burn test is currently running, i will post the results log from that when i'm back.
a b B Homebuilt system
July 23, 2012 11:00:17 PM

moonunit93 said:
I dont think event viewer is telling me anything of great importance. Every now and then i find a "critical" log, which states that "the system has rebooted without cleanly shutting down first...". A few logs before a critical log i find an "error" log which will state "the previous system shutdown at x:xx:xx PM on 7/23/2012 was unexpected.". The logs that occur before the "error" log, are never repeating with other logs before other error logs, thus it doesn't make me terribly suspicious about the logs before "error" occurs. The only thing that seems to be constant are the logs labeled as "warning". Every now and then a few "warning" logs occur, which are ALWAYS one of the following

1. "name resolution for the name isatap.oxfordnetworks.net timed out after none of the configured DNS servers responded."
2. "WLAN autoConfig service has successfully stopped.

I'll be gone for a few hours but i'll check back in later tonight. Also, Intel Burn test is currently running, i will post the results log from that when i'm back.


Keep us posted and good luck.
July 24, 2012 3:06:30 AM

So, intel burn test results are in, with success.

----------------------------
IntelBurnTest v2.54
Created by AgentGOD
----------------------------

Processor: AMD FX(tm)-4100 Quad-Core Processor
Clock Speed: 3.61 GHz
Active Physical Cores: 4
Total System Memory: 4079 MB

Stress Level: High (2048 MB)
Testing started on 7/23/2012 6:39:58 PM
Time (s) Speed (GFlops) Result
[18:43:39] 185.841 14.2194 3.918304e-002
[18:47:15] 184.184 14.3473 3.918304e-002
[18:50:53] 186.298 14.1845 3.918304e-002
[18:54:33] 186.964 14.1340 3.918304e-002
[18:58:25] 188.906 13.9887 3.918304e-002
[19:02:15] 183.433 14.4060 3.918304e-002
[19:06:15] 189.488 13.9457 3.918304e-002
[19:10:09] 190.088 13.9017 3.918304e-002
[19:13:54] 190.948 13.8391 3.918304e-002
[23:03:48] 190.618 13.8631 3.918304e-002
Testing ended on 7/23/2012 11:03:48 PM
Test Result: Success.
----------------------------




I would like to note, however, the computer ran for 5 hours or so since i've left, put it self to sleep, and is now up and running again and it hasn't crashed. Before doing this CPU testing, i pulled out 1 of the sticks of ram and have been just using one stick.

so even though memtest and windows memory diagnostic said i was in the clear, perhaps i do have a bad stick of ram? I'll continue to try and use the computer a lot (gaming if it'll let me) tomorrow and see if we can make it crash. If it doesn't crash, i'd feel comfortable blaming the stick of ram that i took out as being the culprit.
a b B Homebuilt system
July 24, 2012 2:36:29 PM

moonunit93 said:
So, intel burn test results are in, with success.

----------------------------
IntelBurnTest v2.54
Created by AgentGOD
----------------------------

Processor: AMD FX(tm)-4100 Quad-Core Processor
Clock Speed: 3.61 GHz
Active Physical Cores: 4
Total System Memory: 4079 MB

Stress Level: High (2048 MB)
Testing started on 7/23/2012 6:39:58 PM
Time (s) Speed (GFlops) Result
[18:43:39] 185.841 14.2194 3.918304e-002
[18:47:15] 184.184 14.3473 3.918304e-002
[18:50:53] 186.298 14.1845 3.918304e-002
[18:54:33] 186.964 14.1340 3.918304e-002
[18:58:25] 188.906 13.9887 3.918304e-002
[19:02:15] 183.433 14.4060 3.918304e-002
[19:06:15] 189.488 13.9457 3.918304e-002
[19:10:09] 190.088 13.9017 3.918304e-002
[19:13:54] 190.948 13.8391 3.918304e-002
[23:03:48] 190.618 13.8631 3.918304e-002
Testing ended on 7/23/2012 11:03:48 PM
Test Result: Success.
----------------------------




I would like to note, however, the computer ran for 5 hours or so since i've left, put it self to sleep, and is now up and running again and it hasn't crashed. Before doing this CPU testing, i pulled out 1 of the sticks of ram and have been just using one stick.

so even though memtest and windows memory diagnostic said i was in the clear, perhaps i do have a bad stick of ram? I'll continue to try and use the computer a lot (gaming if it'll let me) tomorrow and see if we can make it crash. If it doesn't crash, i'd feel comfortable blaming the stick of ram that i took out as being the culprit.


This is sounding like a possibility. However, if you have more than 2 slots of ram possible on your board, try the other 2 slots first.

Then if that doesn't solve the issue, check the CPU voltages in the BIOS or in Windows using CPU-Z, or HWmonitor. Make sure the CPU voltages are correct. In particular, you want to know the CPU-NB voltages since AMD uses a split plane to power the memory controller and communication IO of the CPU with a different voltage than the cores. If this value is too low, your memory controller can have issues that looks a lot like memory errors.

Lastly, check your memory voltages. The DDR3 voltages are usually 1.5 Volts. Since your ram is running at 1333mhz, your voltage for the DDR3 memory should be at 1.5 Volts. There ARE DDR3 memory voltages at 1.25, 1.35, 1.65, etc. So double check this too.

July 24, 2012 7:31:40 PM

Last night, quite shortly after posting that the computer had been running for 5 hours, it crashed :( 

I've experienced crashes with every combination of memory. both sticks in slot, both sticks in the other two slots, 1 stick in, the other 1 stick in. So, i'm now running with a stick of RAM from my other system, which i know is good.

This is what HWmonitor is showing for data:

CPUID HWMonitor Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

HWMonitor version 1.1.9.0

Monitoring
-------------------------------------------------------------------------

Mainboard Model 970DE3/U3S3 (0x00000299 - 0x234422B0)

LPCIO
-------------------------------------------------------------------------

LPCIO Vendor Nuvoton
LPCIO Model NCT6776
LPCIO Vendor ID 0x5CA3
LPCIO Chip ID 0xC3
LPCIO Revision ID 0x33
Config Mode I/O address 0x2E
Config Mode LDN 0xB
Config Mode registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 FF FF 00 FF FF FF FF 0B FF FF FF FF FF FF FF FF
10 FF FF FF FF FF FF FF FF FF FF F8 8E 80 00 FF FF
20 C3 33 FF 00 58 00 00 88 00 FF 60 08 81 00 00 01
30 81 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
60 02 90 02 00 FF FF FF FF FF FF FF FF FF FF FF FF
70 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Register space LPC, base address = 0x0290


Hardware Monitors
-------------------------------------------------------------------------

Hardware monitor Nuvoton NCT6776
Voltage 0 0.95 Volts [0x77] (CPU VCORE)
Voltage 1 1.89 Volts [0xEC] (VIN1)
Voltage 2 3.39 Volts [0xD4] (AVCC)
Voltage 3 3.39 Volts [0xD4] (3VCC)
Voltage 4 0.12 Volts [0xF] (VIN4)
Voltage 5 1.70 Volts [0xD5] (VIN5)
Voltage 6 0.11 Volts [0xE] (VIN6)
Temperature 0 29°C (84°F) [0x1D] (SYSTIN)
Temperature 1 27°C (80°F) [0x36] (CPUTIN)
Temperature 2 119°C (245°F) [0xED] (AUXTIN)
Temperature 3 40°C (104°F) [0x28] (TMPIN3)
Fan 0 1201 RPM [0x4B1] (SYSFANIN)
Fan 1 3497 RPM [0xDA9] (CPUFANIN)
Fan 2 967 RPM [0x3C7] (AUXFANIN0)
Register space LPC, base address = 0x0290

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 04 FF 04 FF 00 FF FF FF FF FF FF FF FF FF FF FF
10 04 FF 00 00 00 00 FF FF 40 00 00 00 00 00 00 00
20 77 EC D5 D4 07 D5 07 1D FF FF FF DA 00 00 00 00
30 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF FF
40 03 FE 7F FF FF 00 3F FF 2D FF FF FF 08 05 00 A3
50 FF FF FF FF FF FF FF FF C1 FF FF FF FF 00 00 FF
60 00 FF FF FF FF 01 00 FF FF FF FF FF FF FF FF FF
70 00 0A 00 1D 80 1B 00 7F 80 FF FF FF FF FF FF FF
80 FF 03 1F 0F FF 3C 3C 3C 00 00 00 00 00 00 00 00
90 0A 00 00 00 00 0A 0A 0A 0A AA EF 80 FF 40 46 C4
A0 0E 01 00 00 FF 00 00 FF 00 00 80 66 66 06 00 01
B0 00 00 00 00 00 00 29 00 1C 00 00 01 3C 00 C4 FF
C0 01 00 00 00 00 00 00 00 00 10 02 FF FF FF FF FF
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Hardware monitor NVIDIA NVAPI
Voltage 0 0.88 Volts [0x36B] (VIN0)
Temperature 0 31°C (87°F) [0x1F] (TMPIN0)
Fan 0 1710 RPM [0x6AE] (FANIN0)
Fan PWM 0 40 pc [0x28] (FANPWMIN0)


Processors
-------------------------------------------------------------------------

Number of processors 1
Number of threads 4

APICs
-------------------------------------------------------------------------

Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1
-- Core 2
-- Thread 0 2
-- Core 3
-- Thread 0 3

Processors Information
-------------------------------------------------------------------------

Processor 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD FX-4100
Codename Zambezi
Specification AMD FX(tm)-4100 Quad-Core Processor
Package Socket AM3+ (942)
CPUID F.1.2
Extended CPUID 15.1
Core Stepping OR-B2
Technology 32 nm
TDP Limit 95 Watts
Core Speed 1402.9 MHz
Multiplier x FSB 7.0 x 200.4 MHz
Stock frequency 3600 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP
L1 Data cache 4 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 2 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
FID/VID Control yes
Min FID 7.0x
# of P-States 7
P-State FID 0x16 - VID 0x0B - IDD 21 (19.00x - 1.412 V)
P-State FID 0x15 - VID 0x0E - IDD 21 (18.50x - 1.375 V)
P-State FID 0x14 - VID 0x15 - IDD 15 (18.00x - 1.287 V)
P-State FID 0x11 - VID 0x1B - IDD 13 (16.50x - 1.212 V)
P-State FID 0x9 - VID 0x22 - IDD 10 (12.50x - 1.125 V)
P-State FID 0x1 - VID 0x2C - IDD 7 (8.50x - 1.000 V)
P-State FID 0x10C - VID 0x30 - IDD 6 (7.00x - 0.950 V)

PStateReg 0x800001D5-0x00001616
PStateReg 0x800001D5-0x00001C15
PStateReg 0x8000019A-0x00002A14
PStateReg 0x80000182-0x00003611
PStateReg 0x80000163-0x00004409
PStateReg 0x80000143-0x00005801
PStateReg 0x80000139-0x0000604C
PStateReg 0x00000000-0x00000000

Package Type 0x1
Model 00
String 1 0x0
String 2 0x0
Page 0x0
CmpCap 3
Base TDP 11 Watts
Boosted P-States 2
Max non-turbo ratio 18.00x
Max turbo ratio 19.00x
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
Attached device PCI device at bus 0, device 24, function 5




If I experience a crash with this stick of RAM (which i know isn't a bad stick), i'll just go ahead and RMA the motherboard and cross my fingers that it was the issue. Else, if i cant get it to crash, i'll RMA the RAM.
a b B Homebuilt system
July 24, 2012 7:36:09 PM

moonunit93 said:
Last night, quite shortly after posting that the computer had been running for 5 hours, it crashed :( 

I've experienced crashes with every combination of memory. both sticks in slot, both sticks in the other two slots, 1 stick in, the other 1 stick in. So, i'm now running with a stick of RAM from my other system, which i know is good.

This is what HWmonitor is showing for data:

CPUID HWMonitor Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

HWMonitor version 1.1.9.0

Monitoring
-------------------------------------------------------------------------

Mainboard Model 970DE3/U3S3 (0x00000299 - 0x234422B0)

LPCIO
-------------------------------------------------------------------------

LPCIO Vendor Nuvoton
LPCIO Model NCT6776
LPCIO Vendor ID 0x5CA3
LPCIO Chip ID 0xC3
LPCIO Revision ID 0x33
Config Mode I/O address 0x2E
Config Mode LDN 0xB
Config Mode registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 FF FF 00 FF FF FF FF 0B FF FF FF FF FF FF FF FF
10 FF FF FF FF FF FF FF FF FF FF F8 8E 80 00 FF FF
20 C3 33 FF 00 58 00 00 88 00 FF 60 08 81 00 00 01
30 81 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
50 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
60 02 90 02 00 FF FF FF FF FF FF FF FF FF FF FF FF
70 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Register space LPC, base address = 0x0290


Hardware Monitors
-------------------------------------------------------------------------

Hardware monitor Nuvoton NCT6776
Voltage 0 0.95 Volts [0x77] (CPU VCORE)
Voltage 1 1.89 Volts [0xEC] (VIN1)
Voltage 2 3.39 Volts [0xD4] (AVCC)
Voltage 3 3.39 Volts [0xD4] (3VCC)
Voltage 4 0.12 Volts [0xF] (VIN4)
Voltage 5 1.70 Volts [0xD5] (VIN5)
Voltage 6 0.11 Volts [0xE] (VIN6)
Temperature 0 29°C (84°F) [0x1D] (SYSTIN)
Temperature 1 27°C (80°F) [0x36] (CPUTIN)
Temperature 2 119°C (245°F) [0xED] (AUXTIN)
Temperature 3 40°C (104°F) [0x28] (TMPIN3)
Fan 0 1201 RPM [0x4B1] (SYSFANIN)
Fan 1 3497 RPM [0xDA9] (CPUFANIN)
Fan 2 967 RPM [0x3C7] (AUXFANIN0)
Register space LPC, base address = 0x0290

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 04 FF 04 FF 00 FF FF FF FF FF FF FF FF FF FF FF
10 04 FF 00 00 00 00 FF FF 40 00 00 00 00 00 00 00
20 77 EC D5 D4 07 D5 07 1D FF FF FF DA 00 00 00 00
30 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF FF
40 03 FE 7F FF FF 00 3F FF 2D FF FF FF 08 05 00 A3
50 FF FF FF FF FF FF FF FF C1 FF FF FF FF 00 00 FF
60 00 FF FF FF FF 01 00 FF FF FF FF FF FF FF FF FF
70 00 0A 00 1D 80 1B 00 7F 80 FF FF FF FF FF FF FF
80 FF 03 1F 0F FF 3C 3C 3C 00 00 00 00 00 00 00 00
90 0A 00 00 00 00 0A 0A 0A 0A AA EF 80 FF 40 46 C4
A0 0E 01 00 00 FF 00 00 FF 00 00 80 66 66 06 00 01
B0 00 00 00 00 00 00 29 00 1C 00 00 01 3C 00 C4 FF
C0 01 00 00 00 00 00 00 00 00 10 02 FF FF FF FF FF
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Hardware monitor NVIDIA NVAPI
Voltage 0 0.88 Volts [0x36B] (VIN0)
Temperature 0 31°C (87°F) [0x1F] (TMPIN0)
Fan 0 1710 RPM [0x6AE] (FANIN0)
Fan PWM 0 40 pc [0x28] (FANPWMIN0)


Processors
-------------------------------------------------------------------------

Number of processors 1
Number of threads 4

APICs
-------------------------------------------------------------------------

Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1
-- Core 2
-- Thread 0 2
-- Core 3
-- Thread 0 3

Processors Information
-------------------------------------------------------------------------

Processor 1 ID = 0
Number of cores 4 (max 4)
Number of threads 4 (max 4)
Name AMD FX-4100
Codename Zambezi
Specification AMD FX(tm)-4100 Quad-Core Processor
Package Socket AM3+ (942)
CPUID F.1.2
Extended CPUID 15.1
Core Stepping OR-B2
Technology 32 nm
TDP Limit 95 Watts
Core Speed 1402.9 MHz
Multiplier x FSB 7.0 x 200.4 MHz
Stock frequency 3600 MHz
Instructions sets MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, x86-64, AMD-V, AES, AVX, XOP
L1 Data cache 4 x 16 KBytes, 4-way set associative, 64-byte line size
L1 Instruction cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 2 x 2048 KBytes, 16-way set associative, 64-byte line size
L3 cache 8 MBytes, 64-way set associative, 64-byte line size
FID/VID Control yes
Min FID 7.0x
# of P-States 7
P-State FID 0x16 - VID 0x0B - IDD 21 (19.00x - 1.412 V)
P-State FID 0x15 - VID 0x0E - IDD 21 (18.50x - 1.375 V)
P-State FID 0x14 - VID 0x15 - IDD 15 (18.00x - 1.287 V)
P-State FID 0x11 - VID 0x1B - IDD 13 (16.50x - 1.212 V)
P-State FID 0x9 - VID 0x22 - IDD 10 (12.50x - 1.125 V)
P-State FID 0x1 - VID 0x2C - IDD 7 (8.50x - 1.000 V)
P-State FID 0x10C - VID 0x30 - IDD 6 (7.00x - 0.950 V)

PStateReg 0x800001D5-0x00001616
PStateReg 0x800001D5-0x00001C15
PStateReg 0x8000019A-0x00002A14
PStateReg 0x80000182-0x00003611
PStateReg 0x80000163-0x00004409
PStateReg 0x80000143-0x00005801
PStateReg 0x80000139-0x0000604C
PStateReg 0x00000000-0x00000000

Package Type 0x1
Model 00
String 1 0x0
String 2 0x0
Page 0x0
CmpCap 3
Base TDP 11 Watts
Boosted P-States 2
Max non-turbo ratio 18.00x
Max turbo ratio 19.00x
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3
Attached device PCI device at bus 0, device 24, function 4
Attached device PCI device at bus 0, device 24, function 5




If I experience a crash with this stick of RAM (which i know isn't a bad stick), i'll just go ahead and RMA the motherboard and cross my fingers that it was the issue. Else, if i cant get it to crash, i'll RMA the RAM.



As a last resort, try upgrading the BIOS from DOS or a boot cd like UBCD (since windows is unstable). Use only 1 stick for this, as you want to minimize the possibility of a crash.
July 24, 2012 7:43:08 PM

Maxx_Power said:
As a last resort, try upgrading the BIOS from DOS or a boot cd like UBCD (since windows is unstable). Use only 1 stick for this, as you want to minimize the possibility of a crash.



It just crashed with the good stick of RAM.

I'll go ahead and try the bios upgrade right now.
a b B Homebuilt system
July 24, 2012 7:45:27 PM

moonunit93 said:
It just crashed with the good stick of RAM.

I'll go ahead and try the bios upgrade right now.


Be sure to let the BIOS updater to reset CMOS, or do it manually after the update.
July 24, 2012 8:03:40 PM

Maxx_Power said:
Be sure to let the BIOS updater to reset CMOS, or do it manually after the update.



Successfully updated, now says 1.40 which was released on 7/10/2012. Guess I'll cross my fingers!
a b B Homebuilt system
July 24, 2012 8:15:57 PM

moonunit93 said:
Successfully updated, now says 1.40 which was released on 7/10/2012. Guess I'll cross my fingers!


What was the old version ?
July 24, 2012 8:39:30 PM

Maxx_Power said:
What was the old version ?


1.2, which looks to be from May
a b B Homebuilt system
July 24, 2012 8:45:10 PM

moonunit93 said:
1.2, which looks to be from May


Okay, keep fingers crossed. Let me know what happens.
July 25, 2012 9:32:32 PM

Well, i've been using it for a total of about 4 hours now (minus time asleep that i've been gone) and it hasn't crashed yet. If it doesn't crash after a straight 5-6 hours more of use, i think i'll call it fixed!
a b B Homebuilt system
July 25, 2012 10:54:48 PM

moonunit93 said:
Well, i've been using it for a total of about 4 hours now (minus time asleep that i've been gone) and it hasn't crashed yet. If it doesn't crash after a straight 5-6 hours more of use, i think i'll call it fixed!


Still keeping fingers crossed.... My non-crashes be on your side.
August 2, 2012 12:12:29 AM

Alright, well, it crashed... :( 

The motherboard is on its way back as we speak, and a new one should be to me within the week. If a new motherboard doesn't fix the problem i have NO IDEA what could possibly be wrong seeing as i've basically tested every other part.
a b B Homebuilt system
August 2, 2012 2:25:19 PM

moonunit93 said:
Alright, well, it crashed... :( 

The motherboard is on its way back as we speak, and a new one should be to me within the week. If a new motherboard doesn't fix the problem i have NO IDEA what could possibly be wrong seeing as i've basically tested every other part.


Then let's hope your new board will be perfect.
August 10, 2012 2:10:55 AM

New board arrived............. crashes :( 

It's really weird though because it's working 10000% better than before. It's VERY noticeably faster (just opening things), and it only crashes every few hours opposed to a potentialy 10 seconds after booting.

regardless of the "improvement" there is still something very obviously wrong, and i have NO GOD DAMN CLUE what to do.
a b B Homebuilt system
August 10, 2012 1:57:10 PM

At this point of time, I guess you should try all the other non-obvious things, try a different PSU (it is possible that your other PSU is periodically sending out lower than acceptable voltages), GPU.
!