Two BSODs in close proximity after reformat

Killgroup

Killgroup

Killgroup

Associate
Joined
26 Dec 2007
Posts
63
So, I'll start from the beginning:

I was playing Fallout New Vegas and my PC crashed (I just thought it was an any day crash) so I restarted my computer and I couldn't get past the login screen without it freezing, I then tried getting into safe mode to diagnose the problem, and kept going from safe mode to normal to safe and then eventually safe mode stopped working so my only option was to reformat.

I've finished reformatting thinking "Great, I can finally start using my main computer again", I start installing all the usual programs/drivers etc. and then I get a BSOD, I restart and attempt to install things again and I get another BSOD. I'm thinking what might be causing it (sadly) is the HDD (It's a Samsung Spinpoint F3 1TB), but I've only had it for less than a year (So I 'should' be able to claim warranty if it is the HDD). I've tried CHKDSK and everything seems clear so I'm left confused.

Below is the error report Windows showed me:


Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004F9C038
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\102210-21340-01.dmp
C:\Users\Charlie\AppData\Local\Temp\WER-44007-0.sysdata.xml

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

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


The two files can be provided upon request.

Thank you very much for any help/suggestions, it is greatly appreciated.
 
I took a look at the memory dump and unfortunately I can't seem to get the correct symbols for the dump file. All I did find was it was caused by a hardware issue.
 
Yeah, I thought it was hardware since after format it was still doing it but thanks anyway. What did you mean by being unable to get the correct symbols? Is there anything I could do to help?

Thanks.
 
Couple of things i recommend doing are, running memtest for a few hours and/or slackening off any overclock first, see where that leaves you.
 
Thanks for the suggestion Masterk.

Something to report up on - I've been on the main computer for around 20 mins now, downloaded & installed G15 drivers no crash, I noticed both times I BSODed it was when installing ATI CCC drivers, I also noticed previously (before reformat), when the drivers were disabled I was able to get onto normal mode, furthermore, it first crashed in Fallout New Vegas, so all I can conclude right now is that it's GPU related? Would this sound right?

Going to try installing ATI drivers one more time, if it crashes again I guess that's the problem?

Edit: It didn't crash, I have no leads now as to what could be causing it.
 
Last edited:
It could have been a corrupt driver. Or it still could be corrupt RAM or HDD.

I would find a diagnostic tool from Samsung for testing your HDD - it will likely be something you boot up [so doesn't run in Windows]. If that gives you the all-clear, try Memtest as suggested earlier.
 
Memtest came back with no errors, only pass.

Doing HDD diagnostic with ESTOOL (Samsung) and it seems to be passing everything. I really am confused as to what could have caused it, I'd like to know because I don't feel safe :P
 
Whenever I've tried overclocking and I've got a 124 BSOD it's been cpu voltage related, might be worth bumping it up a notch or two.
 
Update: I just tried installing my audio card driver then and it froze the computer, I didn't expect the audio card to be the problem as it's my newest hardware, but could it be that causing the problem?

Tried installing update through device manager, as soon as update was installed I heard a clicking coming from my computer (?) and then it froze.
 
Last edited:
Age is of no relevance at all when it comes to PC hardware. Had far too much stuff arrive DOA over the years to make me think new = not the problem! :p

Remove the soundcard and drivers and see if you have any crashes throughout the day. If none, wack it back in and see if it falls over again.
 
You must log in or register to reply here.
Back
Top Bottom