BSODS recently on new Computer


  1. Posts : 6
    Windows 7 Ultimate x64
       #1

    BSODS recently on new Computer


    I recently built myself a computer about 28 or 4 weeks ago and installed windows 7 Ultimate x64 fine. But then 3 days after Christmas on the 28th of December about 3 weeks after I put together my computer the BSOD's started occurring and i got scared so I started runninng virus checks and checking if i messed up anything in the BIOS.

    I ended up reinstalling a fresh Windows 7 which ended up not helping as much since about within a few hours when I reinstalled Starcraft 2 I ended getting a BSOD halfway through a match. So I searched and searched on google, I tried updating my drivers, used a registry cleaner software and even changed my antivirus but no luck.

    I have attached my minidumps and followed the BSOD posting Instructions.

    Extra: I only get BSOD's when either playing a game or when exiting a game, after I reinstalled Windows 7 I did'nt get any BSOD's while just regularly using my computer for the internet. I guessing which means it might be a graphics card issue.

    Thank you for your time :)
    Last edited by JoeSigma; 01 Jan 2011 at 18:04. Reason: Extra Information
      My Computer


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

    JoeSigma said:
    I recently built myself a computer about 28 or 4 weeks ago and installed windows 7 Ultimate x64 fine. But then 3 days after Christmas on the 28th of December about 3 weeks after I put together my computer the BSOD's started occurring and i got scared so I started runninng virus checks and checking if i messed up anything in the BIOS.

    I ended up reinstalling a fresh Windows 7 which ended up not helping as much since about within a few hours when I reinstalled Starcraft 2 I ended getting a BSOD halfway through a match. So I searched and searched on google, I tried updating my drivers, used a registry cleaner software and even changed my antivirus but no luck.

    I have attached my minidumps and followed the BSOD posting Instructions.

    Extra: I only get BSOD's when either playing a game or when exiting a game, after I reinstalled Windows 7 I did'nt get any BSOD's while just regularly using my computer for the internet. I guessing which means it might be a graphics card issue.

    Thank you for your time :)

    These were caused by fltmgr.sys crashing because of your Symantec AV.

    I would remove Symantec and replace with Microsoft security essentials and run a system file check to repair the system files

    ftp://ftp.symantec.com/public/englis...moval_Tool.exe

    http://www.microsoft.com/security_essentials/

    SFC /SCANNOW Command - System File Checker


    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\Minidumps\123110-45599-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Mini Kernel Dump does not have process information
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\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
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
    Debug session time: Fri Dec 31 13:07:56.477 2010 (GMT-5)
    System Uptime: 0 days 0:02:04.178
    Loading Kernel Symbols
    ...................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Unable to add module at 00000000`00000000
    
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff880012eb141, fffff8800a68f950, 0}
    
    Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 )
    
    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: fffff880012eb141, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff8800a68f950, 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: 
    fltmgr!TreeUnlinkMulti+51
    fffff880`012eb141 488b4620        mov     rax,qword ptr [rsi+20h]
    
    CONTEXT:  fffff8800a68f950 -- (.cxr 0xfffff8800a68f950)
    rax=fffffa8003ffbb60 rbx=0000000000000000 rcx=fffffa8003f8b8a8
    rdx=fffffa8003bd9dd0 rsi=00ff000000000000 rdi=0000000000000000
    rip=fffff880012eb141 rsp=fffff8800a690320 rbp=fffffa8003f8b8a8
     r8=ffffffffffffffff  r9=ffffffffffffffff r10=000000000000015c
    r11=0000000000000001 r12=fffffa8003bd9dd0 r13=0000000000000000
    r14=0000000000002000 r15=fffffa80049b7e90
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    fltmgr!TreeUnlinkMulti+0x51:
    fffff880`012eb141 488b4620        mov     rax,qword ptr [rsi+20h] ds:002b:00ff0000`00000020=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880012eb141
    
    STACK_TEXT:  
    fffff880`0a690320 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!TreeUnlinkMulti+0x51
    
    
    FOLLOWUP_IP: 
    fltmgr!TreeUnlinkMulti+51
    fffff880`012eb141 488b4620        mov     rax,qword ptr [rsi+20h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  fltmgr!TreeUnlinkMulti+51
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: fltmgr
    
    IMAGE_NAME:  fltmgr.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11f
    
    STACK_COMMAND:  .cxr 0xfffff8800a68f950 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!TreeUnlinkMulti+51
    
    BUCKET_ID:  X64_0x3B_fltmgr!TreeUnlinkMulti+51
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #3

    zigzag3143 said:
    JoeSigma said:
    I recently built myself a computer about 28 or 4 weeks ago and installed windows 7 Ultimate x64 fine. But then 3 days after Christmas on the 28th of December about 3 weeks after I put together my computer the BSOD's started occurring and i got scared so I started runninng virus checks and checking if i messed up anything in the BIOS.

    I ended up reinstalling a fresh Windows 7 which ended up not helping as much since about within a few hours when I reinstalled Starcraft 2 I ended getting a BSOD halfway through a match. So I searched and searched on google, I tried updating my drivers, used a registry cleaner software and even changed my antivirus but no luck.

    I have attached my minidumps and followed the BSOD posting Instructions.

    Extra: I only get BSOD's when either playing a game or when exiting a game, after I reinstalled Windows 7 I did'nt get any BSOD's while just regularly using my computer for the internet. I guessing which means it might be a graphics card issue.

    Thank you for your time :)

    These were caused by fltmgr.sys crashing because of your Symantec AV.

    I would remove Symantec and replace with Microsoft security essentials and run a system file check to repair the system files

    ftp://ftp.symantec.com/public/englis...moval_Tool.exe

    http://www.microsoft.com/security_essentials/

    SFC /SCANNOW Command - System File Checker


    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\Minidumps\123110-45599-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Mini Kernel Dump does not have process information
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\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
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
    Debug session time: Fri Dec 31 13:07:56.477 2010 (GMT-5)
    System Uptime: 0 days 0:02:04.178
    Loading Kernel Symbols
    ...................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Unable to add module at 00000000`00000000
    
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff880012eb141, fffff8800a68f950, 0}
    
    Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 )
    
    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: fffff880012eb141, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffff8800a68f950, 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: 
    fltmgr!TreeUnlinkMulti+51
    fffff880`012eb141 488b4620        mov     rax,qword ptr [rsi+20h]
    
    CONTEXT:  fffff8800a68f950 -- (.cxr 0xfffff8800a68f950)
    rax=fffffa8003ffbb60 rbx=0000000000000000 rcx=fffffa8003f8b8a8
    rdx=fffffa8003bd9dd0 rsi=00ff000000000000 rdi=0000000000000000
    rip=fffff880012eb141 rsp=fffff8800a690320 rbp=fffffa8003f8b8a8
     r8=ffffffffffffffff  r9=ffffffffffffffff r10=000000000000015c
    r11=0000000000000001 r12=fffffa8003bd9dd0 r13=0000000000000000
    r14=0000000000002000 r15=fffffa80049b7e90
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    fltmgr!TreeUnlinkMulti+0x51:
    fffff880`012eb141 488b4620        mov     rax,qword ptr [rsi+20h] ds:002b:00ff0000`00000020=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880012eb141
    
    STACK_TEXT:  
    fffff880`0a690320 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!TreeUnlinkMulti+0x51
    
    
    FOLLOWUP_IP: 
    fltmgr!TreeUnlinkMulti+51
    fffff880`012eb141 488b4620        mov     rax,qword ptr [rsi+20h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  fltmgr!TreeUnlinkMulti+51
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: fltmgr
    
    IMAGE_NAME:  fltmgr.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11f
    
    STACK_COMMAND:  .cxr 0xfffff8800a68f950 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_fltmgr!TreeUnlinkMulti+51
    
    BUCKET_ID:  X64_0x3B_fltmgr!TreeUnlinkMulti+51
    
    Followup: MachineOwner
    ---------
    I'd just like to say thank you for replying to my post, wasting expecting a reply on the same day, good to see you have active members on this site :)
      My Computer


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

    You are more than welcome Joe. We have a ton of qualified people that do this because they like helping. Thanks for telling us


    Ken
      My Computer


  5. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #5

    yeh it seems that hasnt solved my problems because, I am still receiving BSOD'S, I removed one stick of ram to check if that would solve the problem but it didnt, so i have attached two more new minidumps to see if anythings different
      My Computer


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

    JoeSigma said:
    yeh it seems that hasnt solved my problems because, I am still receiving BSOD'S, I removed one stick of ram to check if that would solve the problem but it didnt, so i have attached two more new minidumps to see if anythings different

    Well I see two things. Two year old Avast (2008) and memory management. I am glad you ditched Norton, and avast may not even be the cause But......

    I would

    As usual remove Avast and replace with MSE

    Run memtest again.


    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
      My Computer


  7. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #7

    ah alright I installed MSE and im going to run memtest 86 now
      My Computer


  8. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #8

    I removed one stick off RAM and used memtest86 but i didnt get any errors even after 5 passes ><
      My Computer


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

    JoeSigma said:
    I removed one stick off RAM and used memtest86 but i didnt get any errors even after 5 passes ><
    Then use the known good ram to test each mobo slot
      My Computer


  10. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #10

    i checked each slot, finding nothing wrong with them, i then thought to try playing starcraft 2 again thinking it was all fine but even with the good ram in, I received BSOD's :/

    I've added these new minidumps in hopes you might be able to discearn my problem, because I just want to know if i should jut either return my RAM to the store or buy new ram.
      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 18:39.
Find Us