"PathOfExile_x64.exe stoped working" CDT & BLUE SCREENS "ntoskrnl.exe"
GTX970, Ryzen9 3900x, 16GB RAM, 3*SSD (system, swap, game)
NO HEAT problem as the GPU is limited to 70° via MSI Afterburner and CPU never reaches 65°+!! DXDiag report
Spoiler
System Information
------------------ Time of this report: 7/5/2020, 02:51:54 Machine name: dummy-name Machine Id: {A1CE7456-D5A5-41F8-8344-F30CD45B8D0C} Operating System: Windows 10 Pro 64-bit (10.0, Build 18363) (18362.19h1_release.190318-1202) Language: German (Regional Setting: German) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: X570 AORUS ELITE BIOS: BIOS Date: 07/02/20 11:19:41 Ver: 05.00011 (type: BIOS) Processor: AMD Ryzen 9 3900X 12-Core Processor (24 CPUs), ~3.8GHz Memory: 16384MB RAM Available OS Memory: 16330MB RAM Page File: 4518MB used, 12834MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: Unknown DxDiag Version: 10.00.18362.0387 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Input Tab: No problems found. WhoCrashed dumpfile analyse
Spoiler
On Sat 04.07.2020 00:22:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070420-8062-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8036A40F9EE, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Spoiler
On Sat 04.07.2020 21:34:12 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070420-7734-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF806690F525D, 0xFFFFB904E2FA95E0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Spoiler
On Mon 29.06.2020 14:04:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062920-8078-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0) Bugcheck code: 0x139 (0xE, 0xFFFFA0862BDB6140, 0xFFFFA0862BDB6098, 0x0) Error: KERNEL_SECURITY_CHECK_FAILURE file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The kernel has detected the corruption of a critical data structure. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Spoiler
On Wed 24.06.2020 03:15:34 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062420-7421-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80372C27FCF, 0xFFFFFC8477516ED0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. Started with PoE 3.11 :(. As much as the GPU overuse started with 3.11! If I do not limit the GTX970 to 70° via MSI afterburner it starts to cook even with all settings MINIMUM and 60 FPS limit/V-Sync @1080p which should NEVER ever be posible! As if PoE is internaly is trying to render everything in 4k without FPS limiter just to trash all unneeded data later on :(. WTF is happening @GGG??? PS: if you need more info PM me Last edited by Schakar on Jul 4, 2020, 9:07:51 PM Last bumped on Jul 5, 2020, 2:08:06 PM
| |
Another one today
crash dump
On Sun 05.07.2020 14:58:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070520-7843-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80519AA589F, 0xFFFFF28520843F10, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. Allready tryed: - ggpk_defragment.exe - PackCheck.exe - delete all DX11/Vulcan ShaderCaches - moved PoE-Folder to another SSD - uninstall and reinstall NVidia Driver / AMD driver / MoBo driver Last edited by Schakar on Jul 5, 2020, 11:24:53 AM
| |
1. this belongs under tech help not bug reports.
2. https://www.auslogics.com/en/articles/fix-ntoskrnl-exe-bsod/ | |
1. READ before post!
Your link is NO HELP at all and just trys to sell me some curios software! Hate to do it but: " So your link to a side witch tells me "your fault, defect driver, blablabla" is USELESS! 2. As it started with 3.11 ... it is a BUG. Maybe a technical but still a BUG. With 3.10 I had no single crash over the hole league! Same with the absurd high heat production of my GTX970. With 3.10 I had "normal" values around 65° WITHOUT UNDER-CLOCKING! Now if I don't throtle the 970 to 53% power (LOL!! REALY??) I have to fear a heat-death of my hole system. And Link to some ADVERTISE-semi-lookalike-pro website ?? "user OUR TOOL you can BUY HERE to fix your problem" ... NO THANKS! BTW: Allready did the ram-check, driver-check, system-check, SSD-check, heat-check. The standart "it is your fault" stuff you know. Well sorry, it is NOT! Or explain to me: why should a driver which worked 100% with 3.10 suddenly have a bug as soon as 3.11 launches? Maybe as 3.11 HAS A BUG?? Last edited by Schakar on Jul 5, 2020, 2:22:25 PM
|