Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Constant BSODs


  • Please log in to reply
1 reply to this topic

#1 Sacchan

Sacchan

  • Members
  • 37 posts
  • OFFLINE
  •  
  • Local time:06:47 PM

Posted 07 October 2014 - 07:49 PM

It started maybe a few weeks to a month ago that I started getting random BSODs. I thought maybe it was just a software issue so I decided to format my computer. But then, it still kept happening. A friend told me it might be the video card I have, so I uninstalled it and just used the original onboard video output (vga output). I thought this had fixed it, but the blue screens still keep happening.

 

So far, in my dump file, there are three files. I will post them.

 

10/05/14 @ 2:45PM

 

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 84d642a0, The pool entry we were looking for within the page.
Arg3: 84d64330, The next pool entry.
Arg4: 0812000a, (reserved)

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

GetPointerFromAddress: unable to read from 829a284c
Unable to read MiSystemVaType memory at 82981f00

BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 829a284c
Unable to read MiSystemVaType memory at 82981f00
 84d642a0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 828d258b to 82959c6b

STACK_TEXT:  
807d5b78 828d258b 84d642a8 00000000 84c3dd48 nt!ExFreePoolWithTag+0x1b1
807d5b88 828c147d 807d5c38 84d642a8 869fc6e8 nt!CcDeallocateBcb+0x1e
807d5ba8 828fface 00000001 00000000 00003000 nt!CcUnpinFileDataEx+0x2ce
807d5bdc 828c0e6a 84d34378 00003000 00000000 nt!CcReleaseByteRangeFromWrite+0x12a
807d5c70 828c3ddc 86b59670 00000000 00000001 nt!CcFlushCache+0x423
807d5ca8 828d2737 807d5cc4 a111834f 84c26a10 nt!CcWriteBehind+0x105
807d5d00 828b614b 84c26a10 00000000 84c3dd48 nt!CcWorkerThread+0x164
807d5d50 82a42141 00000000 a11183df 00000000 nt!ExpWorkerThread+0x10d
807d5d90 828e9559 828b603e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+1b1
82959c6b cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExFreePoolWithTag+1b1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53158c8f

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x19_20_nt!exfreepoolwithtag+1b1

FAILURE_ID_HASH:  {ff1544f5-2057-d61e-52bb-deaa8d4afef0}

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

 

10/05/14 @ 2:54PM

 

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00000005, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8293587b, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP:
nt!ExDeferredFreePool+21b
8293587b 397b04          cmp     dword ptr [ebx+4],edi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

DPC_STACK_BASE:  FFFFFFFF8078B000

TRAP_FRAME:  807859c4 -- (.trap 0xffffffff807859c4)
ErrCode = 00000000
eax=859f19b0 ebx=00000001 ecx=000001ff edx=00000000 esi=859f16e8 edi=859f16f0
eip=8293587b esp=80785a38 ebp=80785a70 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210297
nt!ExDeferredFreePool+0x21b:
8293587b 397b04          cmp     dword ptr [ebx+4],edi ds:0023:00000005=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8293587b to 82854b7f

