Crash on new PC Full Crash log zipped and included. Driver related?

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Home Premium 64
       #1

    Crash on new PC Full Crash log zipped and included. Driver related?


    So my new Cyberpower PC is crashing. I think it is a driver issue but this level of detail is beyond by "expertise" basic log below. Full diagnostic attached. Please let me know if additional information is needed.

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

    Additional information about the problem:
    BCCode: 7f
    BCP1: 0000000000000008
    BCP2: 0000000080050031
    BCP3: 00000000000406F8
    BCP4: FFFFF80002EA142F
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\083012-13540-01.dmp
    C:\Users\Jesse\AppData\Local\Temp\WER-15225-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

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


  2. Posts : 8
    Windows 7 Home Premium 64
    Thread Starter
       #2

    Additional Information.


    I ran Memtest x86 no errors. I also made sure my video card drivers were up to date. No changes. Anybody know what the stuff in the zip files means?
      My Computer


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

    For how many passes?

    Your dumps do show memory corruption.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 406f8, fffff80002ea142f}
    
    *** 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
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff80002ea142f
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  Gw2.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002e9d769 to fffff80002e9e1c0
    
    STACK_TEXT:  
    fffff800`00ba4d28 fffff800`02e9d769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`02e9bc32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff800`02ea142f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0710d7c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8f
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff80002ea13a2 - nt!SwapContext_PatchXSave+2
    	[ 01:21 ]
        fffff80002ea1486 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    	[ 09:29 ]
        fffff80002ea1642 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
    	[ 01:21 ]
        fffff80002ea1728 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
    	[ 09:29 ]
    4 errors : !nt (fffff80002ea13a2-fffff80002ea1728)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT_LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    Followup: memory_corruption
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff80002ea142f
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  Gw2.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002e9d769 to fffff80002e9e1c0
    
    STACK_TEXT:  
    fffff800`00ba4d28 fffff800`02e9d769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`02e9bc32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff800`02ea142f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0710d7c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8f
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff80002ea13a2 - nt!SwapContext_PatchXSave+2
    	[ 01:21 ]
        fffff80002ea1486 - nt!SwapContext_PatchXRstor+2 (+0xe4)
    	[ 09:29 ]
        fffff80002ea1642 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
    	[ 01:21 ]
        fffff80002ea1728 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
    	[ 09:29 ]
    4 errors : !nt (fffff80002ea13a2-fffff80002ea1728)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT_LARGE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
    
    Followup: memory_corruption
    ---------
    
    0: kd> lmvm memory_corruption
    start             end                 module name
    Start again following the tutorial below & continue for 8 passes at least:
    RAM - Test with Memtest86+

    Run your computer inserting single sticks see which one your comp stays most stable with.
      My Computer


  4. Posts : 8
    Windows 7 Home Premium 64
    Thread Starter
       #4

    7 passes left it on all night. Running it again, will do 8 passes.
    Last edited by Blacshades; 03 Sep 2012 at 04:11. Reason: Going to do 8 passes as suggested.
      My Computer


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

    Tried inserting one stick at a time?
      My Computer


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

    Ran for 8 passes then 4 for reach stick. No errors. I have attached additional crash info with different errors that might hold the key? Perhaps something is else is triggering these "memory" problems.
      My Computer


  7. Posts : 7,466
    Windows 10 Home Premium 64bit sp1
       #7

    SFC/SCANNOW update Bios if there is a Memory fix

    couple options
      My Computer


  8. Posts : 8
    Windows 7 Home Premium 64
    Thread Starter
       #8

    Scannow showed no problems. Will look for Bios Update tomorrow. Looking more and more like this PC may just have to go back if it sill can
      My Computer


  9. Posts : 8
    Windows 7 Home Premium 64
    Thread Starter
       #9

    Bios had latest update already, Same issues. Any other ideas before I box up my PC and send it back? If not thanks for trying, some problems are just to complicated to solve! :)

    Update: Someone suggested a fluctuating power supply? I have an Xtreme Gear 700W ATX. I read they are not the best, but it is new? Are the errors consistent with a bad supply?
    Last edited by Blacshades; 04 Sep 2012 at 17:36.
      My Computer


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

    Before you send it back lets see how your computer performs with driver verifier on

    Its used to rule out buggy drivers, following instructions on the tutorial below:

    Driver Verifier - Enable and Disable
      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:00.
Find Us