Random constant BSOD

[vashla]

Ok so lately my computer has been having an excess of BSOD’S. The only thing event viewer tells me is the generic event Id 41. This tells me nothing! I have attached the diagnostic results and could use your help.

 

[koolkat77]

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

• Create a Dump File when you get a BSOD

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

 

[vashla]

I have had this set up for a while now but it never gets any dump information because the computer locks up then I get the bsod as windows tries to restart. most look like this. The lock up first then the bsod. On the lock up picture I was playing saints row the 3 and the game looks like that is was not a graphical crash.

https://www.dropbox.com/s/7fwbrt14vxx2mhm/2013-08-24 19.58.25.jpg

https://www.dropbox.com/s/7fwbrt14vxx2mhm/2013-08-24 19.58.25.jpg

 

[essenbe]

If you would, Please fill out your system specs as detailed as possible. (http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html) To see what we want, at the bottom left of this post, look at mine. It helps us to help you if we know what hardware we are dealing with. we'll know more about how to help you once we see your system specs. Is it alsway while gaming that you have BSODs or are there other things that cause them?

 

[vashla]

Ok I updated my profile.

 

[vashla]

Also it Will happen when ever it feels like it. I can be gaming, surfing the web, watching a movie, or just staring at my desktop. I dose seem to happen in fits. I can go months with no problems then one day I contently crash. I cant seem to replicate a crash. There is no particular game or up time that I can cause the problem on queue.

 

[essenbe]

What power, brand and model PSU do you have and how old is it? Could you go into your bios and give me the readings on the +12V, 3.3V and +5V. Also, do you have monitoring programs for your GPU and CPU? If so, what ate the temps running and especially the temps when it crashes. Are you running the stock Intel CPU cooler? As I recall from reviews, that CPU runs pretty hot.

 

[vashla]

I do have temp monitoring program I use core temp for my cpu normal idle temps are 35c-40c heavy lode(80% and up) is around 60c-70c.I use precision for my gpu and the temps are normal 45c and heavy lode 70c-80c. I have them open on my 2nd monitor to see the temps when I lock up and they very depending on what I am doing when I crash. As I said before I crash randomly so the temps are in the above ranges when I crash. my psu is a thermaltake tr2 rx 750AH3ch. I will restart and post my bios readings.

 

[vashla]

This is my Bios voltages. And I am using an after market cpu fan it is a ZALMAN CNPS9900ALED 120mm

 

[essenbe]

The voltages look OK, at idle. As for the PSU, the issue is what they put out under stress which there is very little way to tell. CPU temps sound OK, for a chip like yours, the GPU temps sound slightly high, I think for a 560 TI. The card should be able to take those temps, but in my opinion 80C is pushing the limit. Maybe you could add some air flow to your case and set a custom fan profile with Precision X. That is what I do with my card and it will help a lot.

Also, did you follow Koolkat's instructions for creating a small memory dump? Make sure the minidump file is there or create one. It would really help if we had some debugging info to direct us to what the problem is. Without that we are going to have to proceed as if it was a hardware problem, which is may very well be. If you did and still are not getting memory dumps, go further down in the tutorial She linked to and use the regedit file posted there to make sure the registry knows to create the dump.

To troubleshoot hardware problems, is very time consuming and can take a lot of hours. I know very well what a pain it is. I have been there myself several times. Lets start with running memtest86+. Follow the link in the tutorial which will lead you to memtest86+. Be sure to get the + version. There are 2 companies which make the test, memtest86 and memtest86+. The + version is, in my opinion, the best and most accurate. It needs to run for 8 passes and will probably take quite a few hours. Each pass consists of 10 tests, each testing something different. Each pass tests a different thing also, so it takes 8 passes to do a complete test. If you get errors during the test you can stop it, the test has failed. It is best to run the test overnight. This should explain how to run the test. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Also, if you have anything overclocked, set everything back to default values. Also, please download and install Ungine Heaven Basic edition (free). It is a graphics card benchmark and will really push your graphics card. Be sure and set on screen monitoring in Precision to show at least the GPU temps and fan speed. Set a fan profile before you run the test.
If you don't already have it, download and install CPUz and post screenshots of the Mainboard tab, memory tab, CPU tab and the SPD tab.

 

[vashla]

Ok I am running the memtest86+ now. I know that the temps are a little high and I do have a custom fan curve with Precision X. The problem is that i live in Southern California and lately its been over 90 in my room, My case has excellent air flow the problem is there is no cool air to be found.

 

[vashla]

Here are the cpuz Shots.

 

[essenbe]

In your bios, don't you have an XMP option? You should. If you do it manually, set your 1st ram timings to 9-9-9-24 2T, set your ram frequency to 1600 (800) however it is listed and your Dram Voltage to 1.65V. If you set XMP, it should do that for you, but check it anyway and set the dram Voltage manually. I'm not sure what your ram is doing. It has timings for roughly 1200 but it is running at 1068; your ram is manufactured as 1600 MHz. But you can run it slower with no problems if it is set right. I'm thinking the voltage is not correct.

If you have not already, go to Asus web Site and update your drivers. You have the latest Bios update.

Also, make sure you have the latest drivers from Nvidia web site. If you don't, download them and let me tell you how to update them. Use the latest WHQL drivers.

I'm really not that familar with the X58 boards, so if I tell you something that does not sound right, don't hesitate to ask me. I don't get my feelings hurt that easily and do not mind explaining at all.

 

[vashla]

The memtest86+ results are in all is well. Also I changed the memory clocks as you suggested after the tests were completed. they were at 8-8-8-20 now there set to 9-9-9-24 at 1600(800).

 

[vashla]

Also here are some pictures of some bsods they are all mostly the same the most recent being today I can see it tried to make an mini dump but i never saw a counter or % just ...

 

[vashla]

On a side note lately I have been having and odd thing happening after I restart after a crash. Windows logged in and I see my desktop and the normal programs starting up like they should. However before I hear the window log in tune it locks up I can control the mouse but nothing responds. Sometimes if I am fast I can get the Taskmaneger to open before it locks up and I see 0% cpu usage and when I try to force close a proses the command prompt locks up as well. This then repeats on every start up unless I do one of 2 things. I can do a system restore and I will boot up fine until the next crash. Or I can run windows in safe mode open msconfig and change a random non-essential program to either start on start up or not. It does not seem to matter what I change but then I restart and it boots up just fine. If I didn’t explain this in good enough detail I can make a video showing the problem.

 

[koolkat77]

That's a hardware error. Similar to 124's.

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try