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

Cannot Activate XP Home after Repair Install


  • Please log in to reply
13 replies to this topic

#1 hibachi

hibachi

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:10:59 PM

Posted 08 March 2011 - 12:05 AM

Bleepingcomputer, dearest of all my friends. You've helped me out of several jams before, and I'd like to think we can continue this success streak. Here is my woe:
Posted Image


The story: After XP started to have some errors about a cov.exe crashing a few times, and some other funny things, I decided to reboot, only to be greeted with a blue screen and a 0x0000007b error (I forget, but I couldn't boot). Chkdsk said it was fine, so I assumed I had a boot sector virus. I went ahead and backed up my important files, but I made a few goofs:

I was running SP3, and I only had an SP2 disc available to me, from a different manufacturer, though I doubt that matters much. My first mistake was starting a repair install before fixing my MBR. I was just getting a similar blue screen. After starting the repair install twice, I then went to the recovery console and ran FIXMBR, which said it did its thing, and it showed because then XP was able to finish the repair install. Once it finished, it asked for the activation window, shown above, but with slight different icons. While I researched what to do, I ran a boot-time scan for the virus.

My first refuge was here: http://support.microsoft.com/kb/314935

I followed all the steps listed there, aside from 4, reinstalling the Oobe.ini, because for some reason it wouldn't allow me to get the file it needed off my recovery disk. This did nothing.

My next attempt was to install this hotfix http://support.microsoft.com/default.aspx/kb/946501 and then IE8. Some where between doing that and the previous steps, it changed how the two corner images looked slightly, but that was about it. I also extended the activation period by 30 days via Start > Run > rundll32.exe syssetup,SetupOobeBnk.

Further research showed me that it was probably the repair install of SP2 over SP3 that did it, and I figured upgrading back to SP3 would do the trick. I got my hands on this stand alone update http://www.microsoft.com/downloads/details.aspx?FamilyID=5b33b5a8-5e76-401f-be08-1e1555d4f3d4&displaylang=en since the machine cannot connect to my network since it was wireless, and no longer sees the USB wireless connector, though when it did when I plugged it into a different port, but I decided not to go through the trouble of getting the drivers for it at the time.

So I ran the stand alone updated, and though it did upgrade to SP3, it invalidated the 30 days I put on the activation, which I just reapplied anyway, but that was about it. I still have what's shown above.

Any ideas?

Edited by hamluis, 09 March 2011 - 07:03 AM.
Moved from XP to Am I Infected.


BC AdBot (Login to Remove)

 


#2 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:01:59 PM

Posted 08 March 2011 - 12:52 AM

Hi -
Can you still access the "sick" computer even in Safe Mode - It so please follow these directions -
If you are posting from another computer please let us know -

Please download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thank You -

Edited by noknojon, 08 March 2011 - 12:53 AM.


#3 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:59 PM

Posted 08 March 2011 - 07:52 AM

I find your post very hard to follow, but I'd like to comment on a couple of things that I did understand:

1) Boot sector viruses are VERY rare. I have no idea how you came to the conclusion that you had one, but I'm guessing that you did not.
2) It is perfectly acceptable to use a different version of XP to go to the Recovery Console and run fixmbr, but not to do an actual repair installation.
3) Running "fixmbr" would not clear out a boot sector virus even if you had one. Only an anti virus utility can do that.

After that, I'm pretty much lost with what you did :blink:

#4 hibachi

hibachi
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:10:59 PM

Posted 08 March 2011 - 09:49 AM

Hi -
Can you still access the "sick" computer even in Safe Mode - It so please follow these directions -
If you are posting from another computer please let us know -

Yes, I can. As far as that issue is, the 'sick' computer is almost nearly fully operational aside from a speed issue and the inability to connect to the internet at this time, so I am responding with another computer. As for the BSOD, it has stopped since I ran a repair install, but here is the BSOD.txt anyway:

