BSOD's suddenly occurring very frequently, errors 0x00000024, 4a, 1b

[benjamins]

Hello,

I am new to these forums and was hoping for some help regarding my rather extreme BSOD situation.

I've had this PC from Chillblast for over 2 years now, and other than the occasional BSOD (think I've had 3/4 in those 2 years), which was usually rectified with a nVidia driver update, it has been fine. Yesterday it BSOD while I was doing exactly the same things as usual. I had Firefox open with 5/6 tabs, one with fullscreen flash video, Steam was running but I had just closed down the Path of Exile game, and maybe Winamp was open but idle.

Since it started at about 9pm yesterday I can't get the computer to stay up other than idling for very long, hence why I'm adding all this info before trying to go through the seven forums diagnostics tools, as it might not stay up for long enough to run them.

What should I do next? I'm guessing I should try to install the SF diagnostic tool, if the computer will survive long enough to allow it.

Cheers,
Ben

 

[aritra2116]

Please post the SF diagnostic tool files in your next post while a BSOD professional catches up.

 

[benjamins]

I will try to first download it and then run it, but as I said this does require my system to stay up long enough for me to do either of those things.

Assuming it would survive longer in safe mode, is it worth running the tool in safe mode?

This is my issue, I've not known any pc to go from fully working to such frequent BSOD's in such a short space of time.

 

[aritra2116]

Try it in safe mode. Do you have another computer to download the SF diagnostic tool? If yes, download it on that computer and transfer it to the problem computer with a USB drive. This will give you a bit more time to use that tool before the next bsod occurs.

 

[benjamins]

Yes I have my macbook so I can download and transfer things if needed. I will try and run it when I get back from work.

What I would most like to know is if this is a hardware or software issue. If it's software then I might just bite the bullet and reinstall windows, which might require me to buy another copy as I don't know if it shipped with a disk.

 

[benjamins]

I should probably mention I have done a ChkDsk on the only HDD, and other than seeming to say it moved a file, then moved it back again, it didn't appear to do anything nor find any issues. For the next bootup I have it scheduled to go through with both ChkDsk options enabled.

 

[benjamins]

Here's an update:

I did a full ChkDsk with both options ticked, it found nothing wrong this time, not even the previously misplaced file.

I remember previous BSOD's were seemingly caused by Windows media player, hence why I switched to Winamp and never returned. Although I can play DVD's in WMP fine, it seemed to not like playing music, but this only accounted for 2/3 BSOD's many many months ago, but it was possibly video drivers.

The fan on my GPU always starts on full, and is very loud. It sounds like the bearings are misaligned or worn. This full fan behaviour started many months ago, which I think was from an nVidia patch. But after a few minutes the fan goes to idle speed and even during intense gaming does not create any unusual noises, but obviously you can hear it spin faster.

After the full ChkDsk I let it idle on the desktop with nothing running, other than the Steam splash screen in its pre-login state. I came back to the computer some 20 mins later to find it at the password screen, so it had clearly BSOD even while idling on the desktop. This suggests to me a hardware fault, but I don't want to jump to conclusions. I am going to try the same desktop idling in safe mode, to see if its a sound/video driver.

I will try tonight to firstly select minidumps, and secondly run the tool. Bear in mind I have maybe 5 minutes uptime max for some boots, so some more time-consuming suggestions are very hard to perform.

How many BSOD's is sensible before I should just start removing pieces of hardware? I don't want to unnecessarily corrupt a working HDD if that component is fine.

P.S. I found my OEM Win7 disk, so a reinstall would be easy, but I'm guessing not necessary if it's a hardware fault.

Ben

 

[benjamins]

Here are the minidumps


Thanks in advance,
Ben

 

[aritra2116]

Thanks for the files. Will get a BSOD professional shortly. Hope you get your problem fixed in time

 

[Arc]

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
____________________________________________

BugCheck A, {28, 2, 0, fffff80003119d80}
[COLOR=Red]
Probably caused by : memory_corruption[/COLOR] ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
---------

BugCheck 1E, {ffffffffc0000005, fffff800030ff150, 0, ffffffffffffffff}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiReplenishPageSlist+c0 )

Followup: MachineOwner
---------

 

[benjamins]

Thanks, will do.

Apologies for having a zip file with so many minidumps in it. It put them all in there, including the ones from over a year ago!

Obviously only the most recent 5 or so are relevant.

If it's just RAM sticks I'll be very happy, probably one of the easier things to replace. I still get kind of nervous opening up a tower though.

 

