1. #1

    BSOD twice today within an hour.....both caused by different things (maybe)

    I am having an issue with my wifes laptop. It is an ASUS K53TA and I got a BSOD twice today within and hour. I was using photoshop CS4 and I had Firefox open as well (latest version). The Dump file is as follows.

    ==================================================
    Dump File : 020113-79529-01.dmp
    Crash Time : 2/1/2013 11:23:12 AM
    Parameter 1 : 00000000`00000031
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff880`02f64180
    Parameter 4 : 00000000`00000002
    Caused By Driver : amd_sata.sys
    Caused By Address : amd_sata.sys+5071
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7efc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\020113-79529-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 275,112
    ==================================================



    The second time that it happened this was the dump file

    ==================================================
    Dump File : 020113-29952-01.dmp
    Crash Time : 2/1/2013 12:20:02 PM
    Parameter 1 : 00000000`00000031
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff880`02fd5180
    Parameter 4 : 00000000`00000003
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7efc0
    File Description : NT Kernel & System
    Product Name : Microsoftฎ Windowsฎ Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
    Processor : x64
    Crash Address : ntoskrnl.exe+7efc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\020113-29952-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 275,112
    ==================================================

    Any help on why this might be happening or maybe a direction that I can go to get help would be great.

    Thank you.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Tekno Venus's Avatar
    Join Date
    Jul 2012
    Location
    UK
    Age
    20
    Posts
    5,807
    • specs System Specs
      • Manufacturer:
        Custom Built
      • Motherboard:
        ASUS Z170I ITX
      • CPU:
        Intel Core i7 6700K
      • Memory:
        16GB DDR4
      • Hard Drives:
        500GB Samsung 850 EVO, 2TB Seagate HDD
      • Power Supply:
        450W Corsair SFX
      • Case:
        Silverstone SG13 ITX
      • Cooling:
        Corsair H60i
      • Display:
        Dell U2715H - 2160x1440 27 inch
      • Operating System:
        Windows 10 Pro x64

    Re: BSOD twice today within an hour.....both caused by different things (maybe)

    Hello and welcome to Sysnative,

    Please can you follow the bsod posting instructions --> http://www.sysnative.com/forums/bsod...ows-vista.html

    Thanks,
    Stephen


  3. #3

    BSOD questions

    I am attaching the files per Tekno Venus' Instructions. I added the PERFMON.html file to the zip file, because the attachment manager wouldn't let me upload it (too big).
    Thank you

    OS - Windows 7 Home Premium (x64) Service Pack 1 (build 7601)
    x64
    Windows 7 is original OS
    Windows 7 is OEM version
    ~1.5 years old
    OS has never been installed

    1.40 gigahertz AMD A6-3400M APU with Radeon HD Graphics
    Video Card -
    AMD Radeon HD 6650M
    Motherboard - ASUSTeK Computer Inc. K53TA 1.0
    BIOS:
    American Megatrends Inc. 206 07/20/2011
    Manufacturer - ASUSTeK Computer Inc.
    Model # -
    K53TA 1.0

  4. #4

    Join Date
    Feb 2012
    Posts
    2,086
    Blog Entries
    7

    Re: BSOD twice today within an hour.....both caused by different things (maybe)

    Connot run dump files on this system - if they're not run by others, I'll do them when I get home this afternoon

    Get all Windows Updates - visit several times to make sure you've got them all.

    VMWare virtual ethernet adapters are disabled. Please enable them, then update them. If so desired, you can feel free to disable them again

    MSINFO32 shows several Clock Watchdog Timeout errors.

    Trend Micro appears to date from 2010 - please update to the latest version immediately

    Visit the manufacturer's website and update all drivers. Many of your drivers date from 2009 - around the time SP1 came out.

    Run these free hardware diagnostics: Hardware Diagnostics
    Post back with the results of the tests and we'll move on from there.

  5. #5
    Tekno Venus's Avatar
    Join Date
    Jul 2012
    Location
    UK
    Age
    20
    Posts
    5,807
    • specs System Specs
      • Manufacturer:
        Custom Built
      • Motherboard:
        ASUS Z170I ITX
      • CPU:
        Intel Core i7 6700K
      • Memory:
        16GB DDR4
      • Hard Drives:
        500GB Samsung 850 EVO, 2TB Seagate HDD
      • Power Supply:
        450W Corsair SFX
      • Case:
        Silverstone SG13 ITX
      • Cooling:
        Corsair H60i
      • Display:
        Dell U2715H - 2160x1440 27 inch
      • Operating System:
        Windows 10 Pro x64

    Re: BSOD twice today within an hour.....both caused by different things (maybe)

    Hello again,

    I see usasma has posted at the same time. Follow his advice as well as mine. :)

    Outdated 3rd Party Drivers
    These drivers are ones manufactured by a 3rd Party (not Microsoft) and are either outdated or known causes of BSOD's. To update the drivers to the latest version, follow the links below the drivers to find the manufacturer's website and the download location. If an update cannot be found, please uninstall the related software or device. The software can be uninstalled via Control Panel and the device through Device Manager. If you are stuck and require help, please let me know.

    Sentinel64.sys Mon Jun 2 07:14:55 2008 (48438FDF)
    Rainbow Tech/SafeNet USB Security Device
    http://www.sysnative.com/drivers/driver.php?id=Sentinel64.sys

    BSOD Analysis

    Both the BSOD's you gave me are 0x101 bugchecks -- CLOCK_WATCHDOG_TIMEOUT. This bugcheck cannot be analysed properly with a minidump file, like the ones you have attached to your post.

    Could you please navigate to C:\Windows\ and upload the MEMORY.DMP file?

    If that file doesn't exist, you need to enable the setting to create it on new BSOD's. To do so:

    1. Click Start, right-click Computer -> Properties.
    2. Click Advanced system settings, and then click the Advanced tab.
    3. Click Settings under the Writing debugging information area, and then make sure Kernel Memory Dump is selected.


    The MEMORY.dmp file will be quite large, so you will need to upload it to a 3rd party site. I recommend using SkyDrive or Dropbox to do so. Once you have uploaded this file, I will perform detailed analysis. I will warn you though, this BSOD may take some time and effort to fix, but if you co-operate, we will solve it! :)

    Regards,
    Stephen

    The following is for information purposes only. This is the important and relevant information from your dump files. All this should have been discussed earlier in my post.
    Code:
    **************************Fri Feb  1 17:11:09.720 2013 (UTC + 0:00)**************************
    
    Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\Biggwurmm\020113-29952-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 System Uptime:0 days 0:49:26.687 Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BugCheck 101, {31, 0, fffff88002fd5180, 3} BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002fd5180, The PRCB address of the hung processor. Arg4: 0000000000000003, 0. BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC PROCESS_NAME: System FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BIOS Version 206 BIOS Release Date 07/20/2011 Manufacturer ASUSTeK Computer Inc. Product Name K53TA จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ`` **************************Fri Feb 1 16:19:56.641 2013 (UTC + 0:00)************************** Loading Dump File [C:\Users\Stephen\Documents\Computer Stuff\BSOD Dumps\Sysnative\Biggwurmm\020113-79529-01.dmp] Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 System Uptime:1 days 12:34:12.785 Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BugCheck 101, {31, 0, fffff88002f64180, 2} BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101) Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002f64180, The PRCB address of the hung processor. Arg4: 0000000000000002, 0. BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BIOS Version 206 BIOS Release Date 07/20/2011 Manufacturer ASUSTeK Computer Inc. Product Name K53TA จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    koolkat77 says thanks for this.


Similar Threads

  1. BSOD: BugCheck D1, Probably Caused By RDYBOOST.SYS
    By mgmorey in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 05-29-2013, 12:05 PM
  2. BSOD caused DirectX 9 application
    By noxz in forum BSOD, Crashes, Kernel Debugging
    Replies: 1
    Last Post: 10-15-2012, 05:00 PM
  3. BSOD, caused by software?
    By FallDown in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 07-28-2012, 08:49 AM
  4. BSOD - Few things to try while waiting...
    By loda117 in forum BSOD, Crashes, Kernel Debugging
    Replies: 22
    Last Post: 05-09-2012, 12:03 PM

Log in

Log in