Help with BSOD on brand new computer...

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 7
       #1

    Help with BSOD on brand new computer...


    Hello all,
    I just got my 4th BSOD in the last 3 days. The first 3 came while I was playing Mass Effect 2 and the last one came while I was browsing the internet and listening to music via Itunes.

    I bought the computer parts 2 weeks ago and me and my friend assembled it. It ran fine for the first 1.5 weeks but now I am getting the BSOD and it really worries me.

    I am attaching the last 3 minidumps and any help deciphering them would be greatly appreciated because I have never dealt with the BSOD before.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    dahoover said:
    Hello all,
    I just got my 4th BSOD in the last 3 days. The first 3 came while I was playing Mass Effect 2 and the last one came while I was browsing the internet and listening to music via Itunes.

    I bought the computer parts 2 weeks ago and me and my friend assembled it. It ran fine for the first 1.5 weeks but now I am getting the BSOD and it really worries me.

    I am attaching the last 3 minidumps and any help deciphering them would be greatly appreciated because I have never dealt with the BSOD before.

    These crashes were caused by hardware. use these instructions to find and fix. https://www.sevenforums.com/crash-loc...-what-try.html

    let us know if we can help

    Ken

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\032510-19640-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c44e50
    Debug session time: Thu Mar 25 14:08:55.069 2010 (GMT-4)
    System Uptime: 0 days 0:00:07.364
    Loading Kernel Symbols
    ................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8004e1d8f8, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004e1d8f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02fbd6f0 fffff800`02cc1a89 : fffffa80`04e1d8d0 fffffa80`03a00680 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02fbdc10 fffff800`02ba3547 : fffffa80`04e1d8d0 fffff800`02c1c5f8 fffffa80`03a00680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02fbdc40 fffff800`02b0bb95 : fffff800`02c7e360 fffffa80`04929d18 fffffa80`04929d10 fffffa80`03a00680 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02fbdc80 fffff800`02a86161 : fffff880`00c30e00 fffff800`02b0bb70 fffffa80`03a00680 00000554`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02fbdcb0 fffff800`02d1c166 : 00000554`00000000 fffffa80`03a00680 00000000`00000080 fffffa80`0396e990 : nt!ExpWorkerThread+0x111
    fffff880`02fbdd40 fffff800`02a57486 : fffff880`02d63180 fffffa80`03a00680 fffff880`02d6dfc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fbdd80 00000000`00000000 : fffff880`02fbe000 fffff880`02fb8000 fffff880`035c4540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
      My Computer


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

    dahoover said:
    Hello all,
    I just got my 4th BSOD in the last 3 days. The first 3 came while I was playing Mass Effect 2 and the last one came while I was browsing the internet and listening to music via Itunes.

    I bought the computer parts 2 weeks ago and me and my friend assembled it. It ran fine for the first 1.5 weeks but now I am getting the BSOD and it really worries me.

    I am attaching the last 3 minidumps and any help deciphering them would be greatly appreciated because I have never dealt with the BSOD before.
    Hello Dahoover Welcome to SF,

    I guess there are multiple issues going on. I would recommend to start with basics. If your Overclocking please stop. Make sure your BIOS have the latest firmware. If you using any Antivirus or Firewall uninstall it and see whether that makes any difference.

    https://www.sevenforums.com/crash-loc...-what-try.html

    Hardware Diagnostic

    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:
     asusgsb.sys  Thu Sep 27 18:44:50 2007
    Bugcheck Code

    Code:
     
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004e1d8f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x124_AuthenticAMD
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff880`02fbd6f0 fffff800`02cc1a89 : fffffa80`04e1d8d0 fffffa80`03a00680 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02fbdc10 fffff800`02ba3547 : fffffa80`04e1d8d0 fffff800`02c1c5f8 fffffa80`03a00680 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02fbdc40 fffff800`02b0bb95 : fffff800`02c7e360 fffffa80`04929d18 fffffa80`04929d10 fffffa80`03a00680 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02fbdc80 fffff800`02a86161 : fffff880`00c30e00 fffff800`02b0bb70 fffffa80`03a00680 00000554`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02fbdcb0 fffff800`02d1c166 : 00000554`00000000 fffffa80`03a00680 00000000`00000080 fffffa80`0396e990 : nt!ExpWorkerThread+0x111
    fffff880`02fbdd40 fffff800`02a57486 : fffff880`02d63180 fffffa80`03a00680 fffff880`02d6dfc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fbdd80 00000000`00000000 : fffff880`02fbe000 fffff880`02fb8000 fffff880`035c4540 00000000`00000000 : nt!KxStartSystemThread+0x16
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: hardware
    IMAGE_NAME:  hardware
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
     
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960001b44d3, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88008ef5a30, 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: 
    win32k!DEVLOCKOBJ::vDestructor+4f
    fffff960`001b44d3 4c8b80f8090000  mov     r8,qword ptr [rax+9F8h]
    CONTEXT:  fffff88008ef5a30 -- (.cxr 0xfffff88008ef5a30)
    rax=0000000000000000 rbx=fffff88008ef65a8 rcx=fffff88008ef65a8
    rdx=00ff000000000000 rsi=fffff900c2f58630 rdi=fffff900c00bf010
    rip=fffff960001b44d3 rsp=fffff88008ef6410 rbp=fffff900c0155be0
     r8=fffff900c215dbe0  r9=0000000000000000 r10=fffffa8005a28f80
    r11=fffff900c4c35be0 r12=0000000000000305 r13=0000000000000000
    r14=fffff900c2a73cd0 r15=0000000000000305
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    win32k!DEVLOCKOBJ::vDestructor+0x4f:
    fffff960`001b44d3 4c8b80f8090000  mov     r8,qword ptr [rax+9F8h] ds:002b:00000000`000009f8=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  chrome.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001b44d3
    STACK_TEXT:  
    fffff880`08ef6410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DEVLOCKOBJ::vDestructor+0x4f
    FOLLOWUP_IP: 
    win32k!DEVLOCKOBJ::vDestructor+4f
    fffff960`001b44d3 4c8b80f8090000  mov     r8,qword ptr [rax+9F8h]
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  win32k!DEVLOCKOBJ::vDestructor+4f
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0
    STACK_COMMAND:  .cxr 0xfffff88008ef5a30 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!DEVLOCKOBJ::vDestructor+4f
    BUCKET_ID:  X64_0x3B_win32k!DEVLOCKOBJ::vDestructor+4f
     
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80002b87834, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff88007403eb0, 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: 
    nt!PfFbLogEntryComplete+24
    fffff800`02b87834 48634350        movsxd  rax,dword ptr [rbx+50h]
    CONTEXT:  fffff88007403eb0 -- (.cxr 0xfffff88007403eb0)
    rax=0000000000000030 rbx=ff43f80002c5c5e0 rcx=fffff8a0000a6020
    rdx=0000000000003f80 rsi=fffff8a0000a6060 rdi=fffff8a0000a6060
    rip=fffff80002b87834 rsp=fffff88007404890 rbp=0000000008000000
     r8=0000000000000030  r9=fffff8a0000a6020 r10=fffff80002c5c5f0
    r11=fffff8a0000a6020 r12=0000000000000030 r13=fffff8a009b91de8
    r14=fffff8a009b91da8 r15=fffffa8006afa560
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!PfFbLogEntryComplete+0x24:
    fffff800`02b87834 48634350        movsxd  rax,dword ptr [rbx+50h] ds:002b:ff43f800`02c5c630=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  MassEffect2.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002b87834
    STACK_TEXT:  
    fffff880`07404890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`0000000000000000`00000000 : nt!PfFbLogEntryComplete+0x24
    FOLLOWUP_IP: 
    nt!PfFbLogEntryComplete+24
    fffff800`02b87834 48634350        movsxd  rax,dword ptr [rbx+50h]
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  nt!PfFbLogEntryComplete+24
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    STACK_COMMAND:  .cxr 0xfffff88007403eb0 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_nt!PfFbLogEntryComplete+24
    BUCKET_ID:  X64_0x3B_nt!PfFbLogEntryComplete+24
    Hope this helps,
    Captain
      My Computer


  4. Posts : 14
    Windows 7
    Thread Starter
       #4

    Alright, thanks guys! I will try those things and see if they work.
      My Computer


  5. Posts : 14
    Windows 7
    Thread Starter
       #5

    Ok guys, I tried almost everything that you mentioned and am still getting the BSOD.

    I ran the Memory Diagnostic and System Integrity Checker and everything was fine. I also unistalled AVG and turned off Windows Firewall and I continued getting Blue Screens. The last thing I did was perform a clean install of Windows 7 and still got the BSOD.

    I am beginning to panic because I invested so much money into this computer. I am attaching the last few minidumps for analysis. Please help me try to solve this problem and alleviate my stress.
      My Computer


  6. Posts : 14
    Windows 7
    Thread Starter
       #6

    Is there anyone that can help?
      My Computer


  7. Posts : 6,879
    Win 7 Ultimate x64
       #7

    dahoover a couple of things for you to try. First grab this,

    CPUID

    and double cheek the specs for your ram and make sure it is running at the correct latencies and voltage. Compare the timings from the Memory tab to what it says on the SPD tab. If any of them are lower on the memory tab than the SPD tab, then it will require going into the bios and setting those values manually instead of the default Auto setting. Also for the voltage use the manufacturer's spec for it and set it to that value (and maybe on notch higher) in the bios as well.

    If that doesn't sort it back in the bios look for the following settings under "JumperFree Configuration" (will require setting CPU Overclocking to Manual from Auto),

    HT Over Voltage
    Chipset Over Voltage

    for the first one start with raising it one above default (1.25000V) and test to see if that fixes it. If not raise it up another and test, repeating till it gets to the max (1.38500V).

    If that doesn't fix it for the second one start it at about 1.3V, the minimum setting of 1.1V is for when Cool and Quiet is enabled and the bios will lower it that as needed (and too low for a manual setting). Again test to see if that sorts it or not, and if not raise it 0.1V and test.

    Hopefully one of those or a combination of the two will stop the crashes from happening. I was getting the same stop 124 errors on mine (and the same way, could be gaming or doing nothing; no rhyme or reason to it at all), and it took raising those and a couple of more (mine has a few more settings than yours does) to get mine to run stable. Been running with the raised settings for close to a month now and not seen a single stop 124, to the point that I can now run a program (Prime 95) that would cause it to happen almost instantly (one of the few that I could count on triggering it) to running it for hours at a time.
      My Computer


  8. Posts : 86
    Windows 7
       #8

    Since this is a new build make sure all chipset,network,graphics,etc. drivers and bios is current.

    Your bios should be this one:
    Description M4A785T-M BIOS 2002
    Support new CPUs. Please refer to our website at: http://support.asus.com/cpusupport/cpusupport.aspx File Size 759.68 (KBytes) 2010/03/30 update Download from Global (DLM) Global

    Do memory diagnostic for at least 3 passes:http://www.memtest.org/

    Do harddrive diagnostic from manufacturer.
      My Computer


  9. Posts : 14
    Windows 7
    Thread Starter
       #9

    stormy13 said:
    dahoover a couple of things for you to try. First grab this,

    CPUID

    and double cheek the specs for your ram and make sure it is running at the correct latencies and voltage. Compare the timings from the Memory tab to what it says on the SPD tab. If any of them are lower on the memory tab than the SPD tab, then it will require going into the bios and setting those values manually instead of the default Auto setting. Also for the voltage use the manufacturer's spec for it and set it to that value (and maybe on notch higher) in the bios as well.

    If that doesn't sort it back in the bios look for the following settings under "JumperFree Configuration" (will require setting CPU Overclocking to Manual from Auto),

    HT Over Voltage
    Chipset Over Voltage

    for the first one start with raising it one above default (1.25000V) and test to see if that fixes it. If not raise it up another and test, repeating till it gets to the max (1.38500V).

    If that doesn't fix it for the second one start it at about 1.3V, the minimum setting of 1.1V is for when Cool and Quiet is enabled and the bios will lower it that as needed (and too low for a manual setting). Again test to see if that sorts it or not, and if not raise it 0.1V and test.

    Hopefully one of those or a combination of the two will stop the crashes from happening. I was getting the same stop 124 errors on mine (and the same way, could be gaming or doing nothing; no rhyme or reason to it at all), and it took raising those and a couple of more (mine has a few more settings than yours does) to get mine to run stable. Been running with the raised settings for close to a month now and not seen a single stop 124, to the point that I can now run a program (Prime 95) that would cause it to happen almost instantly (one of the few that I could count on triggering it) to running it for hours at a time.
    Ok I am not that technical so I am attaching the saved txt file from the cpuid report. If you could tell me if anything looks like it needs to be changed that would be great.
      My Computer


  10. Posts : 14
    Windows 7
    Thread Starter
       #10

    nickle said:
    Since this is a new build make sure all chipset,network,graphics,etc. drivers and bios is current.

    Your bios should be this one:
    Description M4A785T-M BIOS 2002
    Support new CPUs. Please refer to our website at: ASUSTeK Computer Inc.-Support- File Size 759.68 (KBytes) 2010/03/30 update Download from Global (DLM) Global

    Do memory diagnostic for at least 3 passes:Memtest86+ - Advanced Memory Diagnostic Tool

    Do harddrive diagnostic from manufacturer.
    Thanks Nickle, I updated the BIOS using the file that you linked me too. Hopefully this works!
      My Computer


 
Page 1 of 3 123 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 08:53.
Find Us