BSOD while using Google Chrome(?)

Ragnar · 10 Nov 2016

Hello everyone, I hope You can help me with my problem regarding a new PC I bought. It got 2 BSODs in between a few days and it seems both happened while using Google Chrome, but I'm not really sure if that's the cause or something else. I did some hardware testing after the first BSOD (Memtest and such) but hardware didnt come up with any errors.

Now on the first BSOD I was initially blaming Avira and Windows Defender for it but I have Windows Defender off now and only one is active. The next BSOD happened somewhat randomly after a PC Shutdown (I was putting a new Table cover so I had to shutdown the PC to take the monitor out of the way and such. Then after booting up and running Google Chrome, searching for why my Headphones only have 1 sound (Left ear)... The page fully loaded and then after a little while (not more than a minute of the page fully loading) The Chrome window showed "Oh Snap" and then everything froze and I got the BSOD. This same thing happened IIRC on the first BSOD.

Not sure if that's really the cause or if it's just a coincidence but here is the Data I got from both BSODs, I hope someone can help me with this problem, thanks in advance!

Also I forgot to mention I just inserted a new keyboard and headset before that BSOD... Don't know if it matters or if it caused the BSOD though.

Ragnar · 15 Nov 2016

Just a small update, I got another BSOD after a few minutes right after I cold boot my PC again. I don't get any BSODs if I leave it on sleep mode, or just restart. A shutdown almost guarantees it.
==================================================
Dump File : 111516-4421-01.dmpCrash
Time : 15/11/2016 7:59:54 PM
Bug Check String : BAD_POOL_CALLERBug
Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00a8f201
Parameter 4 : ffff818f`47469af0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a510
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14a510
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111516-4421-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 536,940
==================================================

axe0 · 16 Nov 2016

Hi Ragnar,

Welcome to the 10forums, and apologies for the delay.

Please upload a new zip from the DM Log Collector.

Ragnar · 17 Nov 2016

axe0 said:

Hi Ragnar,

Welcome to the 10forums, and apologies for the delay.

Please upload a new zip from the DM Log Collector.

Thanks! Here's the one for the new one.

axe0 · 18 Nov 2016

See if disabling fast startup helps
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

Ragnar · 20 Nov 2016

axe0 said:

See if disabling fast startup helps
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

Wow, that did it I think, before doing that, I always get those random BSOD's everytime I shutdown the PC, even when I just shut it down and open in in less than a minute or so. What does the Fast Startup do to cause the BSODs though? Is it something on Microsoft's part or some incompatibilities with some installed software?

axe0 · 20 Nov 2016

For the working of fast startup read the tutorial, you need to understand how it works before you can properly understand why it could cause BSODs.

The next BSOD happened somewhat randomly after a PC Shutdown

We know that a BSOD occurred after you shutdown the PC.
The BSOD is a 0xC2 stating that something attempted to release memory which was already free.
We know that fast startup saves an image of the kernel to the hibernation, my guess is that all loaded drivers also take with them their memory allocation references (memory descriptor list or MDL) so when Windows starts they can quickly resume from where they left.
What I guess happened was that fast startup failed to properly save the image of the kernel, all drivers lost the MDL. Because fast startup is enabled Windows attempts to load the image fast startup should've saved properly, the drivers use their MDL to get back to what they were doing and there it goes wrong. The system has a certain view about the memory allocations with fast startup that the drivers use, but not knowing the true state of the memory some of them perform improper actions causing problems.

I honestly am not sure if everything I described truly is how it works, but as mentioned it is a guess.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000000000, (reserved)
Arg3: 0000000000a8f201, Memory contents of the pool block
Arg4: ffff818f47469af0, Address of the block of pool being deallocated

System Uptime: 0 days 0:02:27.201


Event[1493]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2016-11-15T20:14:28.720
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Exelica
  Description: 
Windows failed fast startup with error status 0xC00000D4.