Random BSOD

[simplynluv]

As stated on the title guys

My 2 months rig sometimes having BSOD randomly

whether if it is idle, doing work, or playing games

randomly happened, been 3-4 times

some people in my place mention that it is caused by the HDD (I use only one HDD - 500GB Green Sata from Western Digital - Windows + Data installed within one HDD, and I did the partition there; C for windows and Programs + D for data)
BSOD was caused by imbalance reading speed between Proc with HDD


is it true like that?
this thing really irritating me.. especiallu when I'm in middle of something, or when i do my work (V Ray rendering) and its already halfway - BUMMMBB!! BSOD - even when I do nothing, the computer is IDLE

and I got a message about MemDump on the BSOD
I tried google it, but cant found anything good...

Computer specs;

Core i7 3770 - non OC
Asus Z77 V Pro Motherboards
Kingston 16GB 4 x 4GB Hyper X
Asus ENGTX 580 DC II
Seasonic Modular M12II 750watt
HDD WD 500GB - Green Sata
V6GT Cooler
HAF912 Advanced Customized

Drivers all up to date - non beta driver installed
beta driver no installed

 

[Puppies04]

Has it been overclocked at any point? install cpuz and see what the bus speed is set at (make sure you stress the CPU out whilst checking)

 

[Steltek]

An i7 system running on what is essentially a 5400RPM hard drive? Sorry, had to get my mind 'round that concept...

Anyway, what is the specific BSOD stop code you are getting?

 

[simplynluv]

Has it been overclocked at any point? install cpuz and see what the bus speed is set at (make sure you stress the CPU out whilst checking)

Hi, thanks for the reply there

No, I never OC it since I'm using it for V Ray rendering (where stabilty of the system is very crucial for me)

I did install CPU Z and put stress on it (100% CPu working load)
temps are normal, 55-58 (yeah.. I put max fan blow on V6GT when my CPU hit 55 degree)

idle : speed around 1600 MHz, Bus Speed around 100.3 MHz
stress : speed around 3700 - 3900MHz, Bus Speed around 100.3 MHz

any idea?

 

[simplynluv]

An i7 system running on what is essentially a 5400RPM hard drive? Sorry, had to get my mind 'round that concept...

Anyway, what is the specific BSOD stop code you are getting?

yeah dude...

I plan to get myself an SSD once I got some cash

I cant exactly remember what is the code, there are two or three
but all of them came up with something that mention "MemDump"

can help me dude?

thanks for your reply anyway :biggrin:

 

[Puppies04]

Hi, thanks for the reply there

No, I never OC it since I'm using it for V Ray rendering (where stabilty of the system is very crucial for me)

I did install CPU Z and put stress on it (100% CPu working load)
temps are normal, 55-58 (yeah.. I put max fan blow on V6GT when my CPU hit 55 degree)

idle : speed around 1600 MHz, Bus Speed around 100.3 MHz
stress : speed around 3700 - 3900MHz, Bus Speed around 100.3 MHz

any idea?

Nope, wasn't what I was thinking it might be, sorry.

 

[Steltek]

yeah dude...

I plan to get myself an SSD once I got some cash

I cant exactly remember what is the code, there are two or three
but all of them came up with something that mention "MemDump"

can help me dude?

thanks for your reply anyway :biggrin:

Wasn't trying to be insulting - that WD Green hard drive just looked so out of place in your overall equipment list that I just couldn't resist saying something.

Anyway, Windows generally creates a memory dump file located at C:\Windows\Minidump

You can configure Windows to write a dump files by typing Advanced Systems Settings in the search box off the start menu. In the System Properties box that pops up, go to Startup and Recovery and hit the Settings button. In the Startup and Recovery dialog that pops up, go to the System Failure section. In the write debugging information section, set Windows to write a Kernel Memory Dump.

Download and install the free for home use version of Whocrashed from this link:

http://www.resplendence.com/download/whocrashedSetup.exe

Next time you have a BSOD, once you restart run Whocrashed and have it analyze the dump file from the BSOD to see if it tells you anything about the crash.

 

[Slammy1]

You've Memtested and found no problems?

Also, check out EventViewer to see if you're registering an error before or during the dump.

Problems of this nature can be very hard to track down. Hopefully something will jump out as to the cause, but my last rig had issues the entire time I had it. It eventually went bad, turned out it was the memory slot (but it was Memtest stable so go figure).

 

[simplynluv]

Wasn't trying to be insulting - that WD Green hard drive just looked so out of place in your overall equipment list that I just couldn't resist saying something.

Anyway, Windows generally creates a memory dump file located at C:\Windows\Minidump

You can configure Windows to write a dump files by typing Advanced Systems Settings in the search box off the start menu. In the System Properties box that pops up, go to Startup and Recovery and hit the Settings button. In the Startup and Recovery dialog that pops up, go to the System Failure section. In the write debugging information section, set Windows to write a Kernel Memory Dump.

Download and install the free for home use version of Whocrashed from this link:

http://www.resplendence.com/download/whocrashedSetup.exe

Next time you have a BSOD, once you restart run Whocrashed and have it analyze the dump file from the BSOD to see if it tells you anything about the crash.

hahaha
Yeah, agree with you - WD Green HDD is something annoying from my current rig

Thanks for your reply, I will read it and try what you write down here

:biggrin:

 

[simplynluv]

You've Memtested and found no problems?

Also, check out EventViewer to see if you're registering an error before or during the dump.

Problems of this nature can be very hard to track down. Hopefully something will jump out as to the cause, but my last rig had issues the entire time I had it. It eventually went bad, turned out it was the memory slot (but it was Memtest stable so go figure).