==================================================
Dump File : Mini010211-01.dmp
Crash Time : 1/2/2011 2:16:05 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe55fe028
Parameter 2 : 0x00000000
Parameter 3 : 0xbf88cf96
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+8cf96
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010211-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini122010-02.dmp
Crash Time : 12/20/2010 5:49:18 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xe0000001
Parameter 2 : 0xb8398925
Parameter 3 : 0xb2742884
Parameter 4 : 0x00000000
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+925
File Description : Watchdog Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini122010-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini122010-01.dmp
Crash Time : 12/20/2010 11:18:11 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0xb428bf95
Parameter 3 : 0xb8503bf8
Parameter 4 : 0xb85038f4
Caused By Driver : Ma1FL.sys
Caused By Address : Ma1FL.sys+f95
File Description : JC-AS01 Filter Driver
Product Name :
Company : TigerGame.,Ltd
File Version : 1, 0, 0, 1
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini122010-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini110610-01.dmp
Crash Time : 11/6/2010 5:02:54 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0x8af40000
Parameter 2 : 0x00000000
Parameter 3 : 0x8052e549
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57549
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini110610-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini101910-01.dmp
Crash Time : 10/19/2010 6:31:03 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0x9feb7000
Parameter 2 : 0x00000000
Parameter 3 : 0x8052e549
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+57549
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini101910-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini092410-01.dmp
Crash Time : 9/24/2010 7:57:49 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd2af8cb
Parameter 3 : 0xaeccb93c
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+29d8cb
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini092410-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini092310-01.dmp
Crash Time : 9/23/2010 8:47:43 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd2af8cb
Parameter 3 : 0xaee1493c
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+29d8cb
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini092310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini090110-01.dmp
Crash Time : 9/1/2010 4:34:38 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf9539cc
Parameter 3 : 0xb1af1c00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1539cc
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini072510-01.dmp
Crash Time : 7/24/2010 11:48:58 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe335a024
Parameter 2 : 0x00000000
Parameter 3 : 0xbf83cfe8
Parameter 4 : 0x00000001
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+3cfe8
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini072510-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini052710-01.dmp
Crash Time : 5/27/2010 1:04:18 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf953492
Parameter 3 : 0xb243ec00
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+153492
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini050710-01.dmp
Crash Time : 5/7/2010 8:06:27 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c9079
Parameter 3 : 0xb1a95a48
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7079
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini050710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini022010-01.dmp
Crash Time : 2/20/2010 7:53:07 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xba50e000
Parameter 2 : 0x00000001
Parameter 3 : 0x8053a8e3
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+36ee6
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022010-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini011810-01.dmp
Crash Time : 1/18/2010 7:05:29 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x10000050
Parameter 1 : 0xe7c28848
Parameter 2 : 0x00000000
Parameter 3 : 0xbd0c9072
Parameter 4 : 0x00000001
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7072
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011810-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini011210-01.dmp
Crash Time : 1/12/2010 5:25:59 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c9079
Parameter 3 : 0xb2bc1aa8
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7079
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011210-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini011110-01.dmp
Crash Time : 1/11/2010 11:23:15 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c9079
Parameter 3 : 0xb2814aa8
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7079
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini011010-01.dmp
Crash Time : 1/10/2010 10:19:34 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c9079
Parameter 3 : 0xb8187ae0
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7079
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011010-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini010710-01.dmp
Crash Time : 1/7/2010 5:43:16 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c9079
Parameter 3 : 0xb0d8e59c
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7079
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini010410-01.dmp
Crash Time : 1/4/2010 10:53:13 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c9079
Parameter 3 : 0xb19baaa8
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b7079
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010410-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini123109-01.dmp
Crash Time : 12/31/2009 11:23:30 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbd0c90f2
Parameter 3 : 0xb19cd8a0
Parameter 4 : 0x00000000
Caused By Driver : nv4_disp.dll
Caused By Address : nv4_disp.dll+b70f2
File Description : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Product Name : NVIDIA Compatible Windows 2000 Display driver, Version 158.28
Company : NVIDIA Corporation
File Version : 6.14.11.5828
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini123109-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini070409-01.dmp
Crash Time : 7/4/2009 5:44:27 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x00000104
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xb629b715
Caused By Driver : RtkHDAud.sys
Caused By Address : RtkHDAud.sys+7b715
File Description : Realtek® High Definition Audio Function Driver
Product Name : Realtek® High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
Company : Realtek Semiconductor Corp.
File Version : 5.10.0.5408 built by: WinDDK
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini070409-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini052509-03.dmp
Crash Time : 5/25/2009 6:14:23 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e84bc
Parameter 3 : 0xb346c868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e84bc
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052509-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini052509-02.dmp
Crash Time : 5/25/2009 11:56:00 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e84bc
Parameter 3 : 0xb503c868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e84bc
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052509-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini052509-01.dmp
Crash Time : 5/25/2009 11:29:33 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e84bc
Parameter 3 : 0xb3605868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e84bc
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052509-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini020909-01.dmp
Crash Time : 2/9/2009 5:41:36 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x0a08002a
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804f45aa
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+1790d
File Description : Microsoft Filesystem Filter Manager
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini020909-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini121608-01.dmp
Crash Time : 12/16/2008 6:56:20 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8edec2
Parameter 3 : 0xb576a868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+edec2
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121608-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini112108-01.dmp
Crash Time : 11/21/2008 7:21:00 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8edec2
Parameter 3 : 0xb3f86868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+edec2
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112108-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini100108-03.dmp
Crash Time : 10/1/2008 12:44:51 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e56
Parameter 3 : 0xb3ff7868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e56
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini100108-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini100108-02.dmp
Crash Time : 10/1/2008 11:27:59 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e56
Parameter 3 : 0xb4f1c868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e56
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini100108-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini100108-01.dmp
Crash Time : 10/1/2008 10:57:06 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e56
Parameter 3 : 0xb3384868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e56
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini100108-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini090508-01.dmp
Crash Time : 9/5/2008 5:49:07 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e56
Parameter 3 : 0xb3cdd868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e56
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini090508-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini082608-01.dmp
Crash Time : 8/26/2008 8:09:44 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e91
Parameter 3 : 0xb1c810f8
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e91
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082608-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini082408-01.dmp
Crash Time : 8/24/2008 6:24:38 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e91
Parameter 3 : 0xb3b40868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e91
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082408-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini082208-01.dmp
Crash Time : 8/22/2008 5:45:26 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e91
Parameter 3 : 0xb3818868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e91
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini082208-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini081008-01.dmp
Crash Time : 8/10/2008 12:37:46 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xbf8e5e91
Parameter 3 : 0xb3e50868
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+e5e91
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini081008-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================