STACK_TEXT:  
807859c4 8293587b badb0d00 00000000 00000000 nt!KiTrap0E+0x1b3
80785a70 8293535f 8294a6c0 00000000 84c0fcc0 nt!ExDeferredFreePool+0x21b
80785ad8 828a7804 85db9008 00000000 84c0fcc0 nt!ExFreePoolWithTag+0x8a4
80785af4 899403b1 85db9008 80785ba0 85c671d0 nt!IopFreeIrp+0x65
80785b0c 89940732 85c671d0 00000001 00000000 fltmgr!FltpFreeIrpCtrl+0x47
80785b20 8995afdb 85c67230 80785cec 80785bc4 fltmgr!FltFreeCallbackData+0x1a
80785b30 8998dc2e 85c47e10 85c67230 80785b88 fltmgr!FltQueryInformationFile+0x67
WARNING: Stack unwind information not available. Following frames may be wrong.
80785bc4 8999e10c 85dc2cdc 84c67600 80785c5c MpFilter+0x9c2e
80785c9c 8999faea 00000040 8b829050 80785cc4 MpFilter+0x1a10c
80785cc8 89941324 85c47758 80785cec 00000040 MpFilter+0x1baea
80785d30 89944512 00c476f8 85c476f8 1000000c fltmgr!FltpPerformPostCallbacks+0x24a
80785d44 89944b46 85c476f8 85dbae00 80785d84 fltmgr!FltpProcessIoCompletion+0x10
80785d54 8994529c 859f29f0 85dbae00 85c476f8 fltmgr!FltpPassThroughCompletion+0x98
80785d84 899588c9 80785da4 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a
80785dd0 8284ac1e 859f29f0 859f4638 85dabb7c fltmgr!FltpCreate+0x2db
80785de8 82a5a516 a1c7cca6 80785f90 00000000 nt!IofCallDriver+0x63
80785ec0 82a39d2e 859c2480 84c613f8 85c4ad20 nt!IopParseDevice+0xee6
80785f3c 82a4a157 00000000 80785f90 000002c0 nt!ObpLookupObjectName+0x4fa
80785f98 82a40c35 8078617c 84c613f8 89ae5d00 nt!ObOpenObjectByName+0x165
80786014 82a46dbb 80786198 80000000 8078617c nt!IopCreateFile+0x673
8078605c 828518c6 80786198 80000000 8078617c nt!NtOpenFile+0x2a
8078605c 8284fc0d 80786198 80000000 8078617c nt!KiSystemServicePostCall
807860ec 82e7d165 80786198 80000000 8078617c nt!ZwOpenFile+0x11
80786154 82e7f523 80786198 80786220 8f377a20 CI!CipMinCrypK_OpenFile+0x27
807861a0 82e8141b 807861e4 807861f0 807861f4 CI!I_MapAndSizeDataFile+0x4f
80786218 82e8177e 807862d4 8f3779f0 00000000 CI!I_MapCatalog+0xfb
807862f4 82e818c8 8078631c 807884e9 807864f0 CI!I_ReloadCatalogs+0x22e
80786340 82e81ba2 80786460 00000001 00000001 CI!I_FindFileOrHeaderHashInCatalogs+0xcd
80786378 82e7debd 80786460 00000001 00000000 CI!MinCrypK_VerifyHashInCatalog+0x51
807863e0 82e7eab0 85bce128 80786460 00008004 CI!CipFindFileHash+0xab
807864bc 82e7eecf 85bce128 8ecc0000 0001f000 CI!CipValidateFileHash+0x1d4
80786534 829ecd62 85bce128 8ecc0000 0001f000 CI!CiValidateImageHeader+0x171
80786550 829eca83 85bce128 8ecc0000 0001f000 nt!SeValidateImageHeader+0x4d
807865cc 82a38f79 85bce128 85bdbde0 00000001 nt!MiValidateImageHeader+0x1a4
807866f4 82a382bb 80786748 00000008 80786860 nt!MmCreateSection+0x77f
80786768 828518c6 80786890 00000008 80786860 nt!NtCreateSection+0x16e
80786768 8284f4a1 80786890 00000008 80786860 nt!KiSystemServicePostCall
807867fc 829d97f0 80786890 00000008 80786860 nt!ZwCreateSection+0x11
807868bc 829d6922 8000013c 8295d5b0 84bbd988 nt!MmCheckSystemImage+0x52
80786904 829d96be 80786b30 00000000 80786928 nt!MiCreateSectionForDriver+0x8f
8078692c 829d8fe7 80786998 80786b30 00000000 nt!MiObtainSectionForDriver+0x96
80786930 80786998 80786b30 00000000 80786960 nt!MmLoadSystemImage+0x1d6
80786934 80786b30 00000000 80786960 8078695c 0x80786998
80786998 8b8236d8 003a003a 8b8236d8 80786b9c 0x80786b30
8078699c 003a003a 8b8236d8 80786b9c 00000000 0x8b8236d8
807869a0 8b8236d8 80786b9c 00000000 00000000 0x3a003a
807869a4 80786b9c 00000000 00000000 00000000 0x8b8236d8
8b8236d8 00000000 00000000 00000000 00000000 0x80786b9c


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+21b
8293587b 397b04          cmp     dword ptr [ebx+4],edi

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+21b

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18409

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+21b

