New
#1
BSOD when basically idle, bad_pool_caller ntoskrnl.exe
Timeline:
31/08/2016 - Computer black screen's buzzing sound. Restart, no problem for the rest of the day. Wasn't doing anything stressful.
1/09/2016 - Same as above
2/09/2016 - Same as above
4/09/2016 - Same as above but instead of restarting immediately, I waited for the sound to stop by itself. Minidump created, Bug check string: IRQL_NOT_LESS_OR_EQUAL, Bug check code: 0x0000000a. Used Driver verifier, minidump shows:
BAD_POOL_CALLER and 0x000000c2. Keeps driver verifier on, 3 bsods in 10 minutes. Decided to remove RAM. Removes 1 of 2 8gb sticks, Get IRQL_NOT_LESS_OR_EQUAL error before I can even log in on win10. Remove other ram, exact same thing happens. Places both RAM both in, so far no BSOD's but I feel it's just a matter of time.
The 3 initial black screens were when my computer was in basic to complete idle. Was on netflix or reddit.
BSODs : minidump.rar - Google Drive
I've tried using winDBG, only shows:
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\090416-4625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.545.amd64fre.th2_release.160802-1857
Machine Name:
Kernel base = 0xfffff801`ff406000 PsLoadedModuleList = 0xfffff801`ff6e3cf0
Debug session time: Sun Sep 4 21:42:10.257 2016 (UTC + 1:00)
System Uptime: 0 days 0:02:12.920
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
............
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {62, ffffd00070184000, ffffd0007018400c, 3b}
Thank you in advance.
UPDATE: Just read the posting instructions, Attachment 99871