Dear trix trix,
Thank you for posting to the forum community. Your XML contains an important clue: Windows recorded a crash, so we should investigate that rather than treat Kernel-Power 41 as the cause.
BugcheckCode 59 is decimal for 0x3B — SYSTEM_SERVICE_EXCEPTION. Its first parameter, 0xC0000094, means integer division by zero. These values do not identify the responsible driver or prove that either graphics adapter caused the crash. Event 41 guidance · Bug check 0x3B. Microsoft Learn
Safe Mode working reliably makes a driver or service loaded during normal startup a reasonable possibility. However, it does not completely rule out hardware or power problems, because Safe Mode uses fewer drivers and a different workload.
Please start with these steps:
- Back up your important files while Safe Mode is working. Then check
C:\Windows\Minidumpfor recent.dmpfiles. A crash dump can help identify the code involved in the failure. Microsoft’s crash-dump guidance. Microsoft Learn - Try a clean boot, following Microsoft’s instructions. Hide all Microsoft services before disabling the remaining services, and temporarily disable startup apps. Record what you disable so you can restore it afterward. Some software features will temporarily stop working. If normal startup becomes stable, re-enable items in groups to isolate the trigger. A clean boot does not disable every third-party driver. Microsoft Support
- If this started immediately after a driver or software update, tell us which one. I would avoid removing both graphics drivers or flashing the BIOS before examining that history and the dump.
Could you provide the exact Windows build from winver, when the problem started, and whether recent minidump files exist? Please don’t post your serial number. Memory dumps can contain sensitive information, so avoid making them publicly accessible.
If this helped, I’d appreciate a Like so others can find the answer more easily.