Really at a loss on what going on here. For the past week and a bit my PC has been throwing up a blue screen error message. It doesn't seem to be caused by anything in particular i.e. I haven't noticed certain programs or the removal/input of usb hardware triggers it...often it's happened when I've left it idle while going off to do something else with no programs running.

 

This is the message:

 

MACHINE_CHECK_EXCEPTION

 

*** STOP: 0x0000009C (0x00000004,0x80546E70, 0xB2000000, 0x00070F0F)

 

For the past 12 months the computer has been constantly going wrong tbh...luckily a forum member has been kind enough to troubleshoot the problems, put things right and/or perform a re-install but although they're a good mate I feel pretty bad constantly having to ask for help so I thought I'd also throw it out there in case it's something people can guide through putting right myself! It's truly been driving me insane (thought I'd lost all my important graphic and audio files for the band at one point...they're now all backed up in triplicate!)

 

Any ideas folks?

 

Cheers,

 

Leigh.

if it's constantly going qrong and showing BSOD's after re installing windows(if it has been shut down correctly always etc) your hard drive may be beginning to show signs of beginning to fail.BSOD's as you have listed above can usually be repaired put the code into google and you should come up with a microsoft page of how to fix it chances are though if you've got a fresh install and it has gone on properly then looks like hdd.

 

I had a bad one and no amount of installing windows, low level formatting(i even tried those hdd repair tool thingies which took ages and was cr@p) repaired it. It would run for a bit and randomly throw a blue screen of death which i'd sort out and a while later it would happen again. got me a new 120Gb HDD for a few quid at the time and it's been running now for about 2-3 years ok.

 

It could be another component but my money is on the HDD you could try running with just on stick of ram and trying them individually till it crashes to rule that out also if you have access to another cpu you could swap them around and try that. I've even had power supplies fail that would still operate the 12v to the CD drives etc I bought a new motherboard and cpu for that machine too til I found out they didn't work on the machine either so sold the old parts on after getting a new psu for it.

Edited August 2, 200916 yr by 8ace

I had continuos blue screens like that once. Turned out to be bad/incompatible RAM.

 

If you've got two sticks of RAM, try taking one out or alternating between the two.

Also just found this for you if it throws any light on it http://www.techspot.com/vb/topic129399.html

Hi i've had this problem when building computers for customers, it is the memory in your computer that has a problem. Change the memory on the motherboard you should not have any problems.

0x0000009C (0x00000004,0x80546E70, 0xB2000000, 0x00070F0F) is the memory path it has a problem with. When changing memory always change in pairs!!

Hope this helps. If your not sure PM me.

the blue screen is a hardware failure. first try your ram if you have 2 slots full take one out and try again, then if its still the same swop them cause its usually one that goes down

Guys, I can't thank you enough for your comments.

 

After my last HD appeared to be on the way out I was advised to buy a new one so, back in December of last year I did, buying a Western Digital Caviar Blue 160GB model. I also bought 2Gb (2x1Gb) of DDR memory. It seems like the problems I've been having since then may well be connected, although weirdly it was a few months before things started to go wrong which is why I didn't make the connection (and I have to admit I know next to nothing about this sort of thing!).

 

I've been getting blue screen messages every day for nearly 2 weeks now but yesterday after it failed to boot up, which often happens after getting the BSOD, saying there was a Boot Disk Failure and asking that I insert the original Win XP disk, I did so, as I've done before but with no results...but this time it went directly to Check Disk and proceeded to boot up Windows. Since then it hasn't gone wrong....TBH though, I'm not going to hold my breath...I have a feeling it's going to do it again very soon... :(

 

This computer is going to be the death of me :(

mate to make sure its not your ram which i think it is download memtest86 and run it for a few hours let it run when you go to bed and check results when you wake up it will tell you what the problem is, or you can go more advanced and donwload ultimatebootcd that has a pretty good diagnostics program then you can work on the fix ;)

memtest86 as above for ram, also the power supply's worth testing, swap with a known good one to test.

The BLUE SCREEN OF DEATH, your Doomed ! ! ! !

Think I spoke too soon about everything running ok as, a few hours after posting, the inimitable BSOD made an appearance and the computer refused to reboot thereafter...and this morning it also point blank refused to play ball, getting as far as just before the Windows logo before saying Boot Error etc etc. So, without being able to get into Windows to run a Memory test I decided to get a little more direct and removed one of the modules...and lo and behold, it starts first time with no errors or Check Disk etc. Not counting my chickens yet but it "seems" like that may be the problem. I'll put it back in and see if it stalls again when I've finished grabbing the few remaining files on here that aren't backed up! Really wish I could afford a whizzbang new i7 system... :(

I'm building an i7 mean gaming machine for myself soon, can't wait! :)

