BSOD out of nowhere


  1. Posts : 2
    Windows 7 Professional x64
       #1

    BSOD out of nowhere


    I have been having random blue screens for a while now. I would be just browsing the web then bsod. Sometimes I even get bsod when turning on the computer.

    My observations:
    No memory in page file will not give any "page fault in nonpaged area" blue screen.
    But it still gives other blue screens.

    Putting memory in paging file gives the "page fault in nonpaged area" or sometimes "memory management" blue screen.

    My OS is installed on a SSD and everything else (games, other software) is on HDD.

    Other thoughts: Lately I've also been getting problems when trying to install a game. Cannot copy file because source is corrupted. Is this related to the blue screen?

    Thank you


    Edit: Just had another BSOD saying "page fault in nonpaged area" while running sfc /scannow on safe mode.
    Last edited by xHazardx; 05 Nov 2012 at 20:42. Reason: New bsod info
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hello xHazardx.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {3, fffff8a00afbbee0, fffff8a00afbbee0, fffff8cc0afbbee0}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
    
    Followup: Pool_corruption
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000003, the pool freelist is corrupt.
    Arg2: fffff8a00afbbee0, the pool entry being checked.
    Arg3: fffff8a00afbbee0, the read back flink freelist value (should be the same as 2).
    Arg4: fffff8cc0afbbee0, the read back blink freelist value (should be the same as 2).
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_3
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  TrustedInstall
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8000300b70f to fffff80002ee0fc0
    
    STACK_TEXT:  
    fffff880`077f1728 fffff800`0300b70f : 00000000`00000019 00000000`00000003 fffff8a0`0afbbee0 fffff8a0`0afbbee0 : nt!KeBugCheckEx
    fffff880`077f1730 fffff800`0300d1a1 : fffffa80`09ed9660 fffff8a0`0afcd3a0 00000000`00000754 fffffa80`0a706890 : nt!ExDeferredFreePool+0xcbb
    fffff880`077f17c0 fffff800`031d88bd : fffffa80`0a706890 fffffa80`0a006800 00000000`6d4e624f fffffa80`06707c00 : nt!ExFreePoolWithTag+0x411
    fffff880`077f1870 fffff800`031d9efc : fffffa80`0a0f1640 00000000`00000000 fffffa80`0a0f1601 ffffffff`ffffffff : nt!ObOpenObjectByName+0x5cd
    fffff880`077f1940 fffff800`031e4b54 : 00000000`0098cc78 fffff8a0`00120089 00000000`0098cca0 00000000`0098cc90 : nt!IopCreateFile+0x2bc
    fffff880`077f19e0 fffff800`02ee0253 : ffffffff`ffffffff 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtCreateFile+0x78
    fffff880`077f1a70 00000000`7763186a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0098c7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7763186a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+cbb
    fffff800`0300b70f cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!ExDeferredFreePool+cbb
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: Pool_Corruption
    
    FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
    
    BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
    
    Followup: Pool_corruption
    ---------
    In such a situation, it is better to enable Driver Verifier to monitor the drivers.

    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

    Let us know the results, with the subsequent crash dumps, if any.

    Also, uninstall Daemon Tools. It is one of the most well known BSOD causers.
      My Computer


  3. Posts : 2
    Windows 7 Professional x64
    Thread Starter
       #3

    I ran memtest and found that 1 ram stick had errors. I temporarily removed it and am going to conduct another test using memory diagnostic from cnet to reach a solid conclusion. So far, no bsod after removing the bad memory.
      My Computer


 

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 02:41.
Find Us