BSOD during random times, error 0x00000109

ThePoena · 22 Aug 2015

Hi, this is a post that has to do with an old issue I've been having. I made a thread I believe about a year and a half ago, but since it's been so long and I think some things are a bit different now I thought I'd make a new thread.

Alright, so I will first say that I reformatted my PC and installed a newer BIOS and drivers to try and fix this problem. In the file I uploaded you might see a BSOD with a error code of 0x0000000A, but that's not the one I'm really concerned about (I think it was due to not restarting my PC right as I finished installing Avast, and there was another antivirus I had before I reformatted my PC that made my computer really slow when it finished installing until I restarted my PC. It seems that at least for my computer antivirus programs cause problems until you restart your computer at least once.) The one I'm concerned about is the one with error 0x00000109. I've been getting this one for at least a year now at seemingly random times, and I barely have anything on my computer as of now so I'm thinking that it could be a hardware problem. I have tested my RAM with RAM diagnostic programs and found no problems with it. Also, one of the fan slots on my motherboard gives weird speed readings if I set it to anything other than disabled fan control. I'm fine with the disabled setting, but I wanted to give this info just in case it could give some help on finding out what's causing the BSOD.

I'd also like to add that my computer just shut down and restarted without a BSOD. In the event viewer it says it was a critical level event and it has no error code (it's just 0). There is also an error level event that occurred 3 seconds later that says, "The previous system shutdown at 7:07:14 PM on ‎8/‎22/‎2015 was unexpected."

I just got a new BSOD with an error code of 0x00000024 at about 12:00 UTC 8/26/15 on.

I just received another new BSOD with an error code of 0x00000109 at about 9:30 UTC 8/26/15. I have replaced the previous crash info folder with one I just got after running the program after I got the BSOD.

Laith · 01 Sep 2015

Hey there!

Code:

BugCheck 109, {a3a039d89eb5f7cc, b3b7465ef132c722, fffff80002412e6b, 1}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+2f390 )

Run Furmark, if the temps goes too high stop the test. Video Card - Stress Test with Furmark

Run MemTest86+, It must be MemTest86+. RAM - Test with Memtest86+

Run SeaTools(DO NOT RUN FOR SSDS) SeaTools for DOS and Windows - How to Use

Run Prime95, if the temps goes too high stop the test. Hardware - Stress Test With Prime95

Reinstall Windows and see if that works.

ThePoena · 01 Sep 2015

Thanks for the recommendations, but I went ahead and ordered a new motherboard because I believe my current one is messed up. My internet connection on the PC completely shut off randomly while I was using the computer and I can't get it back. It won't even see my router anymore, it's completely blind. I connected another computer to the same Ethernet cable and the internet works fine on it, so it's something on my pc.. I'm thinking it's the motherboard because that's where the LAN chip is at. Hopefully this new motherboard will solve the other BSODs as well.

Laith · 02 Sep 2015

I have my fingers crossed.