Random BSOD


  1. Posts : 5
    Windows 7
       #1

    Random BSOD


    Guys,

    I've been following this forum for some time now, your advice is great. I hope that I can seek some help now myself. I built what was for me a dream machine. It's no super game machine or anything like that but I picked out what in hardware what I liked, stuck it all together and was a happy camper. This was early last year. Then random BSODs showed up in Vista. I got so frustrated that I actually turned off my machine, used my work laptop all the time and never touched the self built one again. Then Windows 7 came out, I thought I'd give it one more try. Installed 7, it ran for a few days without a problem. All of a sudden - doing nothing, just ideling - a BSOD. Today again, while reading news on the web. I don't want to switch back to my laptop so I'm hoping that with the attached minidump somebody can help me figure out what seems to be causing my problems.

    Any help is more than appreciated.

    Thanks,
    Christoph
      My Computer


  2. Posts : 5
    Windows 7
    Thread Starter
       #2

    Did I do anything wrong with my post above? I'm surprised not having gotten any responses.

    Christoph
      My Computer


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

    christoph404 said:
    Guys,

    I've been following this forum for some time now, your advice is great. I hope that I can seek some help now myself. I built what was for me a dream machine. It's no super game machine or anything like that but I picked out what in hardware what I liked, stuck it all together and was a happy camper. This was early last year. Then random BSODs showed up in Vista. I got so frustrated that I actually turned off my machine, used my work laptop all the time and never touched the self built one again. Then Windows 7 came out, I thought I'd give it one more try. Installed 7, it ran for a few days without a problem. All of a sudden - doing nothing, just ideling - a BSOD. Today again, while reading news on the web. I don't want to switch back to my laptop so I'm hoping that with the attached minidump somebody can help me figure out what seems to be causing my problems.

    Any help is more than appreciated.

    Thanks,
    Christoph
    This one was caused by Mcshield.exe which is part of you rmacaffee. I would uninstall it just to see if it fixes the problem

    I would also run a system file check
    type cmd in search>right click and run as admin>sfc /scannow

    If you are overclocking stop


    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\020710-20529-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\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`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
    Debug session time: Sun Feb  7 19:32:29.424 2010 (GMT-5)
    System Uptime: 2 days 23:16:54.376
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002a7b18e}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: 00000000000006f8
    Arg4: fffff80002a7b18e
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  Mcshield.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002a74469 to fffff80002a74f00
    
    STACK_TEXT:  
    fffff880`02b69ce8 fffff800`02a74469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02b69cf0 fffff800`02a72932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02b69e30 fffff800`02a7b18e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff881`07e0cfd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8b
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`02a72932 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
    ---------
    
    '
      My Computer


  4. Posts : 5
    Windows 7
    Thread Starter
       #4

    WOW! Thank you so much. I had no idea that McAfee can crash a machine. This happened also when I ran Vista... Thank you again!
    Christoph
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    Welcome!

    I'm no BSOD expert, but my best guess is your anti-virus, McAfee. Try disabling it, and see if the problem goes away.

    Also try opening an elevated command prompt and running sfc /scannow.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\Desktop\020710-20529-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\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`02a03000 PsLoadedModuleList = 0xfffff800`02c40e50
    Debug session time: Sun Feb  7 19:32:29.424 2010 (GMT-5)
    System Uptime: 2 days 23:16:54.376
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 6f8, fffff80002a7b18e}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: 00000000000006f8
    Arg4: fffff80002a7b18e
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  Mcshield.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002a74469 to fffff80002a74f00
    
    STACK_TEXT:  
    fffff880`02b69ce8 fffff800`02a74469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff880`02b69cf0 fffff800`02a72932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02b69e30 fffff800`02a7b18e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff881`07e0cfd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SwapContext_PatchXSave+0x8b
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiDoubleFaultAbort+b2
    fffff800`02a72932 90              nop
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    
    Followup: MachineOwner
    ---------
    Edit: it looks as if I'm a little late. However, it is encouraging to me because I came up with the same cause as the expert, and the same solution.

    Can I recommend the free A/V Microsoft Security Essentials instead of McAfee?
      My Computer


  6. Posts : 5
    Windows 7
    Thread Starter
       #6

    You're not too late at all. I uninstalled McAfee... still, such an established software can cause a BSOD... yikes! Installing the MS A/V right now =) Thank you for the advice.
    Christoph
      My Computer


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

    Just an FYI
    There are some display related files that are not registered properly and a file related to Adobe Systems. Apart from the above steps remove the Display drivers and Download and install the drivers from manufactures website and NOT from Windows update.

    Code:
    win32k.sys   unavailable (00000000) - Multi-User Win32 Driver file ( Display related )
    TSDDD.dll    unavailable (00000000) - Framebuffer Display Driver
    cdd.dll      unavailable (00000000) - Canonical Display Driver
    ATMFD.DLL    unavailable (00000000) - Adobe Systems
    Hope this helps,
    Captain
      My Computer


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

    christoph404 said:
    You're not too late at all. I uninstalled McAfee... still, such an established software can cause a BSOD... yikes! Installing the MS A/V right now =) Thank you for the advice.
    Christoph


    Anytime Hope it helps.
      My Computer


  9. Posts : 5
    Windows 7
    Thread Starter
       #9

    Hey guys,

    sorry for the follow-up. So, I uninstalled McAfee and then I just wanted to be safe so I ran the Windows Memory Diagnostic Tool all night - nearly 12 hours. When I woke up this morning, there was a message that there were some "hardware problems" and that I should contact the computer's manufacturer. Is this the message for faulty RAM? I was expecting more along the lines of "RAM defect".

    Also, I have 4 x 1GB RAM. Is there a way to find out which one is faulty? I'm not overclocking (at least I don't think I am, I have mostly all default settings in the BIOS).

    Any help is greatly appreciated!

    Thanks so much,
    Christoph
      My Computer


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

    christoph404 said:
    Hey guys,

    sorry for the follow-up. So, I uninstalled McAfee and then I just wanted to be safe so I ran the Windows Memory Diagnostic Tool all night - nearly 12 hours. When I woke up this morning, there was a message that there were some "hardware problems" and that I should contact the computer's manufacturer. Is this the message for faulty RAM? I was expecting more along the lines of "RAM defect".

    Also, I have 4 x 1GB RAM. Is there a way to find out which one is faulty? I'm not overclocking (at least I don't think I am, I have mostly all default settings in the BIOS).

    Any help is greatly appreciated!

    Thanks so much,
    Christoph

    You can go into event viewer (type eventvwr in search) go too the windows log apllication tab. see what critical errors (the have red in the left column) are listed. should be mentioned there. If so make a screenshot and upload it to us.

    Ken
      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 07:33.
Find Us