BSOD happening 7eral times a day

[Plastic Nev]

Hi Bazman, sorry to hear that when we thought we had won one.

OK what were you doing at the time it went, and also did you notice any kind of slow down, odd things on screen or other unregularities leading up to the crash, it may not have been a spike of heat and could have been building up slowly, you wouldn't have known as you didn't open Speccy till after it recovered.

Hence why Armageddon's good suggestion of a more powerful fan may help. If you were playing an intensive game at the time then a slow build up of heat could be the reason rather than a sudden surge.

 

Nev.

[KenB]

Hi Bazman

 

Just adding a bit to what Nev and Armageddon have advised ....

 

If your Video Card was covered in fluffy dust then the case vents and fans would be too.

Also take a close look at the CPU fan on the motherboard.

Use the compressed air on these too.

 

Using compressed air:

If you hold the button down for too long you will get the expellant gas liquefying ( as you found )

Us it in short bursts for best effect.

 

so happy to pay whatever you think is right.

Thank you for your kind offer. :)

We don't insist that our members contribute but if they do we are happy to accept as it helps to keep the forums running.

 

To give you some idea - recently members have donated £5 / £10 and the more generous have been able to afford more.

Really it is up to you.

If you do decide to donate we would be very grateful.

[Bazman]

Donation made, very grateful for this resource so happy to lend my support. I was away at lunch when the last blue screen occurred so I'm not sure how the load would have increased while I was not there. Will try cleaning the interior again paying more attention to the fans this time. Lets see how that goes. If the problem persists I guess I'll have to look at improved cooling. Just as a heads up do you think water cooling might be better in my situation as this will not be as susceptible to dust?

[KenB]

do you think water cooling might be better in my situation

It shouldn't be necessary - let's see how you get on with cleaning the fans etc.

 

Many thanks for the donation - much appreciated :)

[Plastic Nev]

Many thanks from me too for the donation.

If after a further clean up and you still get problems, let us know as there may be something else acting up now and then. Even perhaps some odd fault on the graphics card, but too early to say yet.

 

Nev.

[Armageddon]

Many thanks from me too for the donation , I also agree with Ken and Nev about watercooling it shouldn't be needed , I took the bull by the horns myself today and cleaned the fans in my desktop that lives in a cupboard , there was a fair build up of dust I cleaned them with air and a soft bristled brush and even though my system runs reasonably cool after cleaning I have a on average 7C drop in temps.

[Bazman]

Well a further two crashes with the same error code given both times (0x00000124), and even the same memory locations referred to each time? However I have to confess I have not done the thorough internal clean yet so I'll wait till I've done that before doing anything else. With that in mind would these brushes be appropriate for internal cleaning: http://www.artsupplies.co.uk/brushes-series-a-hog-brush-long-flat-oil-brushes.htm

[KenB]

Hi Nev / Bazman

 

I have removed the "Solved" from the thread title for the time being :)

 

Let's hope the clean video card solves the problem :)

[Plastic Nev]

Hi, that's OK Ken, I was thinking of doing just that myself.

 

OK about those brushes, go for the large one Bazman, being animal hair they won't create or aid in creating static and therefore ideal for the job.

 

I must admit I was surprised, when I saw Artists brushes I thought lots of £ signs here, and was pleasantly surprised to see how cheap they are.

 

Now for the continuous 0x00000124 error code, It is certainly a hardware error code and this could be the graphics card. There is a tremendous amount of information available including a direct connection to PCIe devices in Windows Vista, though your system is Windows 7 there are too many similarities between the two to ignore that.

 

I am now a little concerned that the overheating prior to cleaning may have done some damage to it. Although it may not now be overheating, it could just be down to expansion of some part of it when it does warm up a bit.

 

The only real test would be to try it in a different computer and see if the fault happens then.

If not a computer of your own, perhaps a willing friend.

 

Nev.

[Bazman]

I realise this is an old one but been on holiday etc. Anyway finally got those brushes and gave the inside a really good clean. I can't guarantee I got it all (especially if there is dust jammed down the slots on the motherboard where the graphics card sits) but it's a lot better than it was with all visible dust removed. Still getting those dammed BSOD's though with the same error codes each time: 0X00000124, 0x0...0X16, 0XFFFFFA800DC2E028,)x00000000BE200000,Ox00000000000T110A. If memory serves these indicate a memory card problem? If you like I can send pictures of the motherboard slots where the motherboard fits, some parts seem a little discoloured even though I have cleaned it as well as I can.

[Bazman]

[ATTACH=CONFIG]1042.vB5-legacyid=1967[/ATTACH] I include fuller details of the last two BSOD's.

[Plastic Nev]

It does seem to indicate some hardware fault in general, it could be RAM, but I am still of the feeling, my opinion only mind, that there is a problem with the graphics card as the fault code 0X00000124 is also linked to PCIe slots as well.

 

There is a tremendous amount of information available on Microsofts own support pages, just have a look here:-

 

http://search.microsoft.com/en-gb/Results.aspx?q=0X00000124

 

See if any of the different fixes on there are of any help as well.

 

Nev.

[danzil]

Hi

looking at the error you are getting I can see it noting HAL.dll.

few questions if you don't mind>

how many hard drives do you have installed in this machine?

what is the bios boot up sequence set to.

has the boot.ini been edited in anyway. (for example an attempted operating system update, or booting from an additional source).

 

have seen this issue a few times when 2 or more hard drive have been installed and the boot sequence has been set wrong, this caused the OS to act extremely strange and throw the same errors as seen in this thread.

also seen the hal.dll error with corrupt hard drive, you have done a scandisk so can almost rule that out,

If the boot.ini file has been changed it can also throw this error.

 

Are all your driver including chipset up to date? and of course the bios?

 

have not been around for a while so sorry if I seem to be jumping in.

 

best regards

[Bazman]

Hi there, The computer has two hard drives a solid state one that it boots off and a traditional one as back up. How can I find out that the bios boot up sequence is set to? Again how can I check of the boot.ini has been altered? I will double check the drivers but I haven't done anything manually but as far as I know they are all set to update automatically as and when they become available. Certainly no need to apologise all help is very welcome.

[danzil]

to check your boot sequence you would need to enter your BIOS>

depending on what bios you have it will be a case of pressing the F2 key or the DELETE key at POST (startup), then checking your boot sequence. this should be set to your main drive, the main drive being the drive that hous3es your operating system.

 

maybe worth checking that your Solid State Drive running mode, is it set to SATA or AHCI.

 

again there is a possibility that a firmware update is available for your SSD.

 

As for the boot.ini very sorry for the misleading information, windows 7 does not have a boot.ini as such, it now uses a boot manager.

to view this go to start (orb) type in cmd then right click cmd as choose run as administrator. click yes on the prompt screen.

when you see a black box (looks like DOS) type in bcedit then press enter

 

take a screenshot of what you see, use snipping tool if needs be.

 

regards

[Bazman]

OK there is the result of the cmd screen the commend "bcedit" is not recognised [ATTACH=CONFIG]1043.vB5-legacyid=1968[/ATTACH] will check BIOS On next reboot. How can I check if the solid state is running SATA or AHCI? Double checked the "indows update" in control panel the drivers are set to update automatically and the last time it updated was June 15th

Edited July 5, 2013 by Bazman