- Jul 14, 2017
- 2
- 0
- 510
Not able to login on my main user account. But am able to login to my 2nd account on the same computer without any changes to any settings. Tried different solutions online like updating bios and underclocking RAM but still no solution (Even overclocked RAM works on my 2nd Account).
After using WhoCrashed to check my dump files, found out it was caused by the windows NT kernel and System.
Detailed info here-
crash dump file: C:\WINDOWS\Minidump\071417-5843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x19 (0x20, 0xFFFFD60EECCF3B38, 0xFFFFD60EECCF4358, 0x348276E0)
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.
Minidumps - https://1drv.ms/f/s!Ao1I2GITFmsviCRZWvmg1fGMHdDu
Help me guys, am stuck!!!!
Note: no new hardware was installed recently and the error started happening by itself today.
After using WhoCrashed to check my dump files, found out it was caused by the windows NT kernel and System.
Detailed info here-
crash dump file: C:\WINDOWS\Minidump\071417-5843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x19 (0x20, 0xFFFFD60EECCF3B38, 0xFFFFD60EECCF4358, 0x348276E0)
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.
Minidumps - https://1drv.ms/f/s!Ao1I2GITFmsviCRZWvmg1fGMHdDu
Help me guys, am stuck!!!!
Note: no new hardware was installed recently and the error started happening by itself today.
Facebook
Twitter
Instagram