Comp freezes and some BSOD, seems random, please give advice

Page 1 of 2 12 LastLast

  1. Posts : 21
    Windows 7 Home Premium 64bit
       #1

    Comp freezes and some BSOD, seems random, please give advice


    Hello guys, im kinda new on this forum, so ill just describe my problem and what i've tried so far, all comments/advices are appreciated!

    Whats happening:

    So about in the March of 2014, ive started to experience system freezes, a few times a week. That means, the last moment shows on the monitor, but no keyboard or mouse reaction, nor mashed screen, only annoying BZZZZZ voice from the speakers till hard reset.

    When:

    Mostly when playing games, mostly because i only play games or do programming and stuff. Also happened after a simple boot, watching a youtube video. Sometimes once in 2 weeks, sometimes 2 times a day, but the weird thing is i do almost the same thing these days.

    What I've tried so far:

    Ran a bunch of test: 3D mark, fur mark, prime95, video memory test, memtest86, etc. ran them a couple of times, for hours, none of them produced errors or crashes, BSODs. Did 2-3 times clean windows reinstall with necessary drivers, updated drivers, updated BIOS, no luck. Also tried to swap ram modules, and use only 1, use in different slots, still no luck. Been in comp service, they did some tests too, tested the PSU, cleaned the PC, still getting the lockups. Also used AIDA64 to monitor and log temps for weeks, nothing bad with them, even seconds before the crashes. Resetted the BIOS to default a few times, im no overclocking and the sad thing is that when the first lockup occured i dont remember installing anything other than World of Warcraft, no drivers or anything.

    One more thing, when i was desperate enough, i tried the in-built driver verifier stuff, from microsoft, and found a driver, ndisrd.sys from NT kernel resources to causes my systeam to crash, but in different way (mashed screen, and instantly after boot). So i did a clean reinstall and after that i didnt fint that driver, but the crash still occured.. So i dont think its the root of the problem, just saying, who knows, maybe some of you know something about it. Also, i have difficulties updating that driver.

    What I personally think:

    IMHO its a faulty motherboard, or MAYBE but really MAYBE a driver which i installed corrupted from original install disks and updated from manufacturer websites 3-4 times? So i've decided to buy a motherboard, because I can hardly belive its the CPU or GPU because of the tons of tests we made.

    Am i wrong, or any other opinions or tests i should try?

    Also, here is the last BSODs error code i got, and ill try to upload the dump file:

    BCCode: 101
    BCP1: 0000000000000019
    BCP2: 0000000000000000
    BCP3: FFFFF88002F65180
    BCP4: 0000000000000002
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    PS: Sorry for the long description.



    My specs are:
    2x4 GB RAM, corsair DDR3 1333Mhz
    ASUS HD7870 GPU
    Intel i7-3770k 2.5GHz CPU
    1x SSD with the OS installed, 1x 1TB HDD with stuff on it, alse checked them for failures, 100% healthy.
    700W PSU, coolermaster
    ASUS P8H77-M mobo

    Thanks in forward for any help or advice,

    Lesley
    Last edited by bigbadwolf; 18 Sep 2014 at 00:27.
      My Computer


  2. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #2

    Can you follow the BSOD Posting instructions please, so i can help you

       Information
    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    If you need to add new information like the dump files, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

    If your computer is not creating DMP Files please follow this link: Dump Files - Configure Windows to Create on BSOD

    I look Forward to Helping you.
      My Computer


  3. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    HarriePateman said:
    Can you follow the BSOD Posting instructions please, so i can help you

       Information
    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    If you need to add new information like the dump files, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

    If your computer is not creating DMP Files please follow this link: Dump Files - Configure Windows to Create on BSOD

    I look Forward to Helping you.

    Okay, I've read the instructions and uploaded the .zip file DM Collector collected, what am I missing? Im kinda new to this dump file thing
      My Computer


  4. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #4

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {19, 0, fffff88002f65180, 2}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    This Bugcheck is mainly caused by a Faulty CPU or an outdated BIOS.

    Details about this bugcheck:
    https://www.sevenforums.com/crash-loc...tml#post567135

    Win 7 A Clock Interrupt... BSOD (101 Error)
      My Computer


  5. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    HarriePateman said:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {19, 0, fffff88002f65180, 2}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    
    Followup: MachineOwner
    ---------
    This Bugcheck is mainly caused by a Faulty CPU or an outdated BIOS.

    Details about this bugcheck:
    https://www.sevenforums.com/crash-loc...tml#post567135

    Win 7 A Clock Interrupt... BSOD (101 Error)
    First, thanks for the fast reply! :)

    Still, i have my BIOS updated, and i had these weird crashes with the old and with the new BIOS, so i dount thats its the BIOS, also, I have the CPU checked with various stress tests, prime95 by myself, ran it for multiple hours, more than 3-4 times. The heat is okay, and i dont OC. Are you sure its the CPU that caused the BSOD? or any other possibilities? (if you are sure that its the CPU and the prim95 finds nothing, what can i do?)

    PS: In my BIOS, on default i have the CPU boost, or something like that enabled, which causes the CPU to be overclocked under heavier pressure, is that ok?
      My Computer


  6. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #6

    While STOP 0x101 can be down to faulty hardware or a BIOS bug it can also be caused by a bad driver or piece of software. There are two drivers showing clearly in your dump and you have a program in your startup that is known to cause BSODs, they're all detailed below.

    1: Your ATI driver has been flagged.

    Code:
    fffff880`061fca48  fffff880`0f0bb2d0Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     atikmdag+0x7d2d0
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f03e000 fffff880`0fc85000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Sat Aug 31 01:02:50 2013 (522132AA)
        CheckSum:         00BF596C
        ImageSize:        00C47000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Check for an updated driver for your GPU here. Download the driver then use AMD Uninstall Utility to remove all traces of your current driver, CCC etc. Reboot and install the downloaded driver.

       Note
    When installing choose 'Advanced' or 'Custom' (whichever option is available, just not Express) and uncheck everything except the video driver.


    2: Your Realtek Gigabit Ethernet controller driver has also been flagged.

    Code:
    fffff880`061fc6d8  fffff880`07452c47Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0x7c47
    
    0: kd> lmvm Rt64win7
    start             end                 module name
    fffff880`0744b000 fffff880`07509000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Thu Oct 25 10:20:09 2012 (50890449)
        CheckSum:         000C14E6
        ImageSize:        000BE000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e
    It's very old and needs updating. Download the latest version from the ASUS support page for your motherboard by clicking the button below.


    Download



    3: Uninstall Daemon Tools, a proven cause of BSODs.

    1. Uninstall Daemon Tools.
    2. Download the SPTD standalone installer and follow these steps:
    3. Double click the executable to open it
    4. Click the button shown below



    If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

    Test and report back.
      My Computer


  7. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    Boozad said:
    While STOP 0x101 can be down to faulty hardware or a BIOS bug it can also be caused by a bad driver or piece of software. There are two drivers showing clearly in your dump and you have a program in your startup that is known to cause BSODs, they're all detailed below.

    1: Your ATI driver has been flagged.

    Code:
    fffff880`061fca48  fffff880`0f0bb2d0Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     atikmdag+0x7d2d0
    
    0: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f03e000 fffff880`0fc85000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Sat Aug 31 01:02:50 2013 (522132AA)
        CheckSum:         00BF596C
        ImageSize:        00C47000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Check for an updated driver for your GPU here. Download the driver then use AMD Uninstall Utility to remove all traces of your current driver, CCC etc. Reboot and install the downloaded driver.

       Note
    When installing choose 'Advanced' or 'Custom' (whichever option is available, just not Express) and uncheck everything except the video driver.


    2: Your Realtek Gigabit Ethernet controller driver has also been flagged.

    Code:
    fffff880`061fc6d8  fffff880`07452c47Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     Rt64win7+0x7c47
    
    0: kd> lmvm Rt64win7
    start             end                 module name
    fffff880`0744b000 fffff880`07509000   Rt64win7 T (no symbols)           
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Thu Oct 25 10:20:09 2012 (50890449)
        CheckSum:         000C14E6
        ImageSize:        000BE000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e
    It's very old and needs updating. Download the latest version from the ASUS support page for your motherboard by clicking the button below.


    Download



    3: Uninstall Daemon Tools, a proven cause of BSODs.

    1. Uninstall Daemon Tools.
    2. Download the SPTD standalone installer and follow these steps:
    3. Double click the executable to open it
    4. Click the button shown below



    If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

    Test and report back.
    Thanks mate for your time!
    I've updated both the drivers, now im going to wait 1-2 weeks to see if something changes. Also, i have to mention that this "Ethernet Controller Driver" is fuzzy a bit, because I tried the Driver Verifier, which crashed the OS stressing this driver, tho I tried this one and the updated one, but I gave up checking them because I doubt that both of their versions are causing these crashes when I ran this maching for half a year without problems.

    Anyway, you could tell something to start over again, I'll let you know if something changed!:)
      My Computer


  8. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #8

    You're welcome, do be sure to let us know how you get on. And please do uninstall Daemon Tools, it uses SCSI Pass-Thru Direct which has been proven time and again to cause BSODs. Follow the steps above to cleanse your system of any traces of SPTD.
      My Computer


  9. Posts : 21
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Boozad said:
    You're welcome, do be sure to let us know how you get on. And please do uninstall Daemon Tools, it uses SCSI Pass-Thru Direct which has been proven time and again to cause BSODs. Follow the steps above to cleanse your system of any traces of SPTD.
    Okay, on this install there are no Daemon now. By the way, the worst thing of these crashes that i rarely get BSOD, like 1 out of 20 times, is there a way to force BSOD? or some test that can at least decrase the range of possible causes?
      My Computer


  10. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #10

    You can run Driver Verifier again if you want to stress your drivers, but with those two showing up already I wouldn't bother. With the two updated drivers and removal of Daemon Tools and SPTD just run your system as normal, if you do get any more BSODs then post the new dumps in a new post and we'll go from there.
      My Computer


 
Page 1 of 2 12 LastLast

  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 13:00.
Find Us