yeah bro, I did memtest, and everything is working fine
if I can't find the problem myself, probably I will have to send my rig to the local trusted computer shop around my area

thanks a lot for the reply:biggrin:

 

[simplynluv]

Guys, I see something like this when I check the event viewer

any idea what is happening?

 

[Slammy1]

http://support.microsoft.com/kb/2028504

This error is generated on system restart. There are some trouble shooting steps as well, some good info there.

The restart is abrupt, not throwing an error.

 

[simplynluv]

http://support.microsoft.com/kb/2028504

This error is generated on system restart. There are some trouble shooting steps as well, some good info there.

The restart is abrupt, not throwing an error.

oh my.. I dont understand what is happening here

but thanks, i will read them now

is Seasonic M12II Modular 750watt good enough to support my system?
I do calculation before, 750watt should be plenty for a single GTX 580 right?

 

[Steltek]

oh my.. I dont understand what is happening here

but thanks, i will read them now

is Seasonic M12II Modular 750watt good enough to support my system?
I do calculation before, 750watt should be plenty for a single GTX 580 right?

That power supply has more than enough capacity for your equipment list, so it isn't a simple power capacity issue. That doesn't mean you don't have a bad power supply, though, but I'd save that for a last resort.

Did you build this system yourself, or did somebody build it for you? Are the memory modules which were used on the motherboard memory compatibility list? If not, you might need a BIOS update. You can also try clearing the CMOS memory and then setting the BIOS back to optimized defaults.

If you feel comfortable doing it, you might also reseat all the power cables to be sure one is not loose (your power supply is modular, so make sure to reseat the cable plugs at both ends). Another thing you might try is to pull two of the four memory modules and see how the system runs on just two modules instead of four (look in the motherboard manual and make sure the two remaining modules are in matched slots). If it doesn't crash on two modules, you might just need to bump up the voltage to the memory a little to get things stabilized.

If you want to eliminate Windows as the source of the problem, you can try running from a Linux live CD for a while to see if the system crashes. It might even be worth running a Prime95 session for a few hours to try to stress the system independent of Windows to see if you get a crash.

FWIW, since you've previously had crashes, there is probably a Windows memory dump file already that you can try to analyze with Whocrashed for some additional leads.

 

[simplynluv]

That power supply has more than enough capacity for your equipment list, so it isn't a simple power capacity issue. That doesn't mean you don't have a bad power supply, though, but I'd save that for a last resort.

Did you build this system yourself, or did somebody build it for you? Are the memory modules which were used on the motherboard memory compatibility list? If not, you might need a BIOS update. You can also try clearing the CMOS memory and then setting the BIOS back to optimized defaults.

If you feel comfortable doing it, you might also reseat all the power cables to be sure one is not loose (your power supply is modular, so make sure to reseat the cable plugs at both ends). Another thing you might try is to pull two of the four memory modules and see how the system runs on just two modules instead of four (look in the motherboard manual and make sure the two remaining modules are in matched slots). If it doesn't crash on two modules, you might just need to bump up the voltage to the memory a little to get things stabilized.

If you want to eliminate Windows as the source of the problem, you can try running from a Linux live CD for a while to see if the system crashes. It might even be worth running a Prime95 session for a few hours to try to stress the system independent of Windows to see if you get a crash.

FWIW, since you've previously had crashes, there is probably a Windows memory dump file already that you can try to analyze with Whocrashed for some additional leads.

I ask the shopkeeper to assemble it for me, and yeah, I did check all the parts before I made the purchase
all is compatible, listed in Asus compatible lists too

i havent tried to update the BIOS, I will do it later after I done my work
all Bios setup is on default

this PC have been running 48 hours nonstop since yesterday, and havent got any BSOD so far..

I did re arrange all the wiring 2 times, and I did get a new exact PSU replaced for one week before, same thing happen..

gezz... dunno what is wrong with my PC

 

[Steltek]

I ask the shopkeeper to assemble it for me, and yeah, I did check all the parts before I made the purchase
all is compatible, listed in Asus compatible lists too

i havent tried to update the BIOS, I will do it later after I done my work
all Bios setup is on default

this PC have been running 48 hours nonstop since yesterday, and havent got any BSOD so far..

I did re arrange all the wiring 2 times, and I did get a new exact PSU replaced for one week before, same thing happen..

gezz... dunno what is wrong with my PC

Before you update the BIOS, try clearing the CMOS memory (the motherboard manual will have instructions on how to do it) the next time it crashes and reload the BIOS defaults first.

I'd flash the BIOS as a last resort type of thing because you don't want to take a chance of the system dying in the middle of the flash process.

If you decide to flash, since you indicate the BSODs normally occur after the system has been running for a while it would be best to download the BIOS and prepare everything to do to the flash, but wait to do it after a cold start in the morning to minimize the chance of a crash occurring during the flashing process.

 

[denis280]

Humm! did you check the plug in the wall??

 

[sm625]

Can you run your programs with just 1 stick of RAM? Try to run what you can with 1 stick and see if that makes a difference. Remove them all first, then put one back in.

If it still BSOD, replace the stick with one other stick, in a different slot. If it still BSOD then try removing video card and running off IGP.

 

[simplynluv]

Sorry for the very late reply guys

UPDATE :

I check the electricity wiring from front of my house till my room - everything is solid, perfectly fine - I did try using another Desktop of mine, everything is fine

Update the Bios, same thing happen, BSOD after 6 hours running idle / working on load

I bought a new pair of RAM and test it
same thing happen after view hours

gezz.....

this really start make me pissed and impatient..

I plan to try change the HDD to SSD for now..
but dunno when can afford it, need some time to get myself a SSD..

cheers :biggrin: