Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Driver trouble, I think. And other things...It's time for help!


  • Please log in to reply
11 replies to this topic

#1 iggee002

iggee002

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 23 January 2014 - 01:19 PM

Hi everyone, 

 

I'm not sure where this should go since I have no clue where my issue actually is :/

 

So, I bought this PC in August off of Ebay. It may be the last time I do such a thing. I've been troubleshooting for weeks, and I'm about ready to smash this thing.  

 

Anyway, it worked fine up until about mid November when I started getting BSOD while playing World of Warcraft. I was extremely busy that month, and it didn't happen any other time, so I just stopped playing until I had time to figure out what was going on. 

 

At the end of December, it got to the point where it was BSOD every time I opened a program. Symptoms changed over and over. One day Seatools for DOS and Chkdsk tests were failing. The next, those tests were passing with no issues found, and it looked like the boot sector was corrupt. I found a solution somewhere on here to fix that through cmd, which worked for about a day. Then sfc /scannow caused the HD to start beeping at me. Seatools found no problems, and neither did Chkdsk after replacing the SATA cables going to my HD. Then I started getting a weird Avast error. When I tried to uninstall, the program was showing in my programs folder, but nothing was inside...like the files had just been deleted without a proper install.

 

At this point, I think I have a rootkit or something equally nasty since all AV scans were coming clean. The only problem is that the standalone antiviruses (I tried Bitdefender and the one from Microsoft) would not complete a scan. Bitdefender wouldn't run past the dragon screen, and the Microsoft tool went the whole way  through and then errored out at the very end. I know it wasn't my CD rom because Ubuntu live works fine, and I was able to recover my files that way. After an Avast scan using the Ubuntu Live CD, it came up positive for the WIN32: CBCrypt trojan. At this point, I just wiped out the HD and reinstalled Windows. 

 

So...this is where I am at now. My clean install worked for about two days before I got a BSOD yesterday. I guessed it was due to an update, so I rolled back using system restore, and again, could not boot into the OS after the restore said it completed successfully. Startup repair wouldn't fix it. None of my cmd scans would fix it. System restore was erroring out. The INSTALLATION media from Cyberpower says that it's not compatible with the version of Windows I am running (and it's the disk I used to do the clean install) After a few hours of banging my head against the wall, I found that the mode my HDD is using changed in BIOS... I changed that back to IDE (I think that's what it's called) and the puter booted right up, with the restore in tact. 

 

After I booted, I ran sfc /scannow. It said there were some errors that it couldn't repair. I have the log from that, but it's too big to attach. 

 

Other than that, the computer worked great for about another 24 hours. Today I got another BSOD...with a flash game, no less. SO I try to install .NET 4 so I can install Windows Debug tools to try and read the dump file (can't seem to attach that either), and I am told that my version of Windows is not genuine...

 

DOH..I forgot to go back and activate through all of this. Only now I cannot get the activation wizard to run. The option isn't even there to do so...I did find the file, and even got to the part where I can enter the key...only to get an error telling me it can't finish the activation.

 

Something is definitely wrong here, and I am out of ideas. I am REALLY hoping someone here can help me. 

 

Thanks for reading this book, lol....here are my specs:

 

 

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name GRAPHICS-PC
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
Processor Intel® Core™ i7-2600K CPU @ 3.40GHz, 3400 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 0703, 10/21/2011
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Graphics-PC\Cherie
Time Zone Eastern Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 6.03 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 14.0 GB
Page File Space 7.98 GB
Page File C:\pagefile.sys
 
As you can see some of the info isn't even showing correctly in my System Information Window. 
 
Thanks in advance for your help :)

Edited by iggee002, 23 January 2014 - 01:20 PM.


BC AdBot (Login to Remove)

 


m

#2 iggee002

iggee002
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 23 January 2014 - 02:09 PM

Wow. I just restarted, and now Windows is activated. My desktop picture is gone though. 

 

:smash: WHY is my computer acting so nutty???!! It's like there are gremlins in it or something  :hysterical: 



#3 KingdomSeeker

KingdomSeeker

  • Members
  • 458 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 AM

Posted 23 January 2014 - 03:56 PM

Welcome to BC iggee002, Let me know what you got so I don't get one too lol. I do appreciate your sense of humor. I know how frustrating it can be. So we can see what error messages you are getting and how your hardware is working I'd like you to do the following.

 

Please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 , taking care to post the link of the snapshot in your next post.
 
 
Please download MiniToolBox  , save it to your desktop and run it.
 
Checkmark the following checkboxes:
  List last 10 Event Viewer log
  List Installed Programs
  List Users, Partitions and Memory size.
 
Click Go and paste the content into your next post.
 

Download BlueScreenView:

http://www.nirsoft.net/utils/blue_screen_view.html

unzip downloaded file and double click on BlueScreenView.exe to run the program.

when scanning is done, go to EDIT - Select All

Go to FILE - SAVE Selected Items, and save the report as BSOD.txt

Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply



#4 iggee002

iggee002
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 23 January 2014 - 08:46 PM

Hi KindomSeeker, and thanks so much for the response! You kind of have to have a sense of humor with these things...many times it's laugh or cry...and you can't see what to do next through tears  :crazy:

 

The PC is a CyberPowerPC Gamer Xtreme Desktop. AKA: The Debbil. I nick named her "The Beast" because she is so much more powerful than the laptop I have been babying for the last 7 years. She must not have liked it very much *shrugs*

 

Here's the info you asked for.

 

Speccy:

 

http://speccy.piriform.com/results/BZu73dHNPYBRETBZUDWGZXf

 

Mini Tool Box:

 

 

MiniToolBox by Farbar  Version: 23-01-2014
Ran by Cherie (administrator) on 23-01-2014 at 20:38:01
Running from "C:\Users\Cherie\Downloads"
Microsoft Windows 7 Home Premium  Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************
 
========================= Event log errors: ===============================
 
Application errors:
==================
Error: (01/23/2014 01:38:23 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003
 
Error: (01/23/2014 00:20:17 PM) (Source: Software Protection Platform Service) (User: )
Description: Installation of the Proof of Purchase failed. 0x80070005
Partial Pkey=2V8WF
ACID=?
Detailed Error[?]
 
Error: (01/23/2014 00:14:17 PM) (Source: Software Protection Platform Service) (User: )
Description: Installation of the Proof of Purchase failed. 0x80070005
Partial Pkey=2V8WF
ACID=?
Detailed Error[?]
 
Error: (01/23/2014 00:09:32 PM) (Source: Software Protection Platform Service) (User: )
Description: Installation of the Proof of Purchase failed. 0x80070005
Partial Pkey=2V8WF
ACID=?
Detailed Error[?]
 
Error: (01/23/2014 00:09:11 PM) (Source: Software Protection Platform Service) (User: )
Description: Installation of the Proof of Purchase failed. 0x80070005
Partial Pkey=2V8WF
ACID=?
Detailed Error[?]
 
Error: (01/23/2014 11:52:26 AM) (Source: Software Protection Platform Service) (User: )
Description: Update Windows license and product key tokens failed with 0x80070005.
 
Error: (01/23/2014 11:49:41 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003
 
Error: (01/23/2014 11:32:19 AM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003
 
Error: (01/22/2014 08:18:18 PM) (Source: Application Hang) (User: )
Description: The program setup.exe version 6.1.7601.17514 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 
Process ID: 350
 
Start Time: 01cf17d8cbd1c304
 
Termination Time: 15
 
Application Path: C:\$WINDOWS.~BT\Sources\setup.exe
 
Report Id: 38035260-83cc-11e3-943c-00190e0ee340
 
Error: (01/22/2014 08:14:44 PM) (Source: WinMgmt) (User: )
Description: //./root/CIMV2SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 990x80041003
 
 
System errors:
=============
Error: (01/23/2014 02:06:16 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:06:12 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:06:08 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:06:04 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:05:59 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:05:55 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:05:51 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:05:47 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:05:43 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
Error: (01/23/2014 02:05:38 PM) (Source: cdrom) (User: )
Description: The device, \Device\CdRom0, has a bad block.
 
 
Microsoft Office Sessions:
=========================
 
=========================== Installed Programs ============================
 
Adobe Acrobat X Pro - English, Français, Deutsch (Version: 10.0.0)
Adobe AIR (Version: 2.5.1.17730)
Adobe Community Help (Version: 3.4.980)
Adobe Content Viewer (Version: 1.4.0)
Adobe Creative Suite 5.5 Design Premium (Version: 5.5)
Adobe Flash Player 11 ActiveX (Version: 11.9.900.170)
Adobe Flash Player 12 Plugin (Version: 12.0.0.43)
Adobe Widget Browser (Version: 2.0 Build 230)
Adobe Widget Browser (Version: 2.0.230)
Asmedia ASM104x USB 3.0 Host Controller Driver (Version: 1.12.5.0)
avast! Free Antivirus (Version: 9.0.2011)
CCleaner (Version: 4.07)
Google Chrome (Version: 11.0.696.77)
Google Update Helper (Version: 1.3.21.57)
Intel® Management Engine Components (Version: 7.0.0.1144)
Java 7 Update 51 (Version: 7.0.510)
Java Auto Updater (Version: 2.1.9.8)
Junk Mail filter update (Version: 14.0.8117.416)
Malwarebytes Anti-Malware version 1.75.0.1300 (Version: 1.75.0.1300)
Microsoft .NET Framework 4 Client Profile (Version: 4.0.30319)
Microsoft .NET Framework 4 Extended (Version: 4.0.30319)
Microsoft Application Error Reporting (Version: 12.0.6015.5000)
Microsoft Choice Guard (Version: 2.0.48.0)
Microsoft Office 2010 (Version: 14.0.4763.1000)
Microsoft Office Access MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Access Setup Metadata MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Excel MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Groove MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Groove Setup Metadata MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office InfoPath MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Office 64-bit Components 2007 (Version: 12.0.4518.1014)
Microsoft Office OneNote MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Outlook MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office PowerPoint MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Proof (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Proof (French) 2007 (Version: 12.0.4518.1014)
Microsoft Office Proof (Spanish) 2007 (Version: 12.0.4518.1014)
Microsoft Office Proofing (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Publisher MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Shared 64-bit MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Shared 64-bit Setup Metadata MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Shared MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Shared Setup Metadata MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Office Ultimate 2007 (Version: 12.0.4518.1014)
Microsoft Office Word MUI (English) 2007 (Version: 12.0.4518.1014)
Microsoft Search Enhancement Pack (Version: 1.2.123.0)
Microsoft Silverlight (Version: 3.0.40624.0)
Microsoft SQL Server 2005 Compact Edition [ENU] (Version: 3.1.0000)
Microsoft Sync Framework Runtime Native v1.0 (x86) (Version: 1.0.1215.0)
Microsoft Sync Framework Services Native v1.0 (x86) (Version: 1.0.1215.0)
Microsoft_VC80_ATL_x86 (Version: 8.0.50727.4053)
Microsoft_VC80_ATL_x86_x64 (Version: 8.0.50727.4053)
Microsoft_VC80_CRT_x86 (Version: 8.0.50727.4053)
Microsoft_VC80_CRT_x86_x64 (Version: 8.0.50727.4053)
Microsoft_VC80_MFC_x86 (Version: 8.0.50727.4053)
Microsoft_VC80_MFC_x86_x64 (Version: 8.0.50727.4053)
Microsoft_VC80_MFCLOC_x86 (Version: 8.0.50727.4053)
Microsoft_VC80_MFCLOC_x86_x64 (Version: 80.50727.4053)
Microsoft_VC90_ATL_x86 (Version: 1.00.0000)
Microsoft_VC90_ATL_x86_x64 (Version: 1.00.0000)
Microsoft_VC90_CRT_x86 (Version: 1.00.0000)
Microsoft_VC90_CRT_x86_x64 (Version: 1.00.0000)
Microsoft_VC90_MFC_x86 (Version: 1.00.0000)
Microsoft_VC90_MFC_x86_x64 (Version: 1.00.0000)
Microsoft_VC90_MFCLOC_x86 (Version: 1.00.0000)
Microsoft_VC90_MFCLOC_x86_x64 (Version: 1.00.0000)
MSVCRT (Version: 14.0.1468.721)
NVIDIA 3D Vision Driver 285.66 (Version: 285.66)
NVIDIA Control Panel 285.66 (Version: 285.66)
NVIDIA Graphics Driver 285.66 (Version: 285.66)
NVIDIA Install Application (Version: 2.1002.46.235)
NVIDIA Stereoscopic 3D Driver (Version: 7.17.12.8566)
PDF Settings CS5 (Version: 10.0)
Realtek Ethernet Controller Driver (Version: 7.45.516.2011)
Realtek High Definition Audio Driver (Version: 6.0.1.6402)
Speccy (Version: 1.24)
Windows Live Call (Version: 14.0.8117.0416)
Windows Live Communications Platform (Version: 14.0.8117.416)
Windows Live Essentials (Version: 14.0.8117.0416)
Windows Live Essentials (Version: 14.0.8117.416)
Windows Live Mail (Version: 14.0.8117.0416)
Windows Live Messenger (Version: 14.0.8117.0416)
Windows Live Movie Maker (Version: 14.0.8117.0416)
Windows Live Photo Gallery (Version: 14.0.8117.416)
Windows Live Sign-in Assistant (Version: 5.000.818.5)
Windows Live Sync (Version: 14.0.8117.416)
Windows Live Toolbar (Version: 14.0.8117.416)
Windows Live Upload Tool (Version: 14.0.8014.1029)
Windows Live Writer (Version: 14.0.8117.0416)
World of Warcraft
 
========================= Memory info: ===================================
 
Percentage of memory in use: 22%
Total physical RAM: 8173.21 MB
Available physical RAM: 6303.12 MB
Total Pagefile: 16344.6 MB
Available Pagefile: 14301.15 MB
Total Virtual: 4095.88 MB
Available Virtual: 3981.15 MB
 
========================= Partitions: =====================================
 
1 Drive c: () (Fixed) (Total:1862.92 GB) (Free:1782.26 GB) NTFS
2 Drive d: (MB Support CD) (CDROM) (Total:3.22 GB) (Free:0 GB) CDFS
8 Drive j: (TOSHIBA EXT) (Fixed) (Total:465.66 GB) (Free:421.66 GB) NTFS
 
========================= Users: ========================================
 
User accounts for \\GRAPHICS-PC
 
Administrator            Cherie                   Guest                    
 
 
**** End of log ****
 
BlueScreenView:
 
==================================================
Dump File         : 012314-38079-01.dmp
Crash Time        : 1/23/2014 11:25:40 AM
Bug Check String  : CRITICAL_OBJECT_TERMINATION
Bug Check Code    : 0x000000f4
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`09545b30
Parameter 3       : fffffa80`09545e10
Parameter 4       : fffff800`031977b0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18247 (win7sp1_gdr.130828-1532)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012314-38079-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 286,280
Dump File Time    : 1/23/2014 11:30:47 AM
==================================================
 
I need to update my Flash and SIlverlight since the rollback....possibly some other things too. I will refrain though until I hear back.  

Edited by iggee002, 23 January 2014 - 08:48 PM.


#5 KingdomSeeker

KingdomSeeker

  • Members
  • 458 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:41 AM

Posted 23 January 2014 - 10:04 PM

I see a lot of this error "Description: Installation of the Proof of Purchase failed. 0x80070005." Did it come with an operating system or did you have to add your own? If you added your own what method dis you use?  I've been looking on Ebay for a newer computer myself and I know that some don't come with an OS.


Edited by KingdomSeeker, 23 January 2014 - 10:06 PM.


#6 iggee002

iggee002
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 23 January 2014 - 11:10 PM

This came with everything installed, and the disc is from CyberPower with Win 7 Home, along with the discs fro the video card and the mobo was included.

 

All of those errors I am assuming were from today when I was trying repeatedly to open Slui. Every angle I took to run that application gave me that error (0x80070005). Oddly enough, the only thing that actually opened the program was to type Activation in the search field under Start. I was able to enter the product key from the sticker on the side of my tower, but was told that the activation could not complete, and that code was given again. That was when I decided to post here. I restarted just after posting, and the computer booted with an activated Windows. 

 

It's just all so odd. None of it is making sense! I currently have the Windows Activation open, and it says the activation was successful. 

 

What worries me is all the processes that are listed, but are not started. 

 

I cannot remember the cmd that I ran to get this, I could look it up if you really need to know...but I was able to filter out info from the CBS file that tells me what sfc was able to fix, and what it did not fix. It's a bit lengthy, but I am going to post it below:

 

 

2014-01-22 20:23:09, Info                  CSI    00000320 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:18, Info                  CSI    00000322 [SR] Verify complete

2014-01-22 20:23:18, Info                  CSI    00000323 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:18, Info                  CSI    00000324 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:20, Info                  CSI    00000326 [SR] Verify complete

2014-01-22 20:23:20, Info                  CSI    00000327 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:20, Info                  CSI    00000328 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:22, Info                  CSI    0000032a [SR] Verify complete

2014-01-22 20:23:22, Info                  CSI    0000032b [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:22, Info                  CSI    0000032c [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:26, Info                  CSI    0000032f [SR] Verify complete

2014-01-22 20:23:26, Info                  CSI    00000330 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:26, Info                  CSI    00000331 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:27, Info                  CSI    00000333 [SR] Verify complete

2014-01-22 20:23:27, Info                  CSI    00000334 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:27, Info                  CSI    00000335 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:28, Info                  CSI    00000337 [SR] Verify complete

2014-01-22 20:23:28, Info                  CSI    00000338 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:28, Info                  CSI    00000339 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:31, Info                  CSI    0000033c [SR] Verify complete

2014-01-22 20:23:32, Info                  CSI    0000033d [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:32, Info                  CSI    0000033e [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:36, Info                  CSI    00000342 [SR] Verify complete

2014-01-22 20:23:36, Info                  CSI    00000343 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:36, Info                  CSI    00000344 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:38, Info                  CSI    00000349 [SR] Verify complete

2014-01-22 20:23:38, Info                  CSI    0000034a [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:38, Info                  CSI    0000034b [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:42, Info                  CSI    00000353 [SR] Verify complete

2014-01-22 20:23:42, Info                  CSI    00000354 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:42, Info                  CSI    00000355 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:46, Info                  CSI    0000035c [SR] Verify complete

2014-01-22 20:23:46, Info                  CSI    0000035d [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:46, Info                  CSI    0000035e [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:48, Info                  CSI    00000363 [SR] Verify complete

2014-01-22 20:23:48, Info                  CSI    00000364 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:48, Info                  CSI    00000365 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:49, Info                  CSI    00000369 [SR] Verify complete

2014-01-22 20:23:49, Info                  CSI    0000036a [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:49, Info                  CSI    0000036b [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:51, Info                  CSI    0000036d [SR] Verify complete

2014-01-22 20:23:51, Info                  CSI    0000036e [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:51, Info                  CSI    0000036f [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:54, Info                  CSI    00000394 [SR] Verify complete

2014-01-22 20:23:54, Info                  CSI    00000395 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:54, Info                  CSI    00000396 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:55, Info                  CSI    00000398 [SR] Verify complete

2014-01-22 20:23:55, Info                  CSI    00000399 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:55, Info                  CSI    0000039a [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:57, Info                  CSI    0000039c [SR] Verify complete

2014-01-22 20:23:57, Info                  CSI    0000039d [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:57, Info                  CSI    0000039e [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:23:59, Info                  CSI    000003a0 [SR] Verify complete

2014-01-22 20:23:59, Info                  CSI    000003a1 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:23:59, Info                  CSI    000003a2 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:00, Info                  CSI    000003af [SR] Verify complete

2014-01-22 20:24:00, Info                  CSI    000003b0 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:00, Info                  CSI    000003b1 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:02, Info                  CSI    000003b4 [SR] Verify complete

2014-01-22 20:24:02, Info                  CSI    000003b5 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:02, Info                  CSI    000003b6 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:04, Info                  CSI    000003c0 [SR] Verify complete

2014-01-22 20:24:04, Info                  CSI    000003c1 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:04, Info                  CSI    000003c2 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:06, Info                  CSI    000003c8 [SR] Verify complete

2014-01-22 20:24:06, Info                  CSI    000003c9 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:06, Info                  CSI    000003ca [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:07, Info                  CSI    000003cc [SR] Verify complete

2014-01-22 20:24:07, Info                  CSI    000003cd [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:07, Info                  CSI    000003ce [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:11, Info                  CSI    000003d1 [SR] Verify complete

2014-01-22 20:24:11, Info                  CSI    000003d2 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:11, Info                  CSI    000003d3 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:11, Info                  CSI    000003d5 [SR] Verify complete

2014-01-22 20:24:11, Info                  CSI    000003d6 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:11, Info                  CSI    000003d7 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:13, Info                  CSI    000003d9 [SR] Verify complete

2014-01-22 20:24:13, Info                  CSI    000003da [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:13, Info                  CSI    000003db [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:17, Info                  CSI    000003dd [SR] Verify complete

2014-01-22 20:24:17, Info                  CSI    000003de [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:17, Info                  CSI    000003df [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:18, Info                  CSI    000003e1 [SR] Verify complete

2014-01-22 20:24:18, Info                  CSI    000003e2 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:18, Info                  CSI    000003e3 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:22, Info                  CSI    000003fd [SR] Verify complete

2014-01-22 20:24:22, Info                  CSI    000003fe [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:22, Info                  CSI    000003ff [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:29, Info                  CSI    00000401 [SR] Verify complete

2014-01-22 20:24:29, Info                  CSI    00000402 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:29, Info                  CSI    00000403 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:30, Info                  CSI    00000405 [SR] Verify complete

2014-01-22 20:24:30, Info                  CSI    00000406 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:30, Info                  CSI    00000407 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:32, Info                  CSI    00000409 [SR] Verify complete

2014-01-22 20:24:32, Info                  CSI    0000040a [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:32, Info                  CSI    0000040b [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:33, Info                  CSI    0000040f [SR] Verify complete

2014-01-22 20:24:33, Info                  CSI    00000410 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:33, Info                  CSI    00000411 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:34, Info                  CSI    00000413 [SR] Verify complete

2014-01-22 20:24:34, Info                  CSI    00000414 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:34, Info                  CSI    00000415 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:36, Info                  CSI    00000417 [SR] Verify complete

2014-01-22 20:24:36, Info                  CSI    00000418 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:36, Info                  CSI    00000419 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:37, Info                  CSI    0000041b [SR] Verify complete

2014-01-22 20:24:37, Info                  CSI    0000041c [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:37, Info                  CSI    0000041d [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:39, Info                  CSI    00000420 [SR] Verify complete

2014-01-22 20:24:39, Info                  CSI    00000421 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:39, Info                  CSI    00000422 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:40, Info                  CSI    00000424 [SR] Verify complete

2014-01-22 20:24:40, Info                  CSI    00000425 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:40, Info                  CSI    00000426 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:42, Info                  CSI    00000428 [SR] Verify complete

2014-01-22 20:24:42, Info                  CSI    00000429 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:42, Info                  CSI    0000042a [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:44, Info                  CSI    0000042c [SR] Verify complete

2014-01-22 20:24:44, Info                  CSI    0000042d [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:44, Info                  CSI    0000042e [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:45, Info                  CSI    00000431 [SR] Verify complete

2014-01-22 20:24:45, Info                  CSI    00000432 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:45, Info                  CSI    00000433 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:47, Info                  CSI    00000435 [SR] Verify complete

2014-01-22 20:24:47, Info                  CSI    00000436 [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:47, Info                  CSI    00000437 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:49, Info                  CSI    00000439 [SR] Verify complete

2014-01-22 20:24:49, Info                  CSI    0000043a [SR] Verifying 100 (0

x0000000000000064) components

2014-01-22 20:24:49, Info                  CSI    0000043b [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:51, Info                  CSI    0000043d [SR] Verify complete

2014-01-22 20:24:51, Info                  CSI    0000043e [SR] Verifying 61 (0x

000000000000003d) components

2014-01-22 20:24:51, Info                  CSI    0000043f [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:52, Info                  CSI    00000441 [SR] Verify complete

2014-01-22 20:24:52, Info                  CSI    00000442 [SR] Repairing 4 comp

onents

2014-01-22 20:24:52, Info                  CSI    00000443 [SR] Beginning Verify

 and Repair transaction

2014-01-22 20:24:52, Info                  CSI    00000445 [SR] Cannot repair me

mber file [l:16{8}]"1394.inf" of 1394.inf, Version = 6.1.7601.17514, pA = PROCES

SOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyT

oken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutr

al, PublicKey neutral in the store, hash mismatch

2014-01-22 20:24:52, Info                  CSI    00000447 [SR] Cannot repair me

mber file [l:18{9}]"IMTCV.IMD" of Microsoft-Windows-IME-Traditional-Chinese-Virt

ualLexicons, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Cu

lture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35

}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

 

2014-01-22 20:24:52, Info                  CSI    00000449 [SR] Cannot repair me

mber file [l:20{10}]"IMTCEN.CHM" of Microsoft-Windows-IME-Traditional-Chinese-Co

re, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neu

tral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type n

eutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-01-22 20:24:52, Info                  CSI    0000044b [SR] Cannot repair me

mber file [l:18{9}]"IMTCS.IMD" of Microsoft-Windows-IME-Traditional-Chinese-Bigr

amDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), C

ulture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e3

5}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatc

h

2014-01-22 20:24:52, Info                  CSI    0000044d [SR] Cannot repair me

mber file [l:18{9}]"IMTCV.IMD" of Microsoft-Windows-IME-Traditional-Chinese-Virt

ualLexicons, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Cu

lture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35

}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

 

2014-01-22 20:24:52, Info                  CSI    0000044e [SR] This component w

as referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364

e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2014-01-22 20:24:52, Info                  CSI    00000451 [SR] Could not reproj

ect corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:1

8{9}]"IMTCV.IMD"; source file in store is also corrupted

2014-01-22 20:24:52, Info                  CSI    00000453 [SR] Cannot repair me

mber file [l:20{10}]"IMTCEN.CHM" of Microsoft-Windows-IME-Traditional-Chinese-Co

re, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neu

tral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type n

eutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2014-01-22 20:24:52, Info                  CSI    00000454 [SR] This component w

as referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364

e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2014-01-22 20:24:52, Info                  CSI    00000457 [SR] Could not reproj

ect corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMETC10\HELP"\[l:20

{10}]"IMTCEN.CHM"; source file in store is also corrupted

2014-01-22 20:24:52, Info                  CSI    00000459 [SR] Cannot repair me

mber file [l:18{9}]"IMTCS.IMD" of Microsoft-Windows-IME-Traditional-Chinese-Bigr

amDictionary, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), C

ulture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e3

5}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatc

h

2014-01-22 20:24:52, Info                  CSI    0000045a [SR] This component w

as referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364

e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"

2014-01-22 20:24:52, Info                  CSI    0000045d [SR] Could not reproj

ect corrupted file [ml:520{260},l:64{32}]"\??\C:\Windows\IME\IMETC10\DICTS"\[l:1

8{9}]"IMTCS.IMD"; source file in store is also corrupted

2014-01-22 20:24:52, Info                  CSI    0000045f [SR] Cannot repair me

mber file [l:16{8}]"1394.inf" of 1394.inf, Version = 6.1.7601.17514, pA = PROCES

SOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyT

oken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutr

al, PublicKey neutral in the store, hash mismatch

2014-01-22 20:24:52, Info                  CSI    00000460 [SR] This component w

as referenced by [l:176{88}]"Microsoft-Windows-Common-Drivers-Package~31bf3856ad

364e35~amd64~~6.1.7601.17514.INF_1394"

2014-01-22 20:24:53, Info                  CSI    00000462 [SR] Repair complete

2014-01-22 20:24:53, Info                  CSI    00000463 [SR] Committing trans

action

2014-01-22 20:24:53, Info                  CSI    00000467 [SR] Verify and Repai

r Transaction completed. All files and registry keys listed in this transaction

 have been successfully repaired

 

C:\Windows\system32>


Edited by iggee002, 23 January 2014 - 11:11 PM.


#7 hamluis

hamluis

    Moderator


  • Moderator
  • 54,839 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:41 AM

Posted 24 January 2014 - 07:11 AM

One day Seatools for DOS and Chkdsk tests were failing. The next, those tests were passing with no issues found, and it looked like the boot sector was corrupt. I found a solution somewhere on here to fix that through cmd, which worked for about a day. Then sfc /scannow caused the HD to start beeping at me. Seatools found no problems, and neither did Chkdsk after replacing the SATA cables going to my HD. .

 

 At this point, I just wiped out the HD and reinstalled Windows. 

 

DOH..I forgot to go back and activate through all of this. Only now I cannot get the activation wizard to run.

 

Well...I see the possibility of hardware problems as being the start of any troubleshooting.  IMO, the stated instances of system beeping point to possible CMOS battery or component issues that need to be examined hands-on by a competent individual.  Random flopping around trying this, trying that...isn't likely to produce reliable results, IMO.

 

If you have a warranty on this system...I suggest that you use it.

 

If you have no warranty, I suggest that you take it to a qualified computer shop or knowledgeable individual and have it checked out for functionality.  Once the components are cleared re functionality, you would then have a valid base from which to troubleshoot any ensuing issues.

 

Louis



#8 iggee002

iggee002
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 24 January 2014 - 10:45 AM

Thank you for the response Hamluis. However, I like to think that my schooling, and experience, in IT qualifies me to troubleshoot my computer at least to some degree. I am not just randomly trying this, and trying that. I can understand how it can seem that way from my original post. It is difficult to summarize a month's worth of troubleshooting and ever changing symptoms into a single post. I am convinced that my issues before the wipe and re-install were mainly due to a virus that I did not catch before serious damage had been done to the OS.

 

The advice I am asking for is with this installation if Windows.   

 

As I stated, the symptoms keep changing. Random things that do not make sense, such as what just happened with the Windows Activation wizard. That is why I am asking for help. I believe this is software related, possibly the wrong combination of installed drivers, and I thought a fresh set of eyes might be useful. I can assure you, I am competent enough to replace hardware such as the CMOS battery if that is what is needed. I draw the line at the Motherboad, however. If that needs to be replaced, I will sell the thing. There is no warranty as I bought it used. 

 

The beeping issue was resolved by a replacement SATA cable from the motherboard to the Hard drive. I have seen no other evidence of hardware failure since then, and the scans using both Seatools for DOS and Chkdsk came back with no bad sectors found. As for the battery, I have thought of that...but dismissed it because the time and date are still correct from when the PC was shipped to me. Not only that, but I am getting no CMOS errors. I am sure replacing the battery couldn't hurt, but the only symptom I have seen of possible failure is that once in a while my wireless keyboard does not work when prompted to push any key to boot from CD after changing the boot device order to boot from CD. It's the only time it fails, however. That and the SATA configuration mysteriously changing from the IDE I had it set to back to the default ACHI mode after I had re-installed Windows. I changed that back almost three days ago, and it has not reset itself. 

 

Anyway, thanks for the reply. The CMOS is still a possibility, and something to keep in mind. 



#9 hamluis

hamluis

    Moderator


  • Moderator
  • 54,839 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:41 AM

Posted 24 January 2014 - 12:43 PM

Well...I can't assess your capabilities but I can read what you submitted.

 

I don't have the system in front of me....you do...theoretcially, that gives you at least two advantages:

 

  a.  You know exactly what you have done and whether it was effective or ineffective.

 

  b.  The members of this website have neither the system, nor knowledge other than what you communicate about the system in your posts.

 

I've reflected the approach I would take...it's not the only one available.

 

I will say this...a clean install would definitely eliminate suspected O/S and/or drivers/programs, etc. from the equation.  Any problems developing after such clearly fall into another category, IMO.

 

Louis



#10 iggee002

iggee002
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 25 January 2014 - 12:39 PM

I will say this...a clean install would definitely eliminate suspected O/S and/or drivers/programs, etc. from the equation.  Any problems developing after such clearly fall into another category, IMO.

 

 

Well, you're right about this. I have been experiencing a slow hard drive failure. I suspected, but I'm stubborn and didn't want to admit that it was going bad so soon after buying this thing. I can't deny it now though without being stupid rather than stubborn...it has started spinning really loudly, and the computer freezes and is running really, really slowly. I have shut it off to prevent further damage, and am now on my laptop to post the update. 

 

I am still uncertain why Seatools would pass the drive tests after the cable change if it were going bad. I used the Seatools disc to wipe the drive, and there was no indication of a problem then either. *sigh*

 

Time to buy a new one and go from there. Thanks for the insight, and I apologize for being unclear in my OP or wasting anyone's time with a hardware issue due to me being too stubborn to admit that the computer I just bought was just faulty. I didn't mean any offense.  

 

--Cherie


Edited by iggee002, 25 January 2014 - 12:45 PM.


#11 iggee002

iggee002
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:04:41 AM

Posted 26 January 2014 - 12:02 AM

Update. With the exception of the few errors sfc /scannow is still saying it is finding, but not able to fix, my system seems to be running like the new install that it is (Though I would like to know what those mean...but they don't seem to be affecting anything right now. They will probably show their teeth when I'm in the middle of a game :/ )

 

Anyway, After posting this, and reviewing my budget (I cannot afford to buy PC parts unless I absolutely have to), I decided to run Seatools again. Why not? I have my Data saved, and I'm about to trash the drive, so I might as well, right? I ran several different tests, including the SMART test on this Hard drive. All passed. Hmmm...then what is that noise?? I unplugged the fan next to the Hard drive, and the helicopter like noise that was coming from my system stopped. I had previously done this, only I unplugged the HDD and not the fan. For some reason the fan must not have started when I turned the system back on that time, leading me to believe the noise did not happen with the HDD unplugged. Of course it didn't, lol...

 

Gleefully, with the HDD ruled out, I went back to the drawing board. Here is what I found: 

 

My SATA usually runs in AHCI mode. When I first ran Seatools for DOS, it had to be run in IDE mode in order to work. I forgot to change the setting back in BIOS before installing Windows. Well, windows does not enable drivers that are not used, and I could not change the SATA mode back after the install without the BSOD. Not only that, but I found that if your PC is in IDE mode, it can switch itself to PIO mode if there are multiple errors concerning IDE. This could be why my system was crawling. So, I set out to fix the AHCI issue I knew I was going to have to deal with eventually, and see if things speed back up. I was able to enable the AHCI driver manually in the registry. Once I had done this, I was able to boot into Windows in AHCI mode again. Yay. 

 

Once in Windows in the faster AHCI mode, I found that I was getting BSOD after a few minutes....just as I had been at the very beginning of my troubles at the end of December. However, I AM able to boot into Safe mode. I did so and used the MUCH easier to use Blue Screen tool I was instructed to download here. There I saw that it was, in fact, a driver causing the BSODs. I configured the Driver Verifier tool located within Windows, and set it to work. After disabling the tool, I checked out the resulting BSOD, and discovered that a driver from AVAST 2014 was at the root of the trouble. 

 

So, I completely uninstalled Avast and rebooted. Voila. Problems seem to be solved. 

 

While researching what Verifier was telling me, I found several forums where the Avast update is causing all sorts of problems for people. When I think back, this may have been my issue all along....I had just updated my Avast not too long ago. 

 

So, bottom line...it was a whole combination of errors and misconfigurations, and me innocently thinking that an antivirus I have used for years would not cause such horrible problems with my PC. Maybe I just needed some moral support and a place to vent my frustrations in a place that is able to "hear" me without getting glazed over looks in their eyes because I lost them at "BSOD Stop Error." Getting it off my chest allowed me to think this puzzle through better....so thanks again!

 

I'm sure I will be back :)



#12 hamluis

hamluis

    Moderator


  • Moderator
  • 54,839 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:41 AM

Posted 26 January 2014 - 10:26 AM

Nice work :).

 

Generally...fans are more likely to be the source of noise in a system...a visual inspection of the system (with cover removed) can usually allow pinpointing of the noise source.

 

If you have any problems in the future...feel free to post such here seeking suggestions.

 

Happy computing :).

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users