I'm building an i7 mean gaming machine for myself soon, can't wait! :)

 

Cheers for rubbing it in, lol! :cry:;)

Cheers for rubbing it in, lol! :cry:;)

 

can sell you my one when I build the i7 ;)

its a nice fatal1ty spec pc with E4600 2.4ghz overclocked at 3 with no raise of temperature at all ;)

Right, an update.

 

I've tried two things: firstly, turning off the quick start-up in BIOS so it performs a memory check. It didn't seem to highlight any problems.

 

Secondly, I ran memtest86 last night...came to it this morning and the results, after 6 passes were that the memory is absolutely fine.

 

Hmmm...

 

Question: I'm running two HD's, the main drive (which is new) which has been partitioned so that the smaller portion is used for Windows and the larger is used as storage and a second drive which I used to use to record audio when this computer was my DAW...so...although this second drive doesn't contain any Windows files, could it still cause these BSOD's? I have also started to notice a "clicking" coming from the general direction of the HD's which doesn't sound good (I know it can be a sign of imminent HD failure)...however this isn't all the time and it can run for hours upon hours before it starts, and then it can go as suddenly as it appeared.

 

lusitano: I had no idea who or what "Fatal1ty" was until I Googled: he seems to be some sort of "pro" gamer...er...right then! ;) TBH, I was all set to buy an i7 system but the album then needed more money than I'd accounted for so I had to put it towards that instead, so part of me is saying hold off on buying a stop-gap as it's a false economy when it's not what I really want! Then again, if the price is right...well, let me know when you do and we'll take it from there ;)

Right, an update.

 

I've tried two things: firstly, turning off the quick start-up in BIOS so it performs a memory check. It didn't seem to highlight any problems.

 

Secondly, I ran memtest86 last night...came to it this morning and the results, after 6 passes were that the memory is absolutely fine.

 

Hmmm...

 

Question: I'm running two HD's, the main drive (which is new) which has been partitioned so that the smaller portion is used for Windows and the larger is used as storage and a second drive which I used to use to record audio when this computer was my DAW...so...although this second drive doesn't contain any Windows files, could it still cause these BSOD's? I have also started to notice a "clicking" coming from the general direction of the HD's which doesn't sound good (I know it can be a sign of imminent HD failure)...however this isn't all the time and it can run for hours upon hours before it starts, and then it can go as suddenly as it appeared.

 

lusitano: I had no idea who or what "Fatal1ty" was until I Googled: he seems to be some sort of "pro" gamer...er...right then! ;) TBH, I was all set to buy an i7 system but the album then needed more money than I'd accounted for so I had to put it towards that instead, so part of me is saying hold off on buying a stop-gap as it's a false economy when it's not what I really want! Then again, if the price is right...well, let me know when you do and we'll take it from there ;)

 

 

 

can you not disconnect the suspect slave drive for the time being and see if the bsod happens. Not sure if bsod would happen with the slave drive but who knows windows does odd stuff.

 

 

Also new drives can fail too. I had a brand new drive fail in less than 9 months but it would boot now and again(enough for me to get my stuff from it) then it went back to seagate and was replaced under there warranty with a "refurbed " one

Edited August 5, 200916 yr by 8ace

Right, an update.

 

I've tried two things: firstly, turning off the quick start-up in BIOS so it performs a memory check. It didn't seem to highlight any problems.

 

Secondly, I ran memtest86 last night...came to it this morning and the results, after 6 passes were that the memory is absolutely fine.

 

Hmmm...

 

Question: I'm running two HD's, the main drive (which is new) which has been partitioned so that the smaller portion is used for Windows and the larger is used as storage and a second drive which I used to use to record audio when this computer was my DAW...so...although this second drive doesn't contain any Windows files, could it still cause these BSOD's? I have also started to notice a "clicking" coming from the general direction of the HD's which doesn't sound good (I know it can be a sign of imminent HD failure)...however this isn't all the time and it can run for hours upon hours before it starts, and then it can go as suddenly as it appeared.

 

lusitano: I had no idea who or what "Fatal1ty" was until I Googled: he seems to be some sort of "pro" gamer...er...right then! ;) TBH, I was all set to buy an i7 system but the album then needed more money than I'd accounted for so I had to put it towards that instead, so part of me is saying hold off on buying a stop-gap as it's a false economy when it's not what I really want! Then again, if the price is right...well, let me know when you do and we'll take it from there ;)

 

 

Fatal1ty brand is good brand, I'm happy with it.

By the time i gather all the money needed for my new system you problaly have yours done already but if not then we can talk :)

now you problaly have done this already but in case you didnt try this.

go to cmd and type chkdsk /r and see if it finds any errors if it does should repair and can be a long process but worth a try.

Edited August 5, 200916 yr by lusitano
typo