Frequent BSODs; 64bit Win7, newly built system

    Discussão Geral

  • Hello!


    I built this new system three days ago on Thursday, July 8th. Everything ran fine through Friday and Saturday night. Near the end of the night on Saturday, however, I restarted my system and let Windows Update do its thing. Once I logged back in, I discovered I couldn't do very much before getting smacked with a BSOD.


    It's happened 4 times so far, and the timings vary. At first I thought it was an issue with one particular game, APB Reloaded, which crashed twice; once as soon as it started and another 2 minutes or so in. Hoping it was just the one game, I moved on to Skyrim, played for about 10 minutes, crashed again. That's when I became concerned, as now I have no idea what's wrong. I did a system restore to before the Windows Update, restarted again, started a disk defragment wondering if my Hard Drive was alright; it ran for about 45 minutes, then I started up Netflix to watch a few shows while it ran and bluescreened within 5 minutes.


    Here's my setup:

    OS - Windows 7 Professional

    CPU - Intel Core i5 3570k 3.4 ghz Quad Core (Not OCd (yet))

    MoBo - ASUS P8Z77-V Intel 7 Series

    RAM - 8GB Corsair Vengeance - CMZ8GX3M2A1600C9

    GPU - EVGA GeForce GTX 670

    HD - 500 GB Westrn Digital Caviar Black


    Any help would be much appreciated. I'm thinking it's a video card driver error given the circumstances I seem to bluescreen under (I've been able to log on, find this website, browse a bit, and even make this post with no trouble so far) but I already -have- the latest drivers. Also, I've been gaming enthusiastically at max settings for two days before the issues, and system restoring to before the potentially compatibility-ruining windows update clearly didn't work, so I'm not sure. Could it be memory, or hard drive? The HD isn't making any unusual sounds. Hope to hear from someone soon, thanks!

    • Editado BTVFX domingo, 8 de julho de 2012 17:59
    domingo, 8 de julho de 2012 17:56

Todas as Respostas

  • Hi, 

    Please go to this path C:\Windows\Minidump  and Upload all DMPs Files into SkyDrive.



    domingo, 8 de julho de 2012 18:00
  • Here we are:!116&authkey=!AESxGnhJzlXCUog

    domingo, 8 de julho de 2012 18:10
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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
            .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)
    kb will then show the corrected stack.
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff80002ca03a0
    Debugging Details:
    BUGCHECK_STR:  0x7f_8
    PROCESS_NAME:  System
    LAST_CONTROL_TRANSFER:  from fffff80002cd75a9 to fffff80002cd8040
    fffff800`00ba4d28 fffff800`02cd75a9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`02cd5a72 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff800`02ca03a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`08aa6fd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x60
    fffff800`02cd5a72 90              nop
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  ntkrnlmp.exe
    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
    Followup: MachineOwner

    Bug Check 0x7f :

    Please check this article it's a same your BSOD :



    domingo, 8 de julho de 2012 18:40
  • Also, it is quite possible the vsdatant.sys is contributing to the crash.

    The vsdatant.sys is a component of ZoneAlarm which appears to be installed.

    Can you provide the following file, which should contain much more information on the crash?:


    You may have to zip and compress the memory.dmp file with a third party application such as 7-Zip or WinRAR to upload to Windows Live SkyDrive as the memory.dmp file can be quite large. 

    domingo, 8 de julho de 2012 22:18
  • Hello Auggy, good timing. I was just about to post again.

    Thanks for the info, Las. Unfortunately it didn't solve my problem. I reset my BIOS and ran multiple passes of multiple memory scans (windows utility and memcheck86) with 0 errors across the board. Was able to play ABP: Reloaded for a good hour and a half, thinking the issue solved, but as soon as I switched games I got another bluescreen within 2 minutes. :(

    I do have ZoneAlarm installed, Auggy. Here's the file you requested.!117&authkey=!AJuSlTT_0yMzDGg

    Thanks for the help, both of you!

    • Editado BTVFX domingo, 8 de julho de 2012 23:02
    domingo, 8 de julho de 2012 22:55
  • The vsdatant.sys is involved in the crash:

    BugCheck 7F, {8, 80050033, 406f8, fffff80002c863a0}

    *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )

    The detailed analysis showed the tcpip.sys, along with other "networking" drivers were also involved in the crash.

    Try installing Service Pack 1 for Windows 7 which contains fixes for the netio.sys and tcpip.sys.

    And try updating or, if necessary, uninstall ZoneAlarm.

    • Editado auggyMVP domingo, 8 de julho de 2012 23:52
    domingo, 8 de julho de 2012 23:46
  • Many thanks! I'll try the hotfixes and report my findings, then proceed to uninstalling ZoneAlarm if necessary.
    domingo, 8 de julho de 2012 23:55
  • OK, good luck.

    segunda-feira, 9 de julho de 2012 00:46
  • I ended up getting rid of ZoneAlarm. After hopping between netflix and 3 games with impunity, I'm cautiously optimistic. Thanks a ton for the help. I'll post again if anything comes up. :)
    segunda-feira, 9 de julho de 2012 01:55
  • You're welcome.
    segunda-feira, 9 de julho de 2012 02:36