Bug Check String: BAD_POOL_CALLER
Bug Check Code: 0x000000c2
Parameter 1: 00000000`00000007
Parameter 2: 00000000`000011f0
Parameter 3: 00000000`0407001e
Parameter 4: ffffe000`0b025b70
Caused by Driver: USBSTOR.SYS
Caused by Address: USBSTOR.SYS+3c78
Processor: x64
Crash Address: ntoskrnl.exe+150da0
Processors Count: 8
Major Version: 15
Minor Version: 9431

This is the details of my lastest dmp file.  The main problem is when ever i try to insert USB Flash Disk, my pc goes to BSOD.

It started to appear when I installed Windows 8.1 Preview

This problem does not apply to Mass Storage from Phones, Cameras and in built Memory Card readers.

A bugcheck (BSOD) is a mechanism to protect your PC from damage.

You get this one:

Bug Check 0xC2: BAD_POOL_CALLER

http://msdn.microsoft.com/en-us/library/ff560185%28v=vs.85%29.aspx

The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad pool request.
 

To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

Andr

[1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
[2] http://support.microsoft.com/kb/254649
[3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
[4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
[5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
[6] http://support.microsoft.com/kb/315263

http://sdrv.ms/159USKn

here is the link for minidump archive

The Intel Storage Driver is the cause. Update the Driver please:

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

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 11f0, 407001e, ffffe0000b025b70}

*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys
GetPointerFromAddress: unable to read from fffff803b4bc8150
GetUlongFromAddress: unable to read from fffff803b4bc8208
Probably caused by : iaStorF.sys ( iaStorF+131e )

Followup: MachineOwner
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 00000000000011f0, (reserved)
Arg3: 000000000407001e, Memory contents of the pool block
Arg4: ffffe0000b025b70, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS:  ffffe0000b025b70 Nonpaged pool

FREED_POOL_TAG:  RstF

BUGCHECK_STR:  0xc2_7_RstF

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre

LAST_CONTROL_TRANSFER:  from fffff803b4b0d336 to fffff803b49c5da0

STACK_TEXT:  
nt!KeBugCheckEx
nt!ExDeferredFreePool
iaStorF
0x0
0x0
0x0
0x0
0x0
iaStorF
0x0
0x0
0x0
0x0



IMAGE_NAME:  iaStorF.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f5e319f

FAILURE_BUCKET_ID:  0xc2_7_RstF_iaStorF+131e

BUCKET_ID:  0xc2_7_RstF_iaStorF+131e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc2_7_rstf_iastorf+131e


        
    Loaded symbol image file: iaStorF.sys
    Image path: \SystemRoot\System32\drivers\iaStorF.sys
    Image name: iaStorF.sys
    Timestamp:        Mon Mar 12 18:25:51 2012 

I just got stuck with an idea that it was USBSTOR.SYS

But anyway the problem is fixed now, downloaded new version of Intel Rapid Storage Technology driver and software. Although for some reason it failed to update the drivers so I had to do it manually. I achieved it through replacing iaStorA.sys and iaStorF.sys file from C:\Windows\System32\Drivers from f6flpy-x64.zip file downloaded from Intel's website (as my system is x64)

But I did one mistake and I went through series of trouble, this process is not a solution, just sharing my experience

To remove old driver and thinking after restart windows will ask me to install new ones, I deleted iaStorA.sys and iaStorF.sys file from C:\Windows\System32\Drivers

Then my pc failed to start, BSOD all the time but I went to Advance Troubleshoot > Command Prompt and copied those two files from extracted f6flpy-x64.zip (i was lucky that i had it extracted) to C:\Windows\System32\Drivers

Anyway the drivers were replaced :D and PC is working fine now.

 the drivers were replaced :D and PC is working fine now.