Frustration with MSI K8N Neo2

Help,

Okay, I'm not a novice at rebuilding PCs but I have encountered nothing but problems with my new MSI K8N Neo2 Platinum. The basic components are:

MoBo - as stated above
CPU - AMD 64 3200+
RAM - 2 X Corsair TwinX 1024 - 3200 mounted in slots 1 & 2 for Dual channel
Graphics - Radeon 9250 w/128 Meg
Boot drive - Maxtor 100 Gb SATA
PSU - Antec NeoPower 480W

I have rebuilt this PC 5 times now with the same results. I even sent back the MoBo and CPU for exchange thinking the components were defective. After loading XP Pro on the boot drive and succesfully booting into Windows everything is smooth until I install Win XP SP2... Then the PC begins rebooting itself about every 5 - 10 minutes and the session are very sluggish. I ran the PC all day before putting in SP2 with no issues other than Power DVD unable to perform playback. I am writing this email in safe mode as that is the only stable operating condition presently....

Any suggestions????

 

Windows XP won't boot after installing SP2 – a BIOS update may be necessary

by Mark Kaelin | More from Mark Kaelin | Published: 8/31/04
Keywords: Microsoft Windows | Windows XP
Rating: 4.9 (out of 5) Rate it Comments: 20 | 0 NEW | View all

Takeaway:
Installing Microsoft Windows XP Service Pack 2 on a PC with a "Prescott" CPU and certain chip sets can cause it to fail to reboot completely. The problem can be solved with a workaround or a BIOS update.


If you have an explanation or quick fix that would make a good SolutionBase article, then we invite you to submit your solution using this form.

Windows XP Service Pack 2 (SP2) is a complex update with many ramifications for IT pros. TechRepublic's Windows XP Service Pack 2 Quick Guide drills down on critical SP2 need-to-know areas, with sections on fundamentals, changes that occur after installation, deployment procedures, problem areas, and removal.
Problem

Depending on the chipset, motherboard manufacturer, BIOS version, and CPU, installing Microsoft Windows XP Service Pack 2 can result in an unbootable computer system. The problem is generally associated with Intel "Prescott" CPUs and its chipsets, but not every such combination will cause a problem. As of this writing, motherboards exhibiting the behavior include:

* Albatron PX865 PE Pro
* Shuttle SB61G2
* Jetway i875P
* Soyo P4I865P
* Aopen AX4SG Max
* Asus P4P800-E deluxe
* Abit IS7-V
* Foxconn 865A01-G-6EKRS

Technically speaking, the problem revolves around the machine's BIOS not installing a production level microcode update. To check whether the BIOS is at the correct level, download the Intel Processor Frequency ID utility. The microcode version is identified by this utility as CPU Revision, which should equal at least 8.
Solution 1

If the Intel utility shows that you have the wrong microcode version, the primary solution to the problem is to update the system BIOS for your motherboard before you install SP2. Here are some motherboard manufacturer links:

* Albatron
* Shuttle
* Jetway
* Soyo
* Aopen
* Asus
* Abit
* Foxconn

BIOS updates

BIOS updates can be dangerous—please follow the manufacturer's instructions very closely to avoid a major catastrophe.
Solution 2

If you have already installed XP SP2 and have a PC that will not boot because of this microcode version problem, there are two workarounds you can try to get to a bootable state.

In the BIOS setup you should temporarily disable the L1 and L2 cache. On some motherboards, this will allow the computer to boot. You should then remove SP2, turn the L1 and L2 cache back on, and then update the BIOS to reflect the correct microcode version. After completing these steps, you should be able to re-install SP2 without running into this particular problem again.

If disabling L1 and L2 cache does not work, you can use a second workaround suggested by a representative at Intel: Boot the problem computer with an alternative OS or to the safe mode command line if possible. Assuming you can get to the Windows directory on the boot partition, navigate to this file and change its name so that it does not load the next time the machine is booted:

windows\system32\drivers\update.sys

After rebooting you should be able to install XP SP2, but keep in mind this is a temporary fix—the system will be unstable until you update the BIOS and reactivate the update.sys file.
Next Steps: Build your skills with these hand-picked resources
> TechRepublic's Windows XP Service Pack 2 Spotlight
> Intel® Processor Frequency ID Utility
> Microsoft Windows Server Community
> AUMHA FORUMS
> Whirpool Forums

 

Hey petalumacacraigslist,