[Arc]

If it's just RAM sticks I'll be very happy, probably one of the easier things to replace. I still get kind of nervous opening up a tower though.

There is a chance, but nothing can be said with certainty without doing the test.

 

[aritra2116]

Also try this : SFC
Log in to your account as an Administrator and go to the start button, type in cmd in the search box and right click on the result and Run as Administrator. In the elevated cmd window, type SFC /SCANNOW and press enter. Let it run until it scan to the end. You may also try this in safe mode with command prompt as the cmd window directly appears and then just key in SFC /SCANNOW there.

 

[Britton30]

Also try this : SFC
Log in to your account as an Administrator and go to the start button, type in cmd in the search box and right click on the result and Run as Administrator. In the elevated cmd window, type SFC /SCANNOW and press enter. Let it run until it scan to the end. You may also try this in safe mode with command prompt as the cmd window directly appears and then just key in SFC /SCANNOW there.

There is a tutorial for that, easier than typing it out.

This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#post14392

   Note

If after 2 runs there are still corrupt files, it won't fix it. I can ask for further help if so.

You may get this result:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair, if so rerun the steps above.

 

[benjamins]

Thanks greatly for the suggestions. I've downloaded memtest and should be able to run it over the weekend at some point. So I'll do that first.

Without tempting fate, I've had my pc on for 5 hours last night with no issues, and briefly today. All I've done is literally poke at some wires inside to check they're not loose, and clean the fan filters as they were very full of dust. The inside is pretty dust-free, so the filters at least do one job correctly. Also I've taken my headphones out of the front headphone socket, as I'm using them elsewhere for the first time.

I have a minor issue, non-fatal, with my sound card fairly often. About 1 boot in 20 the sound card just doesn't initialize, but I don't know if this is relevant for any of my BSOD. Do RAM sticks overheat? I know that's a pretty stupid suggestion, but humour me

If I have time to put a little stress on the RAM, GPU etc over the weekend, I'll play some games, and post a BSOD if another comes up. Are modern computers/RAM that sensitive to slightly high temperatures?

Cheers,
Ben

 

[aritra2116]

Also try this : SFC
Log in to your account as an Administrator and go to the start button, type in cmd in the search box and right click on the result and Run as Administrator. In the elevated cmd window, type SFC /SCANNOW and press enter. Let it run until it scan to the end. You may also try this in safe mode with command prompt as the cmd window directly appears and then just key in SFC /SCANNOW there.

There is a tutorial for that, easier than typing it out.

This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#post14392

   Note

If after 2 runs there are still corrupt files, it won't fix it. I can ask for further help if so.

You may get this result:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair, if so rerun the steps above.

Thanks for the suggestion Gary. Will always do this next time whe helping others
And Ben, you said that you had a lot of dust in there so it is usual to have high temps.

 

[benjamins]

So a mini update.

Unfortunately I did not have time to run memtest over the weekend, was busier than expected!

I had a few BSOD during the weekend, almost all the stop codes this time were either A or 1A. Yesterday I had my pc running for over 10 hours straight until right at the end of the day when I closed down Firefox. Firefox 'closed unexpectedly' as I minimized a flash video and then the BSOD happened about 1 second later.

This was after I updated to the most recent nVidia driver in the morning. I tried to update my sound card drivers, but there have been no new ones for years for a lot of the SoundBlaster range.

I'm guessing A and 1A mean I've got a bit of a RAM stick faulty somewhere, but I'll try and find time for the proper diagnostics. If it runs OK this evening I'll post the latest few minidumps.

 

[Britton30]

Yes please run memtest86+ exactly as in the tutorial.
Some other hardware tests to run.

Graphics card test:
Video Card Stress Test with Furmark ​

Hard drive(s)test(s):

Pick one for your HDD brand or use Seatools.
7 Free Hard Drive Testing Software Tools​

RAM (memory) test:

This will require memtest on a bootable CD or USB stick.
RAM - Test with Memtest86+

Did you do the SFC scan?​

This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html#post14392

   Note

If after 2 runs there are still corrupt files, it won't fix it. I can ask for further help if so.

You may get this result:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair, if so rerun the steps above.

 

[benjamins]

I have just done three successive SFC scans, and it came up clear. I am now going to try windows memory diagnostic.

 

[benjamins]

Here are the latest minidumps.

I also ran windows memory checker and it came up blank, but only after 2 runs. I checked my BIOS and I can't see a USB boot option, so I might need to go find a RWCD for memtest.