Kernel 41 error

[Soloz]

Specs

Built in late February this year.

Windows 7 pro 64 bit
Asus maximum vii hero mobo
Intel i7 4790k 4.0- 4.4 turbo(Corsair H100i cooler)
Asus GTX970 strix(default OC)
Cruxial mx100 512g 2.5'' SSD
Seagate barracuda 3TB 7200rpm SATA III HDD
16g corsair vengeance pro ram(4x4g) 2400
Corsair AX760 PSU

I have been getting the kernel 41 error where the pc shuts down then powers back on a second or two later since Sunday the 12th. It has only happened while in a game. The first crash was while I was playing DayZ and it had been probably about an hour or two in the current session before it crashed. It didn't crash at all after that until I got GTA V and after about 10 minutes in game it crashed. It has been crashing all week ever since then after some time in GTA. The most recent crash my pc froze and I had to manually restarted it.

I've checked my temperatures while in game and my CPU never goes above 50 c and my GPU sits around 65 c. My ram temps after a crash were at 60 c (not sure what a stable temp is for ram). I've checked all plugs into the case and there were two that were just slightly loose so I fixed those and still got crashes. I had recently installed the HDD so I thought maybe that had something to do with it and unplugged it, but still got a crash. Made sure there were no audio conflicts, there were 4 in the device manager but only my headset audio drivers run(I also tried disabling one at a time, but yet again a crash). I set my ram speed to its default 1333 and it seemed to help but still got a crash. I ran a Memtest for 13-14 hrs and there were no errors.

The only thing that helped the most was changing my power settings to high performance instead of balanced which let me play for around 2 hours one night before I went to bed. The next day played for around 2 hours again until it crashed.

Things I think it could be is a faulty PSU, bad wall plug/surge protector, or possible error in voltages? The usb plugs on the front of my case don't seem to work so maybe that is connected to the problem?

I'm all ears for anyone that has some suggestions.

 

[alexoiu]

As it looks like a power issue, try testing different power supply (if possible), or RMA yours.

 

[Mysticking32]

Because it was working correctly before, I'm thinking it has something to do with your video drivers. Have you installed the newest and latest ones that are compatible with gta5? They were recently released. Try uninstalling your current drivers (even if they are the latest) and downloading fresh drivers from their website and installing it.

More than likely should fix your problem.

 

[Soloz]

Mysticking32, I had gotten a crash a day before Gta was released. I'll try to reinstall the drivers to see if it helps though, but I can't even fully test to see if I get crashes from Gta anymore cause the game just crashes every 15 minutes (Gta has stopped working). Last night I had heavens benchmark running for a few hours and didn't experience a crash.

I have had 2 BSOD though over over the past few days, One was a afd.sys error(KMODE_EXCEPTION_NOT_HANDLED), and the other was a win32k.sys error(SYSTEM_SERVICE_EXCEPTION). The second one after research I think it was due to a windows update I had done, don't know about the the first one though. Both happened while playing GTA, but have only happened once so far.

 

[Soloz]

Update - I tried updating my BIOS and reinstalling windows. Played the game for a bit but the computer froze and had to reboot it.

 

[Soloz]

So the pc freezing crash looks like its something to do with Gta in particular, but not the other crash I was getting. I actually haven't gotten the full crash and reboot since I reinstalled windows so I'll keep my fingers crossed for now.

 

[Soloz]

Have still yet to get the original crash I was getting. Looks like reinstalling windows did the trick.

 

[LouieChapman]

Could you play GTA then after reinstalling windows?

I am getting exactly the same Crashes but on windows 8.1.

Specs;

i7 4770 - 3.4Ghz
Asus Z97M Plus
Gtx 770 2 GB
PSU 650

GTA V ran perfectly up until the first up date, i had the The 350.7 driver already installed and the game ran perfectly at 60 FPS. Then it crashed, restarted event 41 error and crashed 6 more times, i reinstalled the driver, verified my files on steam and it ran fine for another week until now were it crashes upon entering the game, restarts event 41 every time.

I have tested other games, Battlefield/Pillars of eternity for example on high settings and no crashes so it seems its a GTA related problem...

I also tried restoring graphics settings, checked all my drivers, I had tested the ram a few weeks ago and all was fine, malware scans, starting in safe mode, checked temps which were normal and i am in the process of reinstalling the game.

Any help/advice would extremely appreciated.

 

[Soloz]

So my problem has shifted from powering off and restarting to the pc freezing requiring a reset. When it crashes I hear the audio cut out and then the display freezes. So far this crash has only happened while having my ram in its xmp profile (2400mhz 1.65v) in both Gta and DayZ(takes longer to crash in DayZ). I'll have to run another Memtest and see if anything pops up this time.

Louie the reinstall did stop the kernel crashes, but as I said above I have a freeze problem now.

 

[Mysticking32]

Are you overclocking your ram or gpu? If so, don't. Undo those overclocks and then test. It's more than likely the gpu is going bad. I can't see it being anything else besides the ram or maybe the power supply.

Try underclocking your gpu from the default OC to something lower.

 

[Soloz]

So far I haven't had a freeze since having the ram set at 1333mhz and 1.5v and I only had put the ram at 2400mhz because that's its advertised speed since by default it was set up at 1333mhz. Although its possible I have a hard time thinking the gpu is going bad because its the second card I had to get(first one was defective). I'm going to run a Memtest tonight and most of tomorrow to see if an error pops up.

 

[Mysticking32]

you can also test each ram stick individually to help eliminate defective ones faster. After that that leaves the psu, since this is your second card

 

[Soloz]

I had originally thought it was the psu when I was getting the crashes that would restart my pc, but that hasn't happened since I reinstalled windows, only the freezing now. If I ran Memtest with all 4 sticks in it would still give me an error right? I would just need to test individually after to figure out which one?

 

[Docto]

There is a good solution on you tube for this error. Basically you set up your own power plan. Hard drive never shuts off and sleep mode and all the other hibernate etc should be never or off. Then download msi afterburner hit the general tab and check all of the boxes. Use kernel mode and msi standard then restart.

 

[Soloz]

Memtest showed 9 errors in test 13. Time to found out which stick is bad.

 

[Soloz]

test 13 is the hammer test

" The Hammer Test is designed to detect RAM modules that are susceptible to disturbance errors caused by charge leakage. This phenomenon is characterized in the research paper Flipping Bits in Memory Without Accessing Them: An Experimental Study of DRAM Disturbance Errors by Yoongu Kim et al. According to the research, a significant number of RAM modules manufacted 2010 or newer are affected by this defect. In simple terms, susceptible RAM modules can be subjected to disturbance errors when repeatedly accessing addresses in the same memory bank but different rows in a short period of time. Errors occur when the repeated access causes charge loss in a memory cell, before the cell contents can be refreshed at the next DRAM refresh interval.

The errors detected during Test 13, albeit exposed only in extreme memory access cases, are most certainly real errors. During typical home PC usage (eg. web browsing, word processing, etc.), it is less likely that the memory usage pattern will fall into the extreme case that make it vulnerable to disturbance errors. It may be of greater concern if you were running highly sensitive equipment such as medical equipment, aircraft control systems, or bank database servers. It is impossible to predict with any accuracy if these errors will occur in real life applications. One would need to do a major scientific study of 1000 of computers and their usage patterns, then do a forensic analysis of each application to study how it makes use of the RAM while it executes. To date, we have only seen 1-bit errors as a result of running the Hammer Test. "

I assume the gaming I due triggers the error that occurs in the hammer test which causes the freeze.

Yesterday while gaming(ram at 1333 mhz) I had my task manager open to monitor my cpu and memory usage and I think there is a memory leak cause it looked like my used memory was slowly climbing the longer I played and not dropping until I would close the game. This would happen faster while set at 2400 mhz correct? Which I assume is why I haven't gotten a freeze at 1333 mhz since I would have to be gaming for a much longer period.

Also, should I just test each stick on test 13 since that was the only test giving me errors or should I do all tests?

 

[Soloz]

So I just finished testing each stick individually through only the hammer test. Each one had an error in the first slot so I put the first stick into every other slot and tested and still got the error. Then I took the second stick and put it in different slots and tested and still got the error. I didn't test the last two sticks in every slot though just the first slot since I'm very sure they will still get the error. The errors would consistently pop up around the halfway mark through the test until I changed the speed from 2400 mhz to 1333 mhz where the errors would not pop up until the first pass had finished.

Can something else be causing the errors to pop up on the memtest? I can't help but think something else is causing this since things were fine for a while and all the sticks are getting the same error. Or I am just that unlucky that all 4 are defective?

 

[Soloz]

Got the new ram couple days ago and things ran smooth until today when I got the lock up and then reboot. When it restarted it couldn't load windows so it went to the boot menu, because it didn't detect my SSD. Shutting it completely down and then powering back up got it to detect the SSD though. Man this is irritating.