Randdom BSOD error 0x19


  1. Posts : 2
    Win 7 64bit
       #1

    Randdom BSOD error 0x19


    I normally try to figure things out on my own but for the life of me i cant seem to pin down this bsod.

    I downloaded Bluescreenview to see what was causing the bsod.

    It claims Procexp141.sys caused the bsod along with ntoskrnl.exe+1a8cae. While I once had processexplorer I no longer have it installed and the driver is no where to be found in my system.

    Any help is greatly appreciated

    attached is one of my latest dmp
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    MSINFO32:
    Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter (you can also press Win and R at the same time to open the Run dialog - then type in msinfo32.exe and press Enter)
    Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
    Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

    If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
    Your BSOD seems to be caused by Driver Description: Sysinternals Process Explorer. Please remove this software to see if the BSOD's stop. Driver Reference Table - PROCEXP141.SYS

    Revo Uninstaller

    Download and install Revo Uninstaller free from here: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

    Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {20, fffff8a0030b2bf0, fffff8a0030b2c70, 508022d}
    
    *** WARNING: Unable to verify timestamp for PROCEXP141.SYS
    *** ERROR: Module load completed but symbols could not be loaded for PROCEXP141.SYS
    Probably caused by : PROCEXP141.SYS ( PROCEXP141+1363 )
    
    Followup: MachineOwner
    ---------
    BUGCHECK_STR:  0x19_20
    
    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b6100
    GetUlongFromAddress: unable to read from fffff800034b61c0
     fffff8a0030b2bf0 Paged pool
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  avgrsa.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800033b1cae to fffff8000327ec00
    
    STACK_TEXT:  
    fffff880`096d7638 fffff800`033b1cae : 00000000`00000019 00000000`00000020 fffff8a0`030b2bf0 fffff8a0`030b2c70 : nt!KeBugCheckEx
    fffff880`096d7640 fffff880`09f1e363 : 00000000`00000040 00000000`00000000 fffffa80`58637250 00000000`00000004 : nt!ExDeferredFreePool+0x12da
    fffff880`096d76f0 00000000`00000040 : 00000000`00000000 fffffa80`58637250 00000000`00000004 00000000`00000000 : PROCEXP141+0x1363
    fffff880`096d76f8 00000000`00000000 : fffffa80`58637250 00000000`00000004 00000000`00000000 00000000`00000000 : 0x40
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    PROCEXP141+1363
    fffff880`09f1e363 ??              ???
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  PROCEXP141+1363
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: PROCEXP141
    
    IMAGE_NAME:  PROCEXP141.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4db5bb3d
    
    FAILURE_BUCKET_ID:  X64_0x19_20_PROCEXP141+1363
    
    BUCKET_ID:  X64_0x19_20_PROCEXP141+1363
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm PROCEXP141
    start             end                 module name
    fffff880`09f1d000 fffff880`09f28000   PROCEXP141 T (no symbols)           
        Loaded symbol image file: PROCEXP141.SYS
        Image path: \??\C:\Windows\system32\Drivers\PROCEXP141.SYS
        Image name: PROCEXP141.SYS
        Timestamp:        Tue Apr 26 00:19:41 2011 (4DB5BB3D)
        CheckSum:         00013D01
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Security App

    Also remove AVG antivirus if you have it and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

    Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

    Microsoft Security Essentials, Free antivirus for windows

    Malwarebytes Anti-Malware Free


       Information
    DO NOT start the free trial of MalwareBytes. Deselect the option when prompted. Make full scans with both separately.

    Please run these tests and report back the results

    1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
    2. Disk check for errors on the hard drive - Disk Check
    3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
    4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
    5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

    Next time you get a BSOD "Grab all" and upload.
      My Computer


  3. Posts : 2
    Win 7 64bit
    Thread Starter
       #3

    Finally got a chance to run some of these tests.

    First of all i see that my post wasnt fully read. I said i understood what the error pointed to and tryed multiple ways of fully removing it. The driver folder doesnt have that file,the program is not installed( btw the program doesnt install to begin with.

    As for the other steps listed i did uninstall AVG( im still fond of it lol) and malawarebytes found PUP.funmoods

    Used a few online recommendations to remove it and the BSODs seemed to have stopped ( going on 12 hours no BSOD yet)

    AS for the sfc /scannow it did fix items but still had a bsod
    memtest 86 did 7 passes with no errors
    diskcheck also didnt stop the bsod

    I didnt run the HDD test or troubleshoot test

    The bsod are very random they can be 6 hours from startup time or even 30 mins but so far so good.

    And about the grab all is all that really necessary? im not fond of uploading info about my pc without knowing what its used for

    Either way thanks for the help
      My Computer


  4. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #4

    There is no personal info stored on the files that we look at to see what is causing your BSODs .
      My Computer


 

  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 23:14.
Find Us