BSOD With Dump File


  1. Posts : 130
    Windows 7 Home Premium 64 bit (OEM) SP1
       #1

    BSOD With Dump File


    Had a BSOD today just before the login screen.
    The system is 14 months old, and my build.
    Changes I made yesterday:
    Downloaded speccy and google chrome.
    No over clocking done.
    About a week ago had a side by side error that wouldn't let me open IE9 and CCleaner but when restarting the problem didn't persist.

    Other info:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033
    Additional information about the problem:
    BCCode: 1000007e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF88004BC5D69
    BCP3: FFFFF88003577488
    BCP4: FFFFF88003576CE0
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
    Files that help describe the problem:
    C:\Windows\Minidump\073111-19359-01.dmp
    C:\Users\GZ\AppData\Local\Temp\WER-40685-0.sysdata.xml

    Dump file is attached.

    Any help would be appreciated.
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    Not much info from the memory dump that you cited. But the memory dump from 17 Jul points to a network driver
    The perfmon report also points to network issues.

    Please go to Device Manager and see if there are any problems with the devices in the Network Adapter category. If there are, right click on those devices and select "Uninstall" - then reboot the system. Then re-check Device Manager and see if any of those devices still remain a problem. Let us know what you find out.

    Go to this link: GIGABYTE - Motherboard - Socket 1156 - GA-P55-USB3 (rev. 2.0)
    Enter the OS specifics in the "Choose your OS" dropdown box.
    Download the Realtek LAN driver and install it on your system.
    Monitor for further BSOD's

    Your USB 3.0 drivers are also older - and that version is also known to cause BSOD's w/some Win7 systems.
    So please download the latest version of the USB 3.0 drivers from the above link and install them also.

    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-19359-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sun Jul 31 10:46:35.210 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:16.021
    Probably caused by : ks.sys ( ks!QueryDeviceRelations+1b9 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_ks!QueryDeviceRelations+1b9
    Bugcheck code 1000007E
    Arguments ffffffff`c0000005 fffff880`04bc5d69 fffff880`03577488 fffff880`03576ce0
    BiosVersion = F9
    BiosReleaseDate = 11/01/2010
    CPUID:        "Intel(R) Core(TM) i7 CPU       K 875  @ 2.93GHz"
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\071711-26613-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sun Jul 17 11:49:34.777 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:13.698
    *** 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 ( Rt64win7+18fb9 )
    BUGCHECK_STR:  0x1E_0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_0_Rt64win7+18fb9
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    CPUID:        "Intel(R) Core(TM) i7 CPU       K 875  @ 2.93GHz"
    MaxSpeed:     2930
    CurrentSpeed: 2931
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 130
    Windows 7 Home Premium 64 bit (OEM) SP1
    Thread Starter
       #3

    Thanks usasma.
    I did all the items you pointed out, I'll just have to wait and see if it works.
    Thanks for the timely reply.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    In general:
    - if you wait a week, it's most likely fixed
    - if you wait 2 weeks, it's probably fixed
    But these are just estimates - and they depend on what's going on inside the case.

    Good luck!
      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 09:48.
Find Us