Quite a detailed reply and thanks much. Actually I can boot into Windows but the issue was my OS triggering a reboot at its own about each 10 minutes. I seem to have circumvented the issue by disabling the "automatically restart" after system failure in Startup and Recovery. My PC has been going for about 3 hours now with no issues..??? I haven't solved the main cause and I would really like to as I hate unsolved problems. Now I have several dmp files in the %SystemRoot%\Minidump... Care to suggest an app that will read them???

Thanks again for your help,
Mark

 

I have this same motherboard, but not this issue. Have you checked to see what the stop error is? You must turn off auto restart first. go to system properties, advanced, startup and recovery settings, and under system failure, uncheck automatically restart. Then post back with everything the error says, and if you can, post the memory dump created, which will be located in C:\windows\minidump, and when I, or someone else has a chance, we can debug it for further info.

 

Adrynalyne,

Thanks for the reply. Since I disabled the auto restart after error I have had no issues, but I would still like to understand what's going on in the background to cause the issue in the first place. I ran the PC all night with Media player with no issues, Dumps attached below and renamed to ..txt for upload..

Another issue with this upgrade still lingers. My Sony DRU-800A just purchased, and the prior model, DRU-510A, refuse to play DVDs. The unit will read and write to the media, FujiFilm, but not visual playback. I have the unit as master on the NVIDIA Primary IDE channel and currently set to ULtra DMA 4 - Ultra66. Reading and writing are very fast, no problem, but playing a movie is not possible as th unit just locks up....

Thanks again
Mark

 

Black ice is/was the application crashing your computer.

Here are the outputs:




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


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\Mini082005-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Aug 20 16:01:09.671 2005 (GMT-7)
System Uptime: 0 days 0:00:39.265
Loading Kernel Symbols
..............................................................................................................................
Loading unloaded module list
...
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {a8e39888, 16fd0163, a8e397f4, 1}

Unable to load image BlackDrv.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for BlackDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for BlackDrv.sys
*** WARNING: Unable to verify timestamp for SYMTDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
Probably caused by :BlackDrv.sys ( BlackDrv+1033 )

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

kd> !analyze =v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {a8e39888, 16fd0163, a8e397f4, 1}

Probably caused by : BlackDrv.sys ( BlackDrv+1033 )

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





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


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\Mini082005-09.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Sat Aug 20 16:06:44.828 2005 (GMT-7)
System Uptime: 0 days 0:00:52.421
Loading Kernel Symbols
..............................................................................................................................
Loading unloaded module list
...
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {a90e6888, 170be163, a90e67f4, 1}

Unable to load image BlackDrv.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for BlackDrv.sys
*** ERROR: Module load completed but symbols could not be loaded for BlackDrv.sys
*** WARNING: Unable to verify timestamp for SYMTDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
Probably caused by : BlackDrv.sys ( BlackDrv+1033 )

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

kd> !analyze =v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {a90e6888, 170be163, a90e67f4, 1}

Probably caused by : BlackDrv.sys ( BlackDrv+1033 )

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

 

Adrynalyne,

Wow, thanks for the input. I did previously go to MS.com and downloaded dumpchk but did not receive the clear text output yopu show below! Did you also use dumpchk or should I just search MS for the debugger you ran...

Anyways, thanks for the interpretation.... So now that I have "auto restart" deactivated and my PC is running smoothly I need to consider what to do about Black Ice.... Switch to a different firewall or uninstall / re-install???

Either way I have to wait for the weekend as I am on assignment away from home and can't play... :{

Suggestions??

Thanks again,
Mark

 

I used Windbg. I have a write up on this forum if you would like to learn more about it.

http://forums.majorgeeks.com/showthread.php?t=35246

In regards to Blackice, you really only have two options. Upgrade, or find another firewall. There are plenty of good free alternatives. I'm particularly fond of Sygate myself.

http://www.majorgeeks.com/Sygate_Personal_Firewall_Free_d3356.html

 

Adrynalyne,

Thanks again. Your instruction has been very helpful indeed. I used to read core dumps back when I was a system anaylst programming in COBOL...

When I get back home I will remove BlackIce and install ...?? Actually I have Symantec firewall and have asked my tech support if this is 64 bit compatible. I have also played with Sygate and Zone Alarm in the past.

Thanks again for the tutorial, I can use this technique for many issues (that I do not want to have) in the future...

Mark

 

No problem