find your post very hard to follow, but I'd like to comment on a couple of things that I did understand:

1) Boot sector viruses are VERY rare. I have no idea how you came to the conclusion that you had one, but I'm guessing that you did not.
2) It is perfectly acceptable to use a different version of XP to go to the Recovery Console and run fixmbr, but not to do an actual repair installation.
3) Running "fixmbr" would not clear out a boot sector virus even if you had one. Only an anti virus utility can do that.

After that, I'm pretty much lost with what you did

1)I guessed I had one when I did something as simple as try to reboot, and then get no where past the Windows loading screen, after having some processes acting up before hand. I was probably wrong, but something did manage to damage my mbr
2)This is really my problem: I ran a repair installation after I ran FIXMBR. The order of what I did was this. I also think its worth noting that previously I was running an up-to-date XP Home with System Pack 3, and the repair disc I used was one for XP Home with System Pack 2:


-Attempt reboot, get bluescreened right after windows loading screen
-Get recovery disk, go into recovery console
-Run chkdsk /r, can access the HDD and repair a few errors found
-Remove HDD from tower, plug into another PC to back up files
-Return HDD to original machine
-Run Repair Installation, though it would bluescreen after the the first reboot
-Repeat that process again because I'm dense
-Run FIXMBR, reboot, get to the second part of the repair install process
-Finish repair install, windows tells me it needs to be reactivated
-Activation Wizard looks like this: http://i52.tinypic.com/1zmpesp.jpg
-Run a boot-time scan of Avast! while looking up what to do about Activation Wizard (This would respond to your third question, since I know viruses don't go away just because FIXMBR)
-Found this page from Microsoft: http://support.microsoft.com/kb/314935
-Made sure to make my HKEY_CLASSES_ROOT\.htm look like this exactly:

"PerceivedType"="text"
(Default) = "htmlfile"
"Content Type"="text/html"

-Reboot, little to no change
-Return to Safe mode
-Attempted to manually reinstall the Oobe.ini file, but my restore disc would not let me access its files on it
-Manually install the jscript.dll and vbscript.dll via command prompt
-Reboot, little to no change
-More research says that it may be because I'm missing IE8
-Install this hot fix: http://support.microsoft.com/default.aspx/kb/946501
-Install IE8
-Reboot, little to no change.
-Return to safe mode, attempt to upgrade SP2 to SP3 with the Microsoft SP3 Stand Alone Updater, found here http://www.microsoft.com/downloads/details.aspx?FamilyID=5b33b5a8-5e76-401f-be08-1e1555d4f3d4&displaylang=en
-Reboot, little to no change
-Give up, frustrated
-Post here

#5 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:59 PM

Posted 08 March 2011 - 09:54 AM

Okay, I'm still a little confused - sorry. It's probably me, not you. Anyway....

According to the log you haven't had a blue screen error generated from within the OS in almost two months, though you clearly had a few over a 2-3 year period. Unless there are files on the system you need to access and can't, at this point I'd consider to a clean format and reinstallation of the OS.

#6 hibachi

hibachi
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:10:59 PM

Posted 08 March 2011 - 10:06 AM

Okay, I'm still a little confused - sorry. It's probably me, not you. Anyway....

According to the log you haven't had a blue screen error generated from within the OS in almost two months, though you clearly had a few over a 2-3 year period. Unless there are files on the system you need to access and can't, at this point I'd consider to a clean format and reinstallation of the OS.


Its okay, I'm probably wording some things wrong.

That's the odd part, really, seeing as that is how this all started. I can tell you that the strongest amount of bluescreens comes from pushing video editing software too hard. I really didn't want to do a format/clean install, simply out of effort of having to reinstall so much more, and having to relocate numerous drivers... but, since I will need this desktop in working order with in a week, and that seems to be the only option, I'll probably end up doing that if no one else chimes in with an idea within the next couple of days.

#7 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:59 PM

Posted 08 March 2011 - 10:14 AM

I'm not suggesting it's the ONLY option - but from what I've been able to get from your posts it is, in my opinion, the best option. And believe me, I understand and empathize regarding the hassle involved with a new installation. I would hate to have to go through it myself. If you don't already use disc imaging software you really might want to consider it in the future. When used on a regular basis, it is the absolute best way to avoid (or at least recover from) severe problems such as you are facing.

Edited by Allan, 08 March 2011 - 10:14 AM.


#8 hamluis

hamluis

    Moderator


  • Moderator
  • 55,236 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:59 PM

Posted 08 March 2011 - 11:24 AM

Appears to be possible malware issue, looking at Google results for cov.exe situations.

Louis

#9 NicciAdonai

NicciAdonai

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 08 March 2011 - 12:23 PM

http://www.microsoft.com/genuine/selfhelp/PKUInstructions.aspx

If I am understanding you correctly, you are mainly asking for the solution to one problem: your activation issue. You said you repaired using an SP2 disc from another manufacturer. If the repair affected activation, my (possibly incorrect) hypothesis is that it may have overwritten your activation code. The above link is to a tool that will let you change your activation code (presumably back to the one you had before the repair). The disc I currently use to clean install XP for my customers is from a Gateway computer and it does not prompt me for the code, so I use this tool all the time before activating.

The activation mechanism itself seems to be damaged, but maybe whatever entries this changes are related.

#10 hibachi

hibachi
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:10:59 PM

Posted 08 March 2011 - 12:48 PM

Appears to be possible malware issue, looking at Google results for cov.exe situations.

Louis


It was this exactly. With a run of malware bytes, it cleaned out a dozen or so items including cov.exe, and upon restart the activation wizard displayed as normal! I am all up and running here, fresh as hell. Thanks for the hot tip!

http://www.microsoft.com/genuine/selfhelp/PKUInstructions.aspx

If I am understanding you correctly, you are mainly asking for the solution to one problem: your activation issue. You said you repaired using an SP2 disc from another manufacturer. If the repair affected activation, my (possibly incorrect) hypothesis is that it may have overwritten your activation code. The above link is to a tool that will let you change your activation code (presumably back to the one you had before the repair). The disc I currently use to clean install XP for my customers is from a Gateway computer and it does not prompt me for the code, so I use this tool all the time before activating.

The activation mechanism itself seems to be damaged, but maybe whatever entries this changes are related.


Though it seems that wasn't the problem, this may actually be useful to me in the future! I have about 4 other computers in the house, and though I found the actual repair disc to the malfunctioning one while looking for internet drivers, there are plenty of other computers I've been charged with taking care of as well. So while this ended up not pertinent to my problem here, it will most likely come up again, and then I'll be prepared. Thanks!

And thanks to everyone else for their suggestions and help. Unless some one thinks I should post my Malwarebytes log, I think we're safe to close shop on this one.

#11 Allan

Allan

  • BC Advisor
  • 8,551 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:11:59 PM

Posted 08 March 2011 - 01:13 PM

Glad you were able to sort it out without having to reinstall. I rarely recommend that, but based on what I was able to get from your post I thought the situation was worse than it was. I have a form of ADD that causes problems for me when I read lengthy posts, so clearly I didn't do justice to your problem. Sorry. But again, glad you're up and running :)

