none
BSOD/Crashes New PC and New install of Windows 7

    Question

  • I have a new system and having an issue with it.  I had some troubles when I first got the system my GPU and PSU were both bad.  I hae replaced both and have had all the hardware checked to make sure they are working correctly.  Once this was done I installed installed Windows 7, updated all my drivers that I needed and updated Windows.  Everything was running fine no errors or anything I could find with it wrong.  At this time I had not installed any progrmas at all.  I took a break for a few mins and when I came back the CP had shutdown for no reason.  I restarted the system and everything looked fine.  So I went ahead and installed Steam (application).  As I was installing a game on steam the PC froze and shutdown.  No error message nothing at the time in the events.   Now after the installation the system crashes or BSOD pretty regularly while nothing is running or if I sit on an application to long.  I have checked everything and could not find the problem.  SO I went ahead and uninstalled Steam figuring there must be some issue with it.  After uninstalling it and restarting the system I still got the BSOD and crashes.  Now thinking it was a tempature issue I checked the temps for the GPU, CPU and and the fan temps.  Nothing was out of the maximum ranges.  I have compeletly removed everything double, triple checked that all the drivers are up to date but I still get these crashes and freezes.

    I have a Memory.dmp file and minidump if anyone would like to look into them and see if they could help me with this.  I also included a list of my specs

    I am at my wits end and exhausted over this. Would greatly appreciate any help if someone has had a similar problem or may know a fix for this. Again everything is updated and all the hardware is working properly.

    CPU: AMD FX-8150 3.60 GHz Eight-Core AM3+ CPU 8MB L2 Cache & Turbo Core Technology
    VIDEO: AMD Radeon HD 6970 2GB GDDR5 16X PCIe Video Card
    MOTHERBOARD: * [CrossFireX] GigaByte GA-970A-D3 AMD 970 Socket AM3+ ATX Mainboard w/ On/Off Charge, 7.1 Audio, GbLAN, USB3.0, SATA-III RAID, 2 Gen2 PCIe X16, 3 PCIe X1 & 2 PCI
    OS: Microsoft(R) Windows 7 Home Premium (64-bit Edition)
    MEMORY: 8GB (4GBx2) DDR3/1600MHz Dual Channel Memory (Kingston HyperX)
    POWERSUPPLY: 1,000 Watts - Raidmax RX-1000AE 80 Plus Gold Power Supply
    FAN: Asetek 510LC Liquid Cooling System 120MM Radiator & Fan (Enhanced Cooling Performance + Extreme Silent at 20dBA) (Single Standard 120MM Fan)
    FAN: 3 Standard Blue LED 120MM Fans (Push - Pull)
    HDD: 1TB SATA-III 6.0Gb/s 32MB Cache 7200RPM HDD (Single Drive)
    SOUND: HIGH DEFINITION ON-BOARD 7.1 AUDIO

    Sunday, February 19, 2012 12:09 AM

Answers

  • The last dump was much the same as the previous, just that the corrupted region in memory wasn't named as being previously allocated to a specific driver. Not much help (to me at least).

    If you now spend some time using the machine normally, and you hit BSODs less frequently than before, or don't get any, it's probably that by doing the uninstall/disable/change power settings/update cycle earlier has reduced the occurance of the conditions needed to trigger the error.

    I'm really way over my experience level with this, even with all the data available from usasma and friends that I've checked on so far aiding me/us.

    I'm guessing that if the problem continues, replacement of 'board, CPU and possibly BIOS would be first up in the next series of troubleshooting steps.

    *******************************************************************************
    *                                                                             *
    *                        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
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    STACK_TEXT:  
    fffff880`009a9628 fffff800`031318c9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
    fffff880`009a9630 fffff800`030e4497 : 00000000`00000000 fffff800`00000002 00000000`00026160 fffffa80`0985cb60 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff880`009a96c0 fffff800`0301e895 : fffff800`03044460 fffff880`009a9870 fffff800`03044460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`009a97c0 fffff800`030d6173 : 00000000`39e0ea09 fffff800`0324fe80 fffffa80`0699ec80 fffff800`031de8ee : hal!HalpHpetClockInterrupt+0x8d
    fffff880`009a97f0 fffff800`03110327 : fffff800`0324fe80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`009a9980 fffff800`030df7cc : 00000000`00000000 fffff880`009a9ab8 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x93
    fffff880`009a99c0 fffff800`030a1469 : 00000000`00000008 00000000`000000ff fffffa80`05bf49d0 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
    fffff880`009a9a90 fffff800`030a1cb7 : ffffffff`ffffffff 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
    fffff880`009a9ad0 fffff800`03374fee : fffffa80`069da040 00000000`00000080 fffffa80`069b6890 fffff800`030cb5d9 : nt!MmZeroPageThread+0x83a
    fffff880`009a9c00 fffff800`030cb5e6 : fffff800`0324fe80 fffffa80`069da040 fffff800`0325dcc0 8b49c033`45c93345 : nt!PspSystemThreadStartup+0x5a
    fffff880`009a9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

    Sunday, February 19, 2012 8:49 PM
  • Hi,

    According to your *.dump files, I find that there are some hardware driver is not compatible with Windows 7.

    First, you need to update the latest drivers for your computer, to do that you may contact your computer manufacturer.

    Then, please do a hardware clean boot to isolate which device is causing the issue.  For doing hardware clean boot do the following steps.
    a) Unplug all the external Devices
    b) Start the System in Safe mode. (Pressing the F8 key while the computer restarts)
    c) Go to Device manger
    Device that can be disabled for doing a Hardware clean boot are
    1. Video Cards
    2. Sound Card
    3. Network Card
    4. USB Devices and controller (Please don’t do this if you are using USB keyboard or Mouse or Wireless Keyboard or mouse)
    5. CD and DVD
    6. Modems
    7. Ports (serial and parallel)
    After doing this if you are able to Boot in Normal Mode try to enable the device one by one and check out which device is causing the issue .Try to install the latest driver for that device or contact the hardware vendor.


    Here is an article can be referred to.

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/defaultbucketid-vistadriverfault/e8add1ef-0304-45ba-802a-ef2f11590c2d

    Hope that helps.




    Monday, February 20, 2012 9:13 AM

All replies

  • It reads like a problem with the ASACPI.sys (or similar) motherboard driver/utility. Try using Driverview by Nirsoft.net to look at the drivers loaded by date, any 3rd party drivers should really be from about 8 months old or newer.

    Uploading your latest dump files from C:\Windows\Minidump to Skydrive and posting the link back here will help someone to analyze it further - make the dumps available to the Public.

    Sunday, February 19, 2012 12:54 AM
  • Went ahead and uploaded the minidump and the driver view.  Thanks!

    Minidump (Public)

    DriverViewSave

    CPU-Z Save
    • Edited by killinfreak Sunday, February 19, 2012 2:01 AM
    Sunday, February 19, 2012 1:46 AM
  • It reads like a problem with the ASACPI.sys (or similar) motherboard driver/utility. Try using Driverview by Nirsoft.net to look at the drivers loaded by date, any 3rd party drivers should really be from about 8 months old or newer.

    Uploading your latest dump files from C:\Windows\Minidump to Skydrive and posting the link back here will help someone to analyze it further - make the dumps available to the Public.

    Went ahead and uploaded the minidump and the driver view.  Thanks!

    Minidump (Public)

    DriverViewSave

    CPU-Z Save

    • Edited by killinfreak Sunday, February 19, 2012 2:00 AM
    Sunday, February 19, 2012 1:47 AM
  • I checked the drivers loaded in one of the dumps:

    SaiK0728.sys Saitek driver - might be from an OEM though - http://www.saitek.com/uk/down/drivers.php
    gdrv.sys Gigabyte Easy Saver - mobo power utility driver http://www.gigabyte.com.tw/Support/Motherboard/Driver_List.aspx <- this looks like the type of driver I was describing!
    The above predate the release of Windows 7; must be updated, disabled or uninstalled for troubleshooting.
    Rt64win7.sys Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false    There should be a more recent version of this, also check in Device Manager that it does not turn off to save power.
    AODDriver2.sys AMD Overdrive; also in EasyTune6 for Gigabyte motherboard http://game.amd.com/us-en/drivers_overdrive.aspx this might be problematic, probably unnecessary anyway, disable during troubleshooting.
    Other drivers are mostly from MSFT or recent, as in the last 8 months or less.

    Quick dump analysis, notice that something is causing the RealTek networking driver to corrupt "Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys ... ":

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 101, {19, 0, fffff880009eb180, 1}

    Unable 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
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880009eb180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  WinSAT.exe

    CURRENT_IRQL:  d

    STACK_TEXT:  
    fffff800`00ba2098 fffff800`030dc8c9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009eb180 : nt!KeBugCheckEx
    fffff800`00ba20a0 fffff800`0308f497 : fffffa80`00000000 fffff800`00000001 00000000`00026160 00000000`00000040 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff800`00ba2130 fffff800`035fb895 : fffff800`03621460 fffff800`00ba22e0 fffff800`03621460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`00ba2230 fffff800`03081173 : 00000000`00000000 fffffa80`0900d060 fffffa80`0900d1b8 fffffa80`090191b8 : hal!HalpHpetClockInterrupt+0x8d
    fffff800`00ba2260 fffff800`0308a7a0 : fffff800`031fae80 fffffa80`00000001 00000000`00000000 fffff800`00ba2518 : nt!KiInterruptDispatchNoLock+0x163
    fffff800`00ba23f0 fffff800`03022fbd : 00000000`00000014 fffff880`0927b000 00000000`00000000 fffff880`0927b068 : nt!KeFlushMultipleRangeTb+0x260
    fffff800`00ba24c0 fffff800`030236e3 : fffff880`0927b068 00000000`00000004 00000000`00000001 00000000`00000001 : nt!MiRemoveIoSpaceMap+0xe9
    fffff800`00ba25f0 fffff880`0485e177 : 00000000`30110000 00000000`00000001 fffffa80`087418d0 fffffa80`0873e000 : nt!MmUnmapIoSpace+0x83
    fffff800`00ba2640 00000000`30110000 : 00000000`00000001 fffffa80`087418d0 fffffa80`0873e000 fffffa80`0873e068 : Rt64win7+0x5e177
    fffff800`00ba2648 00000000`00000001 : fffffa80`087418d0 fffffa80`0873e000 fffffa80`0873e068 fffff880`0485e1e3 : 0x30110000
    fffff800`00ba2650 fffffa80`087418d0 : fffffa80`0873e000 fffffa80`0873e068 fffff880`0485e1e3 fffffa80`076734f0 : 0x1
    fffff800`00ba2658 fffffa80`0873e000 : fffffa80`0873e068 fffff880`0485e1e3 fffffa80`076734f0 fffff880`016943a2 : 0xfffffa80`087418d0
    fffff800`00ba2660 fffffa80`0873e068 : fffff880`0485e1e3 fffffa80`076734f0 fffff880`016943a2 fffffa80`07551bc8 : 0xfffffa80`0873e000
    fffff800`00ba2668 fffff880`0485e1e3 : fffffa80`076734f0 fffff880`016943a2 fffffa80`07551bc8 fffff880`01693958 : 0xfffffa80`0873e068
    fffff800`00ba2670 fffffa80`076734f0 : fffff880`016943a2 fffffa80`07551bc8 fffff880`01693958 fffff800`00ba2868 : Rt64win7+0x5e1e3
    fffff800`00ba2678 fffff880`016943a2 : fffffa80`07551bc8 fffff880`01693958 fffff800`00ba2868 00000000`00000000 : 0xfffffa80`076734f0
    fffff800`00ba2680 00000000`aaaaaaab : fffffa80`087418d0 fffff800`00ba2801 00000000`00000100 00000014`00000000 : tcpip!Ipv6pInterfaceSetTimeout+0x183
    fffff800`00ba2700 fffffa80`087418d0 : fffff800`00ba2801 00000000`00000100 00000014`00000000 fffff880`00000001 : 0xaaaaaaab
    fffff800`00ba2708 fffff800`00ba2801 : 00000000`00000100 00000014`00000000 fffff880`00000001 00000000`00000000 : 0xfffffa80`087418d0
    fffff800`00ba2710 00000000`00000100 : 00000014`00000000 fffff880`00000001 00000000`00000000 fffff800`031fae80 : 0xfffff800`00ba2801
    fffff800`00ba2718 00000014`00000000 : fffff880`00000001 00000000`00000000 fffff800`031fae80 fffffa80`0842c060 : 0x100
    fffff800`00ba2720 fffff880`00000001 : 00000000`00000000 fffff800`031fae80 fffffa80`0842c060 00000000`00000000 : 0x14`00000000
    fffff800`00ba2728 00000000`00000000 : fffff800`031fae80 fffffa80`0842c060 00000000`00000000 00000000`00000000 : 0xfffff880`00000001


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

    Similar thread over at TSF: http://www.techsupportforum.com/forums/f299/bsod-at-about-31-celsius-during-gaming-623853.html overclocking/bad or wrongly setup RAM/faulty hardware probably to blame there - remember, every case is individual - do as suggested at the top of the post to begin with. Test and report back.

    Sunday, February 19, 2012 2:31 AM
  • Saitek - yeah I did not research enough and while checking on this a bit ago I noticed that it was integrated into Windows now.  So I went ahead and deleted the driver, it was added through windows and is showing as the appropriate device now.

    Okay I uninstalled Gigabyte Easy Saver and Easy Tune6 both of those programs were the recomended installs from Gigabytes but I can them install later if need be.

    Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC - Showed the same version only diffrence was the dates one was June of last year and the one on their site is showing January of this year.  I went ahead and removed the driver and installed the new dated one.

    I will post back a minidump if it BSOD again.

    Thanks for your help so far!

    Sunday, February 19, 2012 3:21 AM
  • No BSOD yet but I did crash and this was in the Event View Log...

    Event View Error

    Sunday, February 19, 2012 3:38 AM
  • Where does that error time tie in with what you were doing? Was it immediately before the crash, after or during something else?

    Anything else unusual either side of it - or in the System log?

    Sunday, February 19, 2012 3:43 AM
  • As I was posting the first reply (replying to your reply) it just crashed (no bsod it just crashed) and that was what was in the system event log.

    But...

    Right after I posted the Event Error I did get a BSOD and another minidump but the timestamp for it was an hour ago but it just happened 10 mins ago.

    Here is the new minidump

    Newminidump


    the BSOD read as: IRQL_NOT_LESS_OR_EQUAL
    • Edited by killinfreak Sunday, February 19, 2012 3:54 AM
    Sunday, February 19, 2012 3:52 AM
  • Ok, downloading it now, can you filter both the Application and system logs to the last 24 hours, or week, export each of them as the native *evtx type and upload them please, I might have time to scan through them before hitting the sack.

    On the link I posted on the tail of the dump analysis there's a link, somewhere in  there, maybe in usasma's sig. but certainly in a post, there's a link to hardware diags, can you start prepping for those, run the CPU test first, overnight if you can. Then the memory test, 7+ passes.

    Sunday, February 19, 2012 3:58 AM
  • I did both for 7days filtered for Critical, Errors and Warnings only!

    ApplicationLog7days

    SystemLog7days

    I will get to working on the Hardware Diagnosis and post back the results.

    Again I want to thank you for your help!

    Sunday, February 19, 2012 4:06 AM
  • No worries :)

    Downloaded but I'm seriously flagging now, gonna try to unwind and sleep, I'll look in again after I can think straight ;)

    Sunday, February 19, 2012 4:18 AM
  • Well I spent most of my night running tests and here is the info that I have for them so far.

    Memtest86: Passed - ran completely through 8 Passes (can give all the info if need be)

    Furmark Benchmark:
        Burn in Test
        1920x1080 - 30fps
    FPS Min: 29
    FPS Max: 32
    FPS Avg: 30
    GPU-Z: Core 249mhz - mem: 150mhz - GPU Temp: 38*c
    GPU Powerdraw: 3W (0.900v x 4.250a)
    GPU1 - AMD Radeon HD 6970
    Core: 940mhz Mem: 1425mhz Temp: 70*c
    VDDC: 1.175v Fan SPeed: 48%
    GPU Load: 99% Memload: 0%
    Current temp: 71*c
    Min Temp: 40*c
    Max Temp: 72*c

    Hard Drive Test:
    SMART: Pass
    Short DST: Pass
    Long DST: Pass
    Short Generic: Pass
    Long Generic: Pass
    (checked firmware version: current)

    Prime95:
    When I ran this the first few seconds I got these errors-
    [Sat Feb 18 23:57:51 2012]
    FATAL ERROR: Rounding was 0.5, expected less than 0.4
    Hardware failure detected, consult stress.txt file.
    FATAL ERROR: Rounding was 0.5, expected less than 0.4
    Hardware failure detected, consult stress.txt file.
    FATAL ERROR: Rounding was 0.5, expected less than 0.4
    Hardware failure detected, consult stress.txt file.
    [Sun Feb 19 00:08:33 2012]
    Compare your results to other computers at http://www.mersenne.org/report_benchmarks
    AMD FX(tm)-8150 Eight-Core Processor           
    CPU speed: 7715.73 MHz, 8 cores
    CPU features: Prefetch, MMX, SSE, SSE2, SSE4, AVX
    L1 cache size: 16 KB
    L2 cache size: 2 MB, L3 cache size: 8 MB
    L1 cache line size: 64 bytes
    L2 cache line size: 64 bytes
    L1 TLBS: 32
    L2 TLBS: 1024
    Prime95 64-bit version 26.6, RdtscTiming=1
    Best time for 768K FFT length: 12.741 ms., avg: 12.835 ms.
    Best time for 896K FFT length: 14.964 ms., avg: 15.046 ms.
    Best time for 1024K FFT length: 16.635 ms., avg: 16.690 ms.
    Best time for 1280K FFT length: 21.850 ms., avg: 21.880 ms.
    Best time for 1536K FFT length: 27.153 ms., avg: 27.233 ms.
    Best time for 1792K FFT length: 31.789 ms., avg: 31.872 ms.
    Best time for 2048K FFT length: 35.786 ms., avg: 35.862 ms.
    Best time for 2560K FFT length: 44.581 ms., avg: 44.626 ms.
    Best time for 3072K FFT length: 55.371 ms., avg: 55.409 ms.
    Best time for 3584K FFT length: 69.823 ms., avg: 69.907 ms.
    Best time for 4096K FFT length: 72.982 ms., avg: 73.306 ms.
    Best time for 5120K FFT length: 100.143 ms., avg: 100.567 ms.
    [Sun Feb 19 01:29:06 2012]

    And I will be running it again overnight and will post back the rest.

    Sunday, February 19, 2012 7:43 AM
  • The Furmark result was what I'd anticipated, I'm unsure as to how to interpret it though.

    A couple of useful links to read until I find time to try to analyze the latest data:

    http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101-clock_watchdog_timeout-troubleshtg.html

    http://www.sevenforums.com/crash-lockup-debug-how/63320-stop-0x116-video_tdr_error-troubleshooting.html

    Sunday, February 19, 2012 3:57 PM
  • I have been running Prime95 for a good while with no other errors.  I did get another crash this morning but havent since.

    I also ran a couple of those CPU Stress Tests on one of the links and everything was fine no errors, crashes or BSOD.

    Sunday, February 19, 2012 8:14 PM
  • The last dump was much the same as the previous, just that the corrupted region in memory wasn't named as being previously allocated to a specific driver. Not much help (to me at least).

    If you now spend some time using the machine normally, and you hit BSODs less frequently than before, or don't get any, it's probably that by doing the uninstall/disable/change power settings/update cycle earlier has reduced the occurance of the conditions needed to trigger the error.

    I'm really way over my experience level with this, even with all the data available from usasma and friends that I've checked on so far aiding me/us.

    I'm guessing that if the problem continues, replacement of 'board, CPU and possibly BIOS would be first up in the next series of troubleshooting steps.

    *******************************************************************************
    *                                                                             *
    *                        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
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88002f65180, The PRCB address of the hung processor.
    Arg4: 0000000000000002, 0.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    STACK_TEXT:  
    fffff880`009a9628 fffff800`031318c9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
    fffff880`009a9630 fffff800`030e4497 : 00000000`00000000 fffff800`00000002 00000000`00026160 fffffa80`0985cb60 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff880`009a96c0 fffff800`0301e895 : fffff800`03044460 fffff880`009a9870 fffff800`03044460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`009a97c0 fffff800`030d6173 : 00000000`39e0ea09 fffff800`0324fe80 fffffa80`0699ec80 fffff800`031de8ee : hal!HalpHpetClockInterrupt+0x8d
    fffff880`009a97f0 fffff800`03110327 : fffff800`0324fe80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`009a9980 fffff800`030df7cc : 00000000`00000000 fffff880`009a9ab8 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x93
    fffff880`009a99c0 fffff800`030a1469 : 00000000`00000008 00000000`000000ff fffffa80`05bf49d0 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
    fffff880`009a9a90 fffff800`030a1cb7 : ffffffff`ffffffff 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
    fffff880`009a9ad0 fffff800`03374fee : fffffa80`069da040 00000000`00000080 fffffa80`069b6890 fffff800`030cb5d9 : nt!MmZeroPageThread+0x83a
    fffff880`009a9c00 fffff800`030cb5e6 : fffff800`0324fe80 fffffa80`069da040 fffff800`0325dcc0 8b49c033`45c93345 : nt!PspSystemThreadStartup+0x5a
    fffff880`009a9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

    Sunday, February 19, 2012 8:49 PM
  • Okay well I will talk with AMD, start from there and work my way down the list :(.  Thanks for your help, I will post back the findings if I  get it corrected.

    Again thank you for your help.

     
    Sunday, February 19, 2012 8:57 PM
  • Good luck, any further queries, please bump the thread and I'll respond as fast as I can.

    Currently working through your event logs so there may be a later update from me.

    Sunday, February 19, 2012 9:00 PM
  • Hi,

    According to your *.dump files, I find that there are some hardware driver is not compatible with Windows 7.

    First, you need to update the latest drivers for your computer, to do that you may contact your computer manufacturer.

    Then, please do a hardware clean boot to isolate which device is causing the issue.  For doing hardware clean boot do the following steps.
    a) Unplug all the external Devices
    b) Start the System in Safe mode. (Pressing the F8 key while the computer restarts)
    c) Go to Device manger
    Device that can be disabled for doing a Hardware clean boot are
    1. Video Cards
    2. Sound Card
    3. Network Card
    4. USB Devices and controller (Please don’t do this if you are using USB keyboard or Mouse or Wireless Keyboard or mouse)
    5. CD and DVD
    6. Modems
    7. Ports (serial and parallel)
    After doing this if you are able to Boot in Normal Mode try to enable the device one by one and check out which device is causing the issue .Try to install the latest driver for that device or contact the hardware vendor.


    Here is an article can be referred to.

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/defaultbucketid-vistadriverfault/e8add1ef-0304-45ba-802a-ef2f11590c2d

    Hope that helps.




    Monday, February 20, 2012 9:13 AM
  • UPDATE:

    I have had the CPU (AMD FX-8150 Zambezi 2GB DDR5) taken out, checked and its seems this is the culprit.  Seems the second core is having a problem when starting up causing certain apps to freeze, crash or bsod.  If its able to start up it runs fine but its getting it to.  Everything that we did to it as soon as the second core started it failed.  So getting ahold of the manufacturer and having a new one sent.  Everything else was checked and seemed to be working just fine.  Keeping my fingers crossed that this was it and my headache will finally be over.

    Thanks again satrow for your help!

    Monday, February 20, 2012 11:18 PM
  • No problem, let's hope the next hardware combo is compatible ;)
    Monday, February 20, 2012 11:22 PM