BSOD, fresh install W7 64bit


  1. Posts : 11
    W7 64bit
       #1

    BSOD, fresh install W7 64bit


    OK. attached is the zip files.
    thank you in advance for helping.. this is such a pain.
    blue screens when going into hibernate, or just sitting.
    also blue screens going into stand by.

    x64 bit W7 Ultimate
    retail version
    Hardware is only 2 months old
    OS install 1 week ago, blue screens from day 1
    all drivers are up to date by manufacturs.
    1 device intentionaly disabled in device manager due to freeze problems ( ati tv tuner)


    amd hex core 3.2
    Gigabyte ga 890gpa ud3h
    4 gigs ram
    liquid cooled
    1200 watt psu


    thank you
      My Computer


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

    loueber said:
    OK. attached is the zip files.
    thank you in advance for helping.. this is such a pain.
    blue screens when going into hibernate, or just sitting.
    also blue screens going into stand by.

    x64 bit W7 Ultimate
    retail version
    Hardware is only 2 months old
    OS install 1 week ago, blue screens from day 1
    all drivers are up to date by manufacturs.
    1 device intentionaly disabled in device manager due to freeze problems ( ati tv tuner)


    amd hex core 3.2
    Gigabyte ga 890gpa ud3h
    4 gigs ram
    liquid cooled
    1200 watt psu


    thank you

    So far you have several causes of the BSOD's. First your Rt64win7.sys driver (your realtek driver) and your vsmraid.sys (the via raid driver for amd).

    You need to re-install them as well as all the following drivers.

    Code:
    GVTDrv64.sys        fffff880`095e7000    fffff880`095f1000    0x0000a000    0x44fd22ca    9/5/2006 03:10:02                        
    gdrv.sys        fffff880`099f4000    fffff880`099fd000    0x00009000    0x49b9d175    3/12/2009 23:22:29                        
    spldr.sys        fffff880`01410000    fffff880`01418000    0x00008000    0x4a0858bb    5/11/2009 12:56:27
    After that if you keep having BSOD's we can narrow the focus.

    Ken J

    DMP
    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\Windows_NT6_BSOD_jcgriff2\100310-18267-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\symbols;*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 (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`03295e50
    Debug session time: Sun Oct  3 18:50:29.181 2010 (GMT-4)
    System Uptime: 0 days 22:20:14.617
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8004c06a20, fffff80000b9c518, fffffa8003f2a240}
    
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8004c06a20, Physical Device Object of the stack
    Arg3: fffff80000b9c518, Functional Device Object of the stack
    Arg4: fffffa8003f2a240, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  fffffa8003f2a240
    
    DEVICE_OBJECT: fffffa8005c4d050
    
    DRIVER_OBJECT: fffffa8005cad060
    
    IMAGE_NAME:  Rt64win7.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ba73efa
    
    MODULE_NAME: Rt64win7
    
    FAULTING_MODULE: fffff88014b1c000 Rt64win7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80003137273 to fffff800030c8740
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`03137273 : 00000000`0000009f 00000000`00000003 fffffa80`04c06a20 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`030d429e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
    fffff800`00b9c570 fffff800`030d3dd6 : fffff800`03278700 00000000`004ea7be 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5e0 fffff800`030d44be : 000000bb`3ad8cd0c fffff800`00b9cc58 00000000`004ea7be fffff800`03246a48 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`030d3cb7 : 0000003a`c40414c1 0000003a`004ea7be 0000003a`c40414e9 00000000`000000be : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`030d0eea : fffff800`03242e80 fffff800`03250c40 00000000`00000000 fffff880`0141cc50 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys
    
    BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 11
    W7 64bit
    Thread Starter
       #3

    wow..
    ok thank you.. ill do that tonight and see how it goes tomorrow...
    now when you say reinstall im assuming just reinstall the drivers since im 99.9% sure i have the latest versions.. ill just go through the the install process again.......
      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 04:03.
Find Us