Chronic BSOD Windows 7 upgrade

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Home Premium
       #1

    Chronic BSOD Windows 7 upgrade


    Hi all - thanks for your help. I recently upgraded from Vista to Windows 7 Home Premium (64bit). All is well except when I try to copy&paste/move/delete anything from c: or c:/program files. Each instance results in the same BSOD: BAD_POOL_HEADER. Error code starts with: 0x19.
    Is this an admin rights issue ? I don't see this for anything outside of c:/..

    I've been considering reinstalling Windows 7 Upgrade, but I'm afraid I'll lose my data.

    Any help is greatly appreciated.
    Ryan
      My Computer


  2. Posts : 846
    Windows 10 Pro
       #2

    r22hawk said:
    Hi all - thanks for your help. I recently upgraded from Vista to Windows 7 Home Premium (64bit). All is well except when I try to copy&paste/move/delete anything from c: or c:/program files. Each instance results in the same BSOD: BAD_POOL_HEADER. Error code starts with: 0x19.
    Is this an admin rights issue ? I don't see this for anything outside of c:/..

    I've been considering reinstalling Windows 7 Upgrade, but I'm afraid I'll lose my data.

    Any help is greatly appreciated.
    Ryan
    Hi and welcome.
    It seems that your pool header is corrupted from the install.
    Here is a MSN link but it doesn't say much.
    LINK


    How much memory do you have?

    The only suggestion that may work before considering a reinstall is to open the DOS command prompt "CMD" Run as Admin and type
    sfc /scannow

    This scan key files and actually will repair them it it finds any incorrect.
    Try this and then we can move on to other ideas.

    If you can you can send a copy of your minidump file.

    Anyone else have any suggestions?
      My Computer


  3. Posts : 7
    Windows 7 Home Premium
    Thread Starter
       #3

    Thanks for the quick reply Iggy. I have 4gb of memory. I ran scannow and it did not find any integrity violations. My minidump file (memory.dmp) is very large (448mb), is there a specific portion you're interested in ?

    Thanks again.
    Ryan
      My Computer


  4. Posts : 846
    Windows 10 Pro
       #4

    r22hawk said:
    Thanks for the quick reply Iggy. I have 4gb of memory. I ran scannow and it did not find any integrity violations. My minidump file (memory.dmp) is very large (448mb), is there a specific portion you're interested in ?

    Thanks again.
    Ryan

    WOW!
    If it is that large I'm not sure. Can someone suggest next step for r22hawk?
      My Computer


  5. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #5

    Hello,

    Its actually read the Memory Dump which used to be huge. I will show you how to set the Minidump so we have have a look at it

    1. Click Start, point to Settings, and then click Control Panel.
    2. Double-click System.
    3. Click the Advanced tab, and then click Settings under Startup and Recovery.
    4. In the Write debugging information list, click Small memory dump (64k).
    Once its setup wait for the crash once you get the crash check under C:\Windows\Minidump folder

    Hope this helps,
    Captain
      My Computer


  6. Posts : 7
    Windows 7 Home Premium
    Thread Starter
       #6

    Thanks Captain. Here's my minidump file post-bsod. Couldn't upload .dmp so changed the extension. Let me know if this doesn't work, I'll be sure to check back in case there's something else I can do. Thanks for your help...
      My Computer


  7. Posts : 10,200
    MS Windows 7 Ultimate SP1 64-bit
       #7

    Capt Jack,
    My system shows 128 KB as minidump size rather than 64 kb.

    Is there a difference in the minidump size for different Win 7 versions?

    Makes absolutely no difference, I'm just curious.
      My Computer


  8. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #8

    r22hawk said:
    Thanks Captain. Here's my minidump file post-bsod. Couldn't upload .dmp so changed the extension. Let me know if this doesn't work, I'll be sure to check back in case there's something else I can do. Thanks for your help...
    Hello,

    I guess the problem is with MPRIFL.SYS which belongs to Folder LockBox uninstall it and see whether that makes any difference. Download Malwarebytes and run a complete scan to make sure it clean. Make sure all the drivers are up to date. Uninstall any third party Antivirus / Firewall installed in your system and see whether that makes any difference. Check whether you have any BIOS updates


    Run the Memory Diagnostic & HD Diagnostic

    Also i would recommend to run System Integrity Checker
    Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW
    Update the following Driver

    Code:
    purendis.sys Thu Jan 03 06:09:32 2008
    pnarp.sys    Tue Apr 01 14:14:59 2008
    Bugcheck Analysis

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000020, a pool block header size is corrupt.
    Arg2: fffffa8009a09000, The pool entry we were looking for within the page.
    Arg3: fffffa8009a09a10, The next pool entry.
    Arg4: 0000000004a10000, (reserved)
    Debugging Details:
    ------------------
    
    BUGCHECK_STR:  0x19_20
    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af0e0
     fffffa8009a09000 
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  explorer.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002faa6d3 to fffff80002e78f00
    STACK_TEXT:  
    fffff880`06ded628 fffff800`02faa6d3 : 00000000`00000019 00000000`00000020 fffffa80`09a09000 fffffa80`09a09a10 : nt!KeBugCheckEx
    fffff880`06ded630 fffff880`011170d6 : fffffa80`08a7d010 fffffa80`043a4cc0 fffffa80`656e6f4e fffffa80`09a09010 : nt!ExFreePool+0xda4
    fffff880`06ded6e0 fffffa80`08a7d010 : fffffa80`043a4cc0 fffffa80`656e6f4e fffffa80`09a09010 fffffa80`043a4cc0 : MPRIFL+0x60d6
    fffff880`06ded6e8 fffffa80`043a4cc0 : fffffa80`656e6f4e fffffa80`09a09010 fffffa80`043a4cc0 fffffa80`08a7d010 : 0xfffffa80`08a7d010
    fffff880`06ded6f0 fffffa80`656e6f4e : fffffa80`09a09010 fffffa80`043a4cc0 fffffa80`08a7d010 00000000`00000004 : 0xfffffa80`043a4cc0
    fffff880`06ded6f8 fffffa80`09a09010 : fffffa80`043a4cc0 fffffa80`08a7d010 00000000`00000004 fffff800`03179477 : 0xfffffa80`656e6f4e
    fffff880`06ded700 fffffa80`043a4cc0 : fffffa80`08a7d010 00000000`00000004 fffff800`03179477 00000000`00000004 : 0xfffffa80`09a09010
    fffff880`06ded708 fffffa80`08a7d010 : 00000000`00000004 fffff800`03179477 00000000`00000004 fffff800`0319d080 : 0xfffffa80`043a4cc0
    fffff880`06ded710 00000000`00000004 : fffff800`03179477 00000000`00000004 fffff800`0319d080 fffffa80`06c40010 : 0xfffffa80`08a7d010
    fffff880`06ded718 fffff800`03179477 : 00000000`00000004 fffff800`0319d080 fffffa80`06c40010 fffffa80`043a4d58 : 0x4
    fffff880`06ded720 fffff800`0316f50f : fffffa80`0496dc10 00000000`00000000 fffffa80`03f5bb10 00000000`00000001 : nt!IopParseDevice+0x5a7
    fffff880`06ded8b0 fffff800`03174876 : fffffa80`03f5bb10 fffff880`06deda30 fffffa80`00000040 fffffa80`039dcf30 : nt!ObpLookupObjectName+0x32f
    fffff880`06ded9b0 fffff800`0317b587 : fffffa80`0494b800 00000000`00000001 00000000`00000001 00000000`078f73b0 : nt!ObOpenObjectByName+0x306
    fffff880`06deda80 fffff800`031942a4 : 00000000`078c5b78 fffff880`00060080 fffff880`06dedb60 00000000`0d59d590 : nt!IopCreateFile+0x2b7
    fffff880`06dedb20 fffff800`02e78153 : fffffa80`08f16b60 fffff880`06dedca0 00000000`0d59d5f8 fffff880`06dedbc8 : nt!NtOpenFile+0x58
    fffff880`06dedbb0 00000000`77b101ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0d59d558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b101ea
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    MPRIFL+60d6
    fffff880`011170d6 ??              ???
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  MPRIFL+60d6
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: MPRIFL
    IMAGE_NAME:  MPRIFL.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  46c74f24
    FAILURE_BUCKET_ID:  X64_0x19_20_MPRIFL+60d6
    BUCKET_ID:  X64_0x19_20_MPRIFL+60d6
    Hope this helps,
    Captain
      My Computer


  9. Posts : 846
    Windows 10 Pro
       #9

    The Captain always saves the ship.
    Thanks
      My Computer


  10. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #10

    IggyAZ said:
    The Captain always saves the ship.
    Thanks
    No problem It's Captain's duty :)
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:51.
Find Us