#12 Eyesee

Eyesee

    Bleepin Teck Shop


  • BC Advisor
  • 3,539 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:In the middle of Kansas
  • Local time:10:59 PM

Posted 08 March 2011 - 01:32 PM

I scanned this post and didnt read it thoroughly.
Sorry if I missed anything important.

It appears to me that the issue is a blank activation screen after doing a repair install of XP.
I ran into this once before.

Download and reinstall IE8 from
here.
That fixed it for me when I encountered this.
In the beginning there was the command line.

#13 NicciAdonai

NicciAdonai

  • Members
  • 20 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 08 March 2011 - 04:00 PM

Though it seems that wasn't the problem, this may actually be useful to me in the future! I have about 4 other computers in the house, and though I found the actual repair disc to the malfunctioning one while looking for internet drivers, there are plenty of other computers I've been charged with taking care of as well. So while this ended up not pertinent to my problem here, it will most likely come up again, and then I'll be prepared. Thanks!

You're welcome! By the way, I have had a hard time Googling that link in the past, and bookmarking does no good since I always need it on a fresh install. My solution was to send the link to myself in Gmail and then access my account whenever I need it. Maybe a better solution would be to save a shortcut on a thumb drive.

#14 hibachi

hibachi
  • Topic Starter

  • Members
  • 63 posts
  • OFFLINE
  •  
  • Local time:10:59 PM

Posted 08 March 2011 - 09:05 PM


Though it seems that wasn't the problem, this may actually be useful to me in the future! I have about 4 other computers in the house, and though I found the actual repair disc to the malfunctioning one while looking for internet drivers, there are plenty of other computers I've been charged with taking care of as well. So while this ended up not pertinent to my problem here, it will most likely come up again, and then I'll be prepared. Thanks!

You're welcome! By the way, I have had a hard time Googling that link in the past, and bookmarking does no good since I always need it on a fresh install. My solution was to send the link to myself in Gmail and then access my account whenever I need it. Maybe a better solution would be to save a shortcut on a thumb drive.

I'll be sure to save it to my e-mail or shortcut it to a thumbdrive.

Hilariously enough, I have virtumonde now :(

Well, I think its Virtumonde since its doing the same thing virtumonde did before. IE pop ups, solely for Babylon Software though. I suppose I should go make another thread about this.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users