On Wed 12.11.2014 17:42:17 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\111214-15046-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0xBE (0xFFFFFA80015CC790, 0x8000000003C80121, 0xFFFFD00020C3E2E0, 0xA) Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY having same issue :P The power management thing worked well. But to be honest, I dont think that the change of RAM will solve my bsod .... Specs: 4690k stock 980ti EVGA acx+ ASUS... have a peek here
BSOD - Kernel 41...Need help please! I assisted my Aunt with an upgrade to Windows 10 and now her machine is having this problem as well. I also reverted all my bios settings.I think I have a driver problem. Event Xml:
There are two sets of RAM slots, A1 and A2. On Wed 12.11.2014 17:29:09 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\111214-14843-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801FCF0FE74, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED BSOD Crashes and Debugging Reboot error message "kernel security check failure"Please help.
When my Toshiba Satellite L655 laptop was rebooted I got the above error. I found in the forum the solution to update the mouse driver, I have done it but without succsess. I'm in a moment of my life where I can't afford spending money on new parts right now without knowing exactly what the problem is. You try something but don't see any difference.
Anyways, My computer would randomly restart during and out of ... I have built my first computer this week but I have encountered a persistent problem. The crash took place in a standard Microsoft module. http://www.tomshardware.com/answers/id-2136885/solving-kernel-power-error.html Did you try compressed air in the socket?
The system will ask for a RESTART, you should now do so. hop over to this website Back to top #7 scot Posted 29 December 2016 - 09:10 PM scot Faithful poster Members 1,620 posts Hello, so just wanted to give an update I changed the hardrive today very much for your input. Downloaded the whocrashed program, I can show you the result, mostly the ntoskrnl.exe is the reason, see above.
There is a proper order which should be observed when you uninstall the NVIDIA drivers. http://anyforgeek.com/bsod/bsod-i-really-need-help.html Let me know if I'm missing anything. Place the mouse pointer over the driver you want to uninstall, this will highlight the choice. On Wed 12.11.2014 17:26:56 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\111214-20109-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14F1A0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8029D368884, 0x0, 0x9EE79B72) Error: KMODE_EXCEPTION_NOT_HANDLED
The crash took place in the Windows kernel. BSOD Crashes and Debugging BSOD error 0x124, kernel power while playing games after 1-2 hoursHello, I have been having problems with Kernel power error. Family and loved ones will always be a priority in my daily life. http://anyforgeek.com/bsod/bsod-xp-sp2.html I recently got this problem again ( 2 months ago) and I found that the power socket thingy (that has more sockets to plug in more things) was the problem.
w/o additonal RAM moduls - there is no dump anymore. But I tried two separate PSU's from corsair both 80+ bronze. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Event Viewer shows the "Kernel-Power 41 (63)" error. Internet Speed: Carrier Pigeon Speed Browser: ie11/Chrome/firefox/Opera/edge Antivirus: ESET and Mbam Pro Other Info: Asus Z77 Maximus V Extreme-i7-3770K-16 GB DDR3-2400-EVGA GTX 780 CASSIFIED- 2X Samsung 256 Gb 840 Pro- Samsung The crash took place in the Windows kernel. http://anyforgeek.com/bsod/bsod-10d.html Microsfot-windows-kernel-power event id 41 BSOD need help :( Started by scot , Dec 28 2016 01:39 PM kernel-power bsod gaming Please log in to reply 7 replies to this topic #1
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.