BUCKET_ID:  0xC5_2_nt!ExDeferredFreePool+21b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc5_2_nt!exdeferredfreepool+21b

FAILURE_ID_HASH:  {e6575ec4-3885-288b-127b-fe52d60e1ff2}

Followup: Pool_corruption

 

10/07/14 @5:12PM

 

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 852e9960, The pool entry we were looking for within the page.
Arg3: 852e99f0, The next pool entry.
Arg4: 0812000a, (reserved)

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

GetPointerFromAddress: unable to read from 829a684c
Unable to read MiSystemVaType memory at 82985f00

BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 829a684c
Unable to read MiSystemVaType memory at 82985f00
 852e9960

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from 8289e142 to 8295dc6b

STACK_TEXT:  
9cbbcb84 8289e142 852e9968 00000000 82a651f6 nt!ExFreePoolWithTag+0x1b1
9cbbcb90 82a651f6 852e9968 852e9990 00000000 nt!MiDeleteControlArea+0x2d
9cbbcbbc 8289ec5a 852e9968 82967d20 852e9990 nt!MiSegmentDelete+0x1ce
9cbbcbe8 8289e2cb 852e9968 9e490f00 9e490f58 nt!MiCheckControlArea+0x202
9cbbcc08 82a5fb84 852e9968 00000000 84b5c940 nt!MiDereferenceControlAreaBySection+0x87
9cbbcc2c 82a5f7d9 852e9968 9e490f58 9e490f40 nt!MiSectionDelete+0x103
9cbbcc44 828b5200 00000000 8539e008 8539e04c nt!ObpRemoveObjectRoutine+0x59
9cbbcc58 828b5170 9e490f58 828c8caa 00000000 nt!ObfDereferenceObjectWithTag+0x88
9cbbcc60 828c8caa 00000000 8539e008 8502e410 nt!ObfDereferenceObject+0xd
9cbbcc78 828c83ec 00000001 8502e410 84f1cb40 nt!CcDeleteSharedCacheMap+0xc4
9cbbcca8 828d6737 9cbbccc4 bd47ee71 84b45e38 nt!CcWriteBehind+0x715
9cbbcd00 828ba14b 84b45e38 00000000 850ec518 nt!CcWorkerThread+0x164
9cbbcd50 82a46141 80000000 bd47eee1 00000000 nt!ExpWorkerThread+0x10d
9cbbcd90 828ed559 828ba03e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+1b1
8295dc6b cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExFreePoolWithTag+1b1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53158c8f

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+1b1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x19_20_nt!exfreepoolwithtag+1b1

FAILURE_ID_HASH:  {ff1544f5-2057-d61e-52bb-deaa8d4afef0}

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

 

Does anyone know what I can do? Or anyone know what the exact problem is and how to fix it so that I can use the video card I had originally bought?

 

 

 

 

 

 



BC AdBot (Login to Remove)

 


#2 Aberrant

Aberrant

  • Members
  • 40 posts
  • OFFLINE
  •  
  • Local time:09:47 AM

Posted 07 October 2014 - 08:19 PM

From what I had encountered lately with BSOD that has a "BAD_POOL_HEADER" and "IRQ" errors was mainly caused by a defective RAM. Though the culprit may vary from pc to pc knowing the hardware/parts differs from one another. Chances also that you might have installed a defective driver perhaps, have you installed the updated drivers of your system?

How many sticks of RAM are you using? If you got more than one stick of RAM then try to insert just a single stick and observe if you will still get any BSOD, this is somewhat common that one of your RAMs is defective.


Edited by Aberrant, 07 October 2014 - 08:21 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users