locked
Blue screen issue: Windows 7 - Newly built system RRS feed

  • Question

  • I just built a new system and it keeps randomly crashing. Every time i get the blue screen it is the same error report. This is the info that the error report is giving me. Any help would be greatly appreciated.

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.256.48
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    50
      BCP1:    FFFFF87FFF58BBE4
      BCP2:    0000000000000008
      BCP3:    FFFFF87FFF58BBE4
      BCP4:    0000000000000005
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\030212-24148-01.dmp
      C:\Users\JEH\AppData\Local\Temp\WER-49280-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt


    • Edited by Hulse88 Friday, March 9, 2012 12:37 AM
    Friday, March 9, 2012 12:36 AM

Answers

  • Hi,

    Following is the information in your *dump files.

    Please uninstall the BitDefender AVC and run Microsoft Security Essentials for testing. Update BIOS and other hardware drivers to the latest.

    Boot the system to clean boot environment and then try again: 

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    http://support.microsoft.com/kb/929135

    Hope that helps.

    • Marked as answer by Arthur Xie Friday, March 16, 2012 8:42 AM
    Monday, March 12, 2012 9:05 AM

All replies

  • STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
    Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, AntivirusDevice driver, NTFS corruption, BIOS.

    You need to upload your minidump(s) to Skydrive in a Public folder and post the link back here. C:\Windows\Minidump\030212-24148-01.dmp <-- copy the file(s) to your Desktop then upload them.

    Friday, March 9, 2012 6:55 AM
  • ok i uploaded the minidumps to a public folder on sydrive so i think you should be able to see them all from this link. LMK if you want the full specs of my pc.

    https://skydrive.live.com/redir.aspx?cid=2dfb038d89dbd55d&resid=2DFB038D89DBD55D!103&parid=2DFB038D89DBD55D!101&authkey=!ALqFZzRQTBiW1xw

    Friday, March 9, 2012 3:18 PM
  • Uninstall this: AODDriver2.sys AMD Overdrive; also in EasyTune6 for Gigabyte motherboard http://game.amd.com/us-en/drivers_overdrive.aspx <--- Most likely suspect if the problem is a driver!

    Uninstall BitDefender <-- blamed in one dump. Install Microsoft Security Essentials for testing.

    Update this: AtiPcie.sys ATI PCIE Driver for ATI PCIE chipset or ATI PCI Express (3GIO) Filter http://support.amd.com/us/Pages/AMDSupportHub.aspx

    Update this: RTL8187.sys Realtek networking driver http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2

    ===================================================================================================

    Debug session time: Sat Mar 3 03:53:08.441 2012 (UTC + 0:00) System Uptime: 0 days 0:20:00.627 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d8996076ff, b3b7465eebdd4665, fffff80003410770, 1} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d8996076ff, Reserved Arg2: b3b7465eebdd4665, Reserved Arg3: fffff80003410770, Failure type dependent information Arg4: 0000000000000001, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003098640 STACK_TEXT: fffff880`033cb5d8 00000000`00000000 : 00000000`00000109 a3a039d8`996076ff b3b7465e`ebdd4665 fffff800`03410770 : nt!KeBugCheckEx STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80003410e88 - nt!PfVerifyScenarioBuffer+718 [ 0f:0d ] 1 error : !nt (fffff80003410e88) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption ---------

    =================================================================================================

    Debug session time: Thu Mar  8 18:03:05.224 2012 (UTC + 0:00)
    System Uptime: 0 days 0:00:27.410
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff880011a2e94, fffff88006e24d10, 0}
    
    Probably caused by : avc3.sys ( avc3+56e94 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff880011a2e94, Address of the instruction which caused the bugcheck
    Arg3: fffff88006e24d10, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    avc3+56e94
    fffff880`011a2e94 c700ffffffff    mov     dword ptr [rax],0FFFFFFFFh
    
    CONTEXT:  fffff88006e24d10 -- (.cxr 0xfffff88006e24d10)
    rax=000000000000004c rbx=0000000000000049 rcx=000000000000006c
    rdx=000000000000ffff rsi=000000000000003a rdi=000000000000000b
    rip=fffff880011a2e94 rsp=fffff88006e256f0 rbp=000000000000000c
     r8=fffffa80097cc5a8  r9=000000000000006c r10=0000000000000000
    r11=fffff88006e25838 r12=000000000000006c r13=0000000000000069
    r14=00000000fffffff4 r15=fffff88006e25800
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    avc3+0x56e94:
    fffff880`011a2e94 c700ffffffff    mov     dword ptr [rax],0FFFFFFFFh ds:002b:00000000`0000004c=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  bdagent.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880011a2e94
    
    STACK_TEXT:  
    fffff880`06e256f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : avc3+0x56e94
    
    
    FOLLOWUP_IP: 
    avc3+56e94
    fffff880`011a2e94 c700ffffffff    mov     dword ptr [rax],0FFFFFFFFh
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  avc3+56e94
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: avc3
    
    IMAGE_NAME:  avc3.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f34f2e2
    
    STACK_COMMAND:  .cxr 0xfffff88006e24d10 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_avc3+56e94
    
    BUCKET_ID:  X64_0x3B_avc3+56e94
    
    Followup: MachineOwner
    ---------

    ==================================================================================================

    If the BSOD's continue after doing the above, test all hardware as outlined on the following page: http://www.carrona.org/hwdiag.html

    Friday, March 9, 2012 4:02 PM
  • Hi,

    Following is the information in your *dump files.

    Please uninstall the BitDefender AVC and run Microsoft Security Essentials for testing. Update BIOS and other hardware drivers to the latest.

    Boot the system to clean boot environment and then try again: 

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    http://support.microsoft.com/kb/929135

    Hope that helps.

    • Marked as answer by Arthur Xie Friday, March 16, 2012 8:42 AM
    Monday, March 12, 2012 9:05 AM