New
#21
Well i see there's another nvidia update so will have to see if that fixes everything.
Well i see there's another nvidia update so will have to see if that fixes everything.
Please note, MSI software is known for causing BSODs. Software from many laptop/motherboard manufacturers are known for causing BSODs, like ASUS and Gigabyte.
In the situation of BSODs I would always recommend a temporary removal of the software.
I mean i'm not getting persistent bsod's with everything, it seems so far limited to fallout 4 and only during the dpc latency spikes.
I'll keep it in mind. I think i've read usually people having bsod with mobo utilities are mostly because of the overclocking software.
Not only due to the overclocking features, but also other features like reading voltages, temperatures, fan rates, etc. (IME)
Huh really? TIL, does that mean utilities like GPU-Z or coretemp which monitor temps when active can as well? The only msi app i'm using at the moment is the live update tool and some kind of usb speed up so possibly safe in that regard.
All programs that use a driver in non-paged pool could cause a BSOD for some reason, laptop/motherboard manufacturer software are just very well known for it.
Hmm it looks like i just got the exact same odd fps drop+audio buzzing in the overwatch, completely at random while in the main menu.
Reinstalled drivers for realtek hd audio and DDU installed the newest Nvidia drivers, got a bsod upon the first restart after DDU uninstalled the drivers in safemode. The drivers seem to have uninstalled/installed just fine though.
On Wed 10/12/2016 2:43:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-4703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x19 (0x22, 0xFFFFBC8074E52000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Last edited by BobLeSaget; 11 Oct 2016 at 21:50.
This says nothing useful when it comes to finding the cause.....
Upload a new zip from the DM Log Collector.On Wed 10/12/2016 2:43:41 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-4703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x19 (0x22, 0xFFFFBC8074E52000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.