Windows 8 and 8.1 Forums


BSOD happens randomly. A clock interrupt was not recieved

  1. #1


    Posts : 7
    Windows 7 Ultimate 64 bit

    BSOD happens randomly. A clock interrupt was not recieved


    Hi Everyone
    I've been getting this BSOD quite alot since i built my pc. It has been happening for as long as i can remember, and seems to happen randomly too. The last few times it has happened was while streaming videos on google chrome, and watching videos on a usb drive. Ive attached the dump file so you can have a look. Any help would be greatly appreciated!

    Thanks
    Attachment 59229

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Please provide this report:
    License Information (Windows 7 and earlier)

    Please provide the MGADiag report according to these instructions (from this post: Product Key Number - Uninstall and Deactivate in Windows - Page 3 - Windows 7 Help Forums ):
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
    There are no memory dumps in the uploaded reports, please do this:
    Upload Dump Files:
    NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
    Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
    Left click on the first minidump file.
    Hold down the "Shift" key and left click on the last minidump file.
    Right click on the blue highlighted area and select "Send to"
    Select "Compressed (zipped) folder" and note where the folder is saved.
    Upload that .zip file with your next post.

    If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

    If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

    Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

    Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDumpMore info on dump file options here: Overview of memory dump file options for Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2
    While waiting for a reply, please start with these free diagnostics: Hardware Diagnostics
      My System SpecsSystem Spec

  3. #3


    Posts : 7
    Windows 7 Ultimate 64 bit


    https://www.dropbox.com/s/1gwftnwi1z...59-01.dmp?dl=0

    Here is the only dump file that was in the folder. Hope this helps!
    Sorry I didnt reply, I thought the problem was fixed but it happened again today. I realised that it always happens when i am watching a video or listening to music off a USB stick.
      My System SpecsSystem Spec

  4. #4


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Not a problem, I get notified whenever you reply to this topic.

    Please provide this report:
    License Information (Windows 7 and earlier)

    Please provide the MGADiag report according to these instructions (from this post: Product Key Number - Uninstall and Deactivate in Windows - Page 3 - Windows 7 Help Forums ):
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
    What were the results of the hardware diagnostics?
      My System SpecsSystem Spec

  5. #5


    Posts : 7
    Windows 7 Ultimate 64 bit


    Here is the MGADiag report:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->


    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-XV3VV-FYFTP-6XY4C
    Windows Product Key Hash: SqJUFScGLiKd13hNiX+ErpcUuVs=
    Windows Product ID: 00426-292-6914116-85778
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {D49698FE-5D07-4E2F-811E-A957F06FDCFE}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.150202-1526
    TTS Error:
    Validation Diagnostic:
    Resolution Status: N/A


    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002


    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002


    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002


    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005


    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed


    File Scan Data-->


    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{D49698FE-5D07-4E2F-811E-A957F06FDCFE}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-6XY4C</PKey><PID>00426-292-6914116-85778</PID><PIDType>5</PIDType><SID>S-1-5-21-807313939-923010165-2981598496</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1201 </Version><SMBIOSVersion major="2" minor="5"/><Date>20130419000000.000000+000</Date></BIOS><HWID>286D3907018400F2</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>1BF8D8A9C9ACD86</Val><Hash>9g2cFime44GimOJ+Wlk57pXf6gQ=</Hash><Pid>89388-707-8166527-65978</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>


    Spsys.log Content: 0x80070002


    Licensing Data-->
    Software licensing service version: 6.1.7601.17514


    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00170-292-691411-00-2057-7600.0000-2062013
    Installation ID: 000226173096404771967081924623376013859882258123048072
    Processor Certificate URL: SpcService Web Service
    Machine Certificate URL: RacService Web Service
    Use License URL: UseLicenseService Web Service
    Product Key Certificate URL: PkcService Web Service
    Partial Product Key: 6XY4C
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 02/04/2015 19:45:35


    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 3:28:2015 12:38
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:




    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAAACAAAAAgABAAEA6GEqhCKDVPkQM1xBOJjK/PjgipuyghjYNJJ2Mg==


    OEM Activation 1.0 Data-->
    N/A


    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    APIC 041913 APIC1304
    FACP 041913 FACP1304
    HPET 041913 OEMHPET
    MCFG 041913 OEMMCFG
    OEMB 041913 OEMB1304
    SSDT A M I POWERNOW
      My System SpecsSystem Spec

  6. #6


    Posts : 7
    Windows 7 Ultimate 64 bit


    Oh, and memtest passed no problem. The only problem is that memtest said my RAM is DDR2 and running at 800mhz, although I know that I have DDR3 running at 1600mhz!
      My System SpecsSystem Spec

  7. #7


    Posts : 5,139
    Win8.1Pro - Finally!!!


    What about the other hardware diagnostics (anti-malware, hard drive, video, Prime95, video2, CPU stress)?

    Still looks like a hardware error - but the AMD chipset drivers are very old (from as early as 2009). They may not be compatible w/Win8 or 8.1
    Please update them immediately to a version that is compatible w/Win8.1

    I also have to wonder about the legitimacy of your OS. If it is pirated, it can easily cause these errors - so we'd just be wasting our time here.
    Also, if it is an OS issue, then the best thing would be to wipe the hard drive clean and install a fresh copy of Windows.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Mar 31 11:21:20.523 2015 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\033115-11559-01.dmp]
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    System Uptime:0 days 0:00:06.850
    Probably caused by :AuthenticAMD
    BugCheck 124, {0, fffffa8004cc7038, 0, 0}
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR (124)
    Arguments: 
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004cc7038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    BUGCHECK_STR:  0x124_AuthenticAMD
    FAILURE_BUCKET_ID: WRONG_SYMBOLS
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue Mar 31 11:21:20.523 2015 (UTC - 4:00)**************************
    AtiPcie.sys        Mon Aug 24 04:25:26 2009 (4A924E76)
    amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    MpFilter.sys       Sat Nov  1 15:22:16 2014 (545532E8)
    
    http://www.carrona.org/drivers/driver.php?id=AtiPcie.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys


    Here's the STOP 0x124 info:
    Opened log file 'C:\Users\John\AppData\Local\Temp\SysnativeBSODApps\25356\kdc\outkdOutput1.3.txt'

    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\John\SysnativeBSODApps\033115-11559-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328d890
    Debug session time: Tue Mar 31 11:21:20.523 2015 (UTC - 4:00)
    System Uptime: 0 days 0:00:06.850
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
    Loading Kernel Symbols
    .....................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list

    ************* Symbol Loading Error Summary **************
    Module name Error
    ntkrnlmp The system cannot find the file specified

    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8004cc7038, 0, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_MMPTE ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : AuthenticAMD

    Followup: MachineOwner
    ---------

    3: kd> !niemiro.auto_errrec; q
    ===============================================================================
    Common Platform Error Record @ fffffa8004cc7038
    -------------------------------------------------------------------------------
    Record Id : 01d06bc6547a53c8
    Severity : Fatal (1)
    Length : 928
    Creator : Microsoft
    Notify Type : Machine Check Exception
    Timestamp : 3/31/2015 15:21:20 (UTC)
    Flags : 0x00000002 PreviousError

    ===============================================================================
    Section 0 : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor @ fffffa8004cc70b8
    Section @ fffffa8004cc7190
    Offset : 344
    Length : 192
    Flags : 0x00000001 Primary
    Severity : Fatal

    Proc. Type : x86/x64
    Instr. Set : x64
    Error Type : BUS error
    Operation : Generic
    Flags : 0x00
    Level : 3
    CPU Version : 0x0000000000600f20
    Processor ID : 0x0000000000000002

    ===============================================================================
    Section 1 : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor @ fffffa8004cc7100
    Section @ fffffa8004cc7250
    Offset : 536
    Length : 128
    Flags : 0x00000000
    Severity : Fatal

    Local APIC Id : 0x0000000000000002
    CPU Id : 20 0f 60 00 00 08 06 02 - 0b 32 98 3e ff fb 8b 17
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_XPF_PROCESSOR_ERROR_SECTION ***
    *** ***
    *************************************************************************

    Proc. Info 0 @ fffffa8004cc7250

    ===============================================================================
    Section 2 : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor @ fffffa8004cc7148
    Section @ fffffa8004cc72d0
    Offset : 664
    Length : 264
    Flags : 0x00000000
    Severity : Fatal

    *************************************************************************
    *** ***
    *** ***
    *** Either you specified an unqualified symbol, or your debugger ***
    *** doesn't have full symbol information. Unqualified symbol ***
    *** resolution is turned off by default. Please either specify a ***
    *** fully qualified symbol module!symbolname, or enable resolution ***
    *** of unqualified symbols by typing ".symopt- 100". Note that ***
    *** enabling unqualified symbol resolution with network symbol ***
    *** server shares in the symbol path may cause the debugger to ***
    *** appear to hang for long periods of time when an incorrect ***
    *** symbol name is typed or the network symbol server is down. ***
    *** ***
    *** For some commands to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    Error : BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR (Proc 2 Bank 5)
    Status : 0xb480000000030e0f
    Address : 0x0000000000000011
    Misc. : 0x0000000000000000

    quit:

    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My System SpecsSystem Spec

  8. #8


    Posts : 7
    Windows 7 Ultimate 64 bit


    Thanks for all your help so far!
    Anti Virus and Anti Malware scans came back clean and prime95 ran for 30 mins before i turned it off. I updated my chipset drivers from the AMD website (although i'm not sure if they were the correct ones), and I updated windows from control panel. The BSOD still happens though.
    Im pretty sure my copy of windows 7 is genuine. I had a friend install it for me since he had the disc and product key. I recently bought an SSD and cloned windows to it using EaseUS, but the BSOD was happening before this anyway.
    I havent run the hard drive test because there was no link to a sandisk ssd.
    Im concerned about memtest saying I only have 800mhz ddr2 ram though. Is that normal?
      My System SpecsSystem Spec

  9. #9


    Posts : 7
    Windows 7 Ultimate 64 bit


    Ok, I have made a discovery. The BSOD doesnt happen in safe mode, or safe mode with networking!Im guessing that this rules out hardware problems, phew! Hope this helps.
    Also, sometimes my PC just restarts without showing a BSOD, but it still restarts in the same situation (playing video through usb), so im guessing the restart and the BSOD are related to the same problem.
      My System SpecsSystem Spec

  10. #10


    I blame the pie crumbs
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
BSOD happens randomly. A clock interrupt was not recieved
Related Threads
Hi I am getting BSODs - Kernal Security check / Clock Watchdog Timeout usually playing battlefield 4. File uploaded, Hope somebody can help.
BSOD for the clock watchdog timeout error in BSOD Crashes and Debugging
Ok so my bf who has a pretty nice computer with win 8 on it also its a OEM system. He keeps getting the BSOD for the clock watchdog timeout error and he tried everything that you had posted about before we tried it all. Im sad that we cant get it to work he is my gaming partner lol. I hope to get...
Get multiple BSOD's everyday. Interrupt Exception Not Handled KMODE Exception Not Handled Unexpected Kernel Mode Trap System Service Exception All of them result in a file called ntoskrnl.exe being highlighted in BlueScreenView Other files highlighted in KMODE Dump were athw8x.sys,...
As above - i get these two errors sometimes when I'm merely surfing the web.. or when i'm editing photos in lightroom as well. crash files attached as requested. kindly help! thanks!
DPC_Watchdog_Violation (recieved frequently) in BSOD Crashes and Debugging
Many times in a day I receive this error. Mostly when Gaming, watching videos, etc. However, on occasion I receive this error when doing nothing. Just sitting at the desktop. Please reply quickly, this is beginning to become a big problem.
OMG...in asus site there is not my lap top drivers on win 8. my lap top model is:ASUS X42JY what should I do???plz some one help me..how can I find my lap top drivers on win 8 to install wndows 8
Hi all i have received 2 e-mails i wanted to share with you folks Received the Wed 8/15/2012 16:37 Received the Wed 8/15/2012 16:37 http://image.email.microsoftemail.com/lib/feed1d7871600d/m/1/flash-header-v2.gif Customize MSDN Flash | Unsubscribe
Eight Forums Android App Eight Forums IOS App Follow us on Facebook