I have been having BSOD issues for the past 3 days now. It started not long after i had started playing on Minecraft 1.3.1 with CJB's mod pack installed. After I started getting BSOD's I went and updated my drivers for my graphics card (thinking that was the problem because i had not recently updated them) and that is all i have done so far. I am also still able to log into windows normally.
Hello Arskann and welcome to Sevenforums.
BSOD Analyse
Be aware of these drivers
tifsfilt.sysCode:tifsfilt.sys Wed Aug 29 14:37:29 2007 (46D56889) timntr.sys Wed Aug 29 14:38:23 2007 (46D568BF) tdrpman.sys Mon Nov 12 14:36:33 2007 (473856E1) snapman.sys Thu Nov 22 09:19:33 2007 (47453B95)
timntr.sys
tdrpman.sys
snapman.sys
It appears they're a legacy of Acronis True Image (also included in Seagate DiscWizard).
BCCode CLOCK_WATCHDOG_TIMEOUT
This code can indicate a lot of things. Usually it's a driver hogging on the CPU, but before diagnosing the drivers, we're asking people to do a Memtest86+.
Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.
WarningNote that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.
To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.
Memtest86+ - Advanced Memory Diagnostic Tool
Also one of your crashes points an image that belongs to Teamspeak.
Best Regards,Code:Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 System Uptime: 0 days 1:26:05.411 Use !analyze -v to get detailed debugging information. BugCheck 101, {21, 0, fffff880009b2180, 4} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) CLOCK_WATCHDOG_TIMEOUT (101) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: ts3client_win6 STACK_TEXT: fffff880`0b9284d8 fffff800`032e7efa : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx fffff880`0b9284d8 fffff800`032e7efa : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx fffff880`0b9284e0 fffff800`0329acd7 : fffffa80`00000000 fffff800`00000004 00000000`00002710 fffffa80`07470000 : nt! ?? ::FNODOBFM::`string'+0x4e2e fffff880`0b928570 fffff800`03804895 : fffff800`0382a460 fffff880`0b928720 fffff800`0382a460 fffff700`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0b928670 fffff800`0328d713 : 00000000`9b131082 fffff800`03403e80 fffff800`03403e80 fffff680`00016b00 : hal!HalpHpetClockInterrupt+0x8d fffff880`0b9286a0 fffff800`032c28c1 : fffff800`03403e80 fffffa80`00000000 00000000`00000001 fffff880`0b9288f8 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0b928830 fffff800`032c3ea9 : 00000000`00000000 00000000`02d60fff fffff880`00000000 fffff880`00000000 : nt!MiDeleteVirtualAddresses+0x7f0 fffff880`0b9289f0 fffff800`035a3ec1 : fffffa80`07f428b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9 fffff880`0b928b10 fffff800`035a42c3 : 0000007f`00000000 00000000`02d60000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1 fffff880`0b928bd0 fffff800`03290453 : 00000000`00000000 00000000`02d60004 fffffa80`0ab7db30 00000000`02d60000 : nt!NtUnmapViewOfSection+0x5f fffff880`0b928c20 00000000`773015ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0413f828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773015ba FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE sysinfo: unknown error 80004005 [SMBIOS Data Tables v2.5] [DMI Version - 0] [2.0 Calling Convention - No] [Table Size - 1825 bytes] [BIOS Information (Type 0) - Length 24 - Handle 0000h] Vendor American Megatrends Inc. BIOS Version V1.9 BIOS Starting Address Segment f000 BIOS Release Date 04/02/2011 BIOS ROM Size 200000 BIOS Characteristics 04: - ISA Supported 07: - PCI Supported 09: - Plug and Play Supported 11: - Upgradeable FLASH BIOS 12: - BIOS Shadowing Supported 14: - ESCD Supported 15: - CD-Boot Supported 16: - Selectable Boot Supported 17: - BIOS ROM Socketed 19: - EDD Supported 23: - 1.2MB Floppy Supported 24: - 720KB Floppy Supported 25: - 2.88MB Floppy Supported 26: - Print Screen Device Supported 27: - Keyboard Services Supported 28: - Serial Services Supported 29: - Printer Services Supported 30: - CGA/Mono Services Supported 32: - BIOS Vendor Reserved BIOS Characteristic Extensions 00: - ACPI Supported 01: - USB Legacy Supported 04: - LS120-Boot Supported 05: - ATAPI ZIP-Boot Supported 08: - BIOS Boot Specification Supported 10: - Specification Reserved BIOS Major Revision 8 BIOS Minor Revision 15 EC Firmware Major Revision 255 EC Firmware Minor Revision 255 [System Information (Type 1) - Length 27 - Handle 0001h] Manufacturer MSI Product Name MS-7640 Version 1.0 Serial Number UUID 00000000-0000-0000-0000-000000000000 Wakeup Type Power Switch SKUNumber To Be Filled By O.E.M. Family To Be Filled By O.E.M. [BaseBoard Information (Type 2) - Length 15 - Handle 0002h] Manufacturer MSI Product 890FXA-GD70 (MS-7640) Version 1.0 Serial Number Asset Tag Feature Flags 09h 1757887860: - °?3 1757887820: - °?3 Location To Be Filled By O.E.M. Chassis Handle 0003h Board Type 0ah - Processor/Memory Module Number of Child Handles 0 [System Enclosure (Type 3) - Length 21 - Handle 0003h] Manufacturer MSI Chassis Type Desktop Version 1.0 Serial Number Asset Tag Number Bootup State Safe Power Supply State Safe Thermal State Safe Security Status None OEM Defined 0 Height 0U Number of Power Cords 1 Number of Contained Elements 0 Contained Element Size 0 [Processor Information (Type 4) - Length 40 - Handle 0004h] Socket Designation CPU1 Processor Type Central Processor Processor Family ech - Specification Reserved Processor Manufacturer AMD Processor ID a00f1000fffb8b17 Processor Version AMD Phenom(tm) II X6 1100T Processor Processor Voltage 8eh - 1.4V External Clock 200MHz Max Speed 3300MHz Current Speed 3300MHz Status DisabledByPOST Populated Processor Upgrade Specification Reserved L1 Cache Handle 0005h L2 Cache Handle 0006h L3 Cache Handle 0007h Serial Number Asset Tag Number Part Number To Be Filled By O.E.M. [Cache Information (Type 7) - Length 19 - Handle 0005h] Socket Designation L1-Cache Cache Configuration 0180h - WB Enabled Int NonSocketed L1 Maximum Cache Size 0300h - 768K Installed Size 0300h - 768K Supported SRAM Type 0010h - Pipeline-Burst Current SRAM Type 0010h - Pipeline-Burst Cache Speed 1ns Error Correction Type Specification Reserved System Cache Type Unified Associativity 2-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 0006h] Socket Designation L2-Cache Cache Configuration 0181h - WB Enabled Int NonSocketed L2 Maximum Cache Size 0c00h - 3072K Installed Size 0c00h - 3072K Supported SRAM Type 0010h - Pipeline-Burst Current SRAM Type 0010h - Pipeline-Burst Cache Speed 1ns Error Correction Type Specification Reserved System Cache Type Unified Associativity 16-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 0007h] Socket Designation L3-Cache Cache Configuration 0182h - WB Enabled Int NonSocketed L3 Maximum Cache Size 1800h - 6144K Installed Size 1800h - 6144K Supported SRAM Type 0010h - Pipeline-Burst Current SRAM Type 0010h - Pipeline-Burst Cache Speed 1ns Error Correction Type Specification Reserved System Cache Type Unified Associativity Other [Physical Memory Array (Type 16) - Length 15 - Handle 0028h] Location 03h - SystemBoard/Motherboard Use 03h - System Memory Memory Error Correction 03h - None Maximum Capacity 8388608KB Memory Error Inf Handle [Not Provided] Number of Memory Devices 4 [Memory Array Mapped Address (Type 19) - Length 15 - Handle 0029h] Starting Address 00000000h Ending Address 008dffffh Memory Array Handle 0028h Partition Width 01 [Memory Device (Type 17) - Length 27 - Handle 002ah] Physical Memory Array Handle 0028h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM1 Bank Locator BANK0 Memory Type 01h - Other Type Detail 0080h - Synchronous Speed 1513MHz Manufacturer Corsair Serial Number Asset Tag Number Part Number CMX8GX3M2A1333C9 [Memory Device (Type 17) - Length 27 - Handle 002ch] Physical Memory Array Handle 0028h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM2 Bank Locator BANK1 Memory Type 01h - Other Type Detail 0080h - Synchronous Speed 1513MHz Manufacturer Corsair Serial Number Asset Tag Number Part Number CMX8GX3M2A1333C9 [Memory Device (Type 17) - Length 27 - Handle 002eh] Physical Memory Array Handle 0028h Memory Error Info Handle [Not Provided] Total Width [Unknown] Data Width 64 bits Size [Not Populated] Form Factor 01h - Other Device Set [None] Device Locator DIMM3 Bank Locator BANK2 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer Manufacturer02 Serial Number Asset Tag Number Part Number ModulePartNumber02 [Memory Device (Type 17) - Length 27 - Handle 0030h] Physical Memory Array Handle 0028h Memory Error Info Handle [Not Provided] Total Width [Unknown] Data Width 64 bits Size [Not Populated] Form Factor 01h - Other Device Set [None] Device Locator DIMM4 Bank Locator BANK3 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer Manufacturer03 Serial Number Asset Tag Number Part Number ModulePartNumber03
Frederik.
Okay so I am currently unable to get memtest86+ due to certain circumstances, But I did use Windows Memory Diagnostic as a temporary check until i am able to get memtest86+. After running Windows Memory Diagnostic it showed that i had no problems (I am not sure how good Windows Memory Diagnostic is for checking RAM but it is all I have currently). I am still thinking of doing a check on my RAM with memtest86+, but just let me know if I still should do the check with it or if I should start checking somewhere else for the cause of my crashes
Alright... I did not say that i couldn't get it to work but that i am currently unable to actually get it. I am going to try and get it within the next few days and then run the test (hopefully my RAM will be good) but until then i am just going to have to do nothing.
Quote