ntoskrnl.exe BSOD Randomly every few days

Your card will most likely never see the stress put on it by Furmark, so it will probably never see those temps. If it does, however, yes it could be the reasons for the BSODs. I seriously doubt it will though. Furmark is designed to run your card as hard as possible. But, in my opinion you did the correct thing. The rep on the AMD series has been the run excessively too hot, with the reference cooler. Some have come out with custom cooling which makes them much cooler.

If you have a utility that came with your card, I would use it and set a custom fan profile and run it with the fan speed increased considerably. If you don't have a utility to do that you can use MSI Afterburner which is primarily an overclocking utility, but allows a custom fan profile. I have it in another rig and have not overclocked that card, but I do use it for a custom fan profile and monitoring.

Try this and see what difference it makes. Download Ungine Heaven 4.0 Run it with the basic preset and see how hot it gets. If it seems to do OK, run it again after the card cools down with the Extreme preset. It has a benchmark function if you want to use it.

I would suggest you watch your Graphics card and CPU temps any time you are doing anything stressful with them. I set mine for on screen display which tells me, among other things, the temp and fan speed of my card when gaming.

I can't look at the logs for a couple of hours or so as I'm at work, but I'll take a look when I get home if essenbe hasn't beaten me to it.

Sorry, the files basically show the Generic Hardware error and identifies the CPU, which I seriously doubt that is the issue. If you are overclocked, please set everything back to default levels, at lest for testing until we can get to the bottom of this. Please run more the tests Boozad laid out in Post #2.

Next I would like you to run memtest86+. It is quite a long test as it needs to be run for 8 complete passes all at the same time. Please download the test from Memtest86+ - Advanced Memory Diagnostic Tool. Although the names are similar, this testis much better than memtest86. It needs to be run for 8 complete passes or until you get an error. If you get an error, stop the test. In the link above if you will go down to the middle of the page you can download either the ISO file which needs to be burned to a CD by Windows image burner or any disk image burner you choose. Or you can download the auto installer for USB Flash drives to run it from a flash drive. Whichever you choose, be sure to download the zip file and extract it. Each Pass consists of 10 tests, each pass checks a different thing and each Test checks different things. It takes a minimum of 8 passes to completely check the ram, more passes are better. It will take quite a number of hours to do the test, so it is usually better run over night. To run the test, boot from the media you chose and don't press any keys, the test will run automatically and will continue running until you tell it to stop. It will tell you how many passes it has run and how many errors are found. If it finds errors they will show up as red lines at the bottom of the page. It will take somewhere around 9-10 hours to check my Backup computer with 8 GB of ram. If you have more it will take much longer.

So far that's just the memory that's run the complete test, yes? Run Prime95 next to test your CPU, then Furmark or Unigine to test your GPU, then run the HDD diagnostics. It's definitely a hardware problem but with 0x124s it's virtually impossible to tell exactly what it is from the logs.

Please explain. What you are describing is a restart of the computer and not a classic BSOD. BOODs (Blue Screen of Death) is when the screen turns blue and text appears telling you a bunch of stuff. Like this

Attachment 323052

Is that what you are getting or something else? Basically, all we are getting in the dumps is a generic hardware fault 0X124. That just says your CPU has detected a defective piece of hardware and has shut down. It can however be caused by a driver, but in the vast majority of the cases it is hardware. Normally if it is a driver, one of the dump files will list a driver. If you have had any since your last upload please go to C:/Windows/Minidump and open it (you will have to give admin permission several times) Copy the last ones (the numbers are dates and times) copy the ones you haven't uploaded and paste them to your desktop, highlight them, right click and select send to >compressed zip folder. Then using the paperclip icon, upload the zip folder with your next post.

Next, Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, please go into bios and give us the reading of the +12V, +5V and +3.3V.

The only way I can think to force a problematic driver out into the open is to run Driver Verifier. It's worth a shot seeing as all hardware tests have turned nothing up.

Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable

Enable Driver Verifier but only enable these options:
Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

   Warning

Make a System Restore point before enabling Driver Verifier.

   Note

Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.