Random BSOD on W7

[Bobokun]

Hey guys I'm trying to find help on this problem :S I've posted it on another forum too but there seems to be no help so far. I would get random BSOD which drives me crazy! I even reformatted my computer. I used a program called KillDisk which securely deletes everything on your HD and restores it back to as if you bought it from the manufacturer and deletes everything permanently. I'm not sure what is the cause of this BSOD Please help me!

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 4105

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\091509-20217-01.dmp
C:\Users\Jon\AppData\Local\Temp\WER-33087-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[H2SO4]

If you copy this file (listed in your report) to a temporary location, zip it up, then upload it here, somebody may be able to analyse it and tell you why your machine is crashing:

"C:\Windows\Minidump\091509-20217-01.dmp"

 

[Bobokun]

Minidump post :]

Hey Thanks for replying so quickly! I will post up the mini-dump you requested. :] Please try and help me fix this problem as I have been struggling with the BSOD ever since I started using windows 7. When I was using Windows Vista and XP it had no problem running or having BSOD. My assumption is that some driver issues may be the cause of this. But I updated all my drivers to the latest version ): So i'm not sure...

 

[H2SO4]

Hey Thanks for replying so quickly! I will post up the mini-dump you requested. :] Please try and help me fix this problem as I have been struggling with the BSOD ever since I started using windows 7. When I was using Windows Vista and XP it had no problem running or having BSOD. My assumption is that some driver issues may be the cause of this. But I updated all my drivers to the latest version ): So i'm not sure...

I hate to be the bearer of bad news, but everything about that set of minidumps screams "unreliable hardware".

If you're over-clocking, that's a bad idea, and if the machine is being insufficiently cooled that could also be the cause. If the machine is new or still under warranty, you may want to consider showing the same minidumps to the hardware vendor and asking them for a replacement. They can then sort out exactly what's wrong with it on their own time, after they give you a box that works.

I can give you more debug info if you're interested.

 

[Bobokun]

Yes I am overclocking..however I've ran many stress tests and also have tested for stability many many times and with all my tests it shows that my overclock is stable. my Q9400 is running at 3.4GHz and I've ran different programs like intel burn test and prime95 for so long and I've never gotten errors. If what u say is true..than how come when I use windows vista or XP I've never gotten BSOD once? :S

My machine runs at max 50degrees celcius and is usually at 39degrees. It only goes up to 50 when I'm playing a hardcore game with max graphics. So the temperature should be fine. I also ran Memtest overnight and it shows not one error for my memory :S

Is there a way that you could find out which part in my machine is causing the trouble? Because I bought all my parts seperately and built the machine myself so every part has its own warranty. IF there is any way to find out what part of my machine is causing it that would be great.

 

[H2SO4]

...it shows that my overclock is stable.

With respect, the 9 minidumps suggest otherwise

If what u say is true..than how come when I use windows vista or XP I've never gotten BSOD once? :S

I don't know. Perhaps the weather was colder at time of the year (in your locality), or there was less dust in the processor fan, or you didn't drive it quite as hard, or you got lucky, or...

In any case, troubleshooting BSODs while the machine remains overclocked is pointless. To "overclock" means to drive one or more pieces of hardware beyond their design specifications - to make them do something they were not designed to do. Literally every failure is then potentially attributable to hardware glitches, even if it wasn't quite as obviously hardware-related as these 9 crashes.

 

[Bobokun]

Thank you. I will disable all my OC and see if I still get BSOD. If I still get BSOD's is there any way you can find out what hardware is the problem? :S I need to know what I need to return to the manufacturer since I built this computer myself

 

[H2SO4]

Thank you. I will disable all my OC and see if I still get BSOD. If I still get BSOD's is there any way you can find out what hardware is the problem? :S I need to know what I need to return to the manufacturer since I built this computer myself

No, I'm sorry, I can't tell you precisely which component is definitely at fault. Memory dumps are generally not a good way to determine that since you can't readily tell why a certain bit of memory isn't what it's supposed to be - whether the RAM is faulty, or whether the processor mismanaged one of its calculations, or whether the bus used to transport those data is unreliable.

Three of those dumps are of a type called a stop 0x124 - an error reported by the hardware itself, not a software crash. They reference the "PROCESSOR_BUS" as the entity where the error was detected, and hence it is entirely likely that the processor is somehow at fault. Reverting to non OC-ed settings may resolve that issue, but I cannot guarantee that.

 

[Bobokun]

Ok I reverted all my OC'd and restored everything to default, including my RAM. Hopefully this will fix the problem. If it doesn't then do you think my best bet is to return my processor? Do you think that is the most likely hardware at fault? Thank you for your quick responses and I will come back in a few days (or earlier) depending when the next time I get a BSOD is.