Question for Microsoft:Lots of users has this problem

Moto Guzzi

[H]ard|Gawd
2FA
Joined
Aug 9, 2002
Messages
1,138
EventViewer:
An error was detected on device \Device\Harddisk0\D during a paging operation.
>In my case it only happens at bootup.
>XP-PRO...MB=GA-8IEXP Rev 2.1 BIOS=F9[Latest]..786MB...P4 2Ghz, now 3.06GHz.

This fault/error is driving me nuts. Since I had my PC 3.5Years, I never saw this problem in Eventviewer till I did the following:
1-Install larger PSU=AOPEN 300W upgraded to 550W.
2-Install larger processor:FRom 2Ghz/400[Without HT] to 3.06Ghz/533[With HT].
3-Still SP1 at this stage.
4-Disk=WD 40GB & MAX 40GB=Both do it.
4-Problem only appears if Hypertreading is enabled in BIOS......!!! The problem also disappers if I disable IDE-2, on which my CD-RW[Master] and DVD-ROM[Slave] is connected.

Solving the problem while at SP1.
>Upgrading the Intel 845E chipset, then upgrading IAA also.
I managed to get rid of it by Uninstalling the processor, then reboot and enable HT, then XP loads both Processor.sys drivers. I never saw it again,
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
UNTILL:
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
>>>>I installed SP2....Now I have tried everyting in the book I know, except:
.....I upgraded to Seagate 120GB disk, 8mb/7200, but now luck.
1-Sfc.exe
2-Repair XP
3-Re-Install XP
#######################
*I do believe that this problem causes other little problems also like with burning CD's.
**I do believe that this problem has to do with Hypertreading and IAA and the faster speed demands from disks as a result of these.
***One or other way we must get Microsoft and the Disk Manufacturers as well as motherboard/chipset/Processor manufacturers to sort this out.....!!!
#####################
Question-1: Can anybody tells me what the "/D" stands for. My drive D is the CD Writer[AOPEN] on IDE2. ??
Question-2:With bootlogging enabled, the system loads the driver SCSIPORT.SYS...Why on earth, I don't use SCSI method ??
#####################
Research: Which subsystem hardware you got ?
1-Motherboard=
2-Chipset=
3-HT Enabled ?=
4-Processor=
>FSB=
5-Disk Drive=
6-Type IDE/SATA/RAID ?=
7-CD-RW & CDROMs ?=
8-Have you got IAA [Intel Application Accellerator installed ?=
#####################
Important thing I noticed on a PC which does not have this problem, but it has SP1 still.
>>>A Dell Computer 3.2 GHz 800FSB. In Device manager I noticed IAA was not used and it show dual lines for the Intel Ultra ATA controllers, where myne only has one entry with IDE1/2. ??????, maybe with newer chipset design ?
#####################
This is a pain-in-the -a...ss-BUG.
 
There is one thing I can always be sure of, and that is, that as soon as I uninstall IAA, or the processor drivers[WIN XP reinstall them on next reboot], the condition is always missing on the next reboot.

Last night I made this discovery: Intel readme with IAA 23, mention that you must check for the following files to confirm IAA is instaled correctly:
1-IdechDr.sys
2-IdeBusDr.sys
3-IprtCnst.dll
Now if I uninstall IAA, then reboot[Prefetch files deleted beforehand], and then go and uninstall the chipset drivers, windows XP-PRO actually re-install these files as above, but without the IAA executable interface. So it looks like part of IAA is taken care of by XP.

If I now go and uninstall Processor-1, then XP install Intellppm.sys instread of Processr.sys ....Somebody mentioned Intelppm.sys comes with SP2 ??

If I now uninstall Processor-2[Virtual of HT], on re-boot XP loads Intelppm.sys for it too.
This is how myne is currently. I then futher changed the way users logon/off by unchecking Welcome screen and fast user switching.

>So far after 6x reboots, the problem is still gone, but I know it may return..

:D
The readme of IAA also mention about OEM products, and special treat for them, which I not fully understand so far. ?? I have a OEM-Product..
 
To load just the driver as outlined in the Microsoft*
document, "Deployment Guide Automating Windows NT Setup,"
use the supplied TXTSETUP.OEM file included in this
package and insert the lines below into the UNATTEND.TXT
file. This method is available for Microsoft* Windows*
NT* 4.0, Windows 2000, and Windows XP. (For Windows NT 4.0,
the TXTSETUP.OEM, INTELATA.INF, and INTELATA.SYS files need to
first be extracted from the compressed .CAB file. For
Windows 2000 and Windows XP, the idechndr.inf, IdeBusDr.sys,
idechndr.sys, and Txtsetup.oem files need to be extracted.
To extract these files, run 'SETUP -A -P <path>' as described
above.)

Microsoft Windows NT 4.0:
// Insert the lines below into the UNATTEND.TXT file

[MassStorageDrivers]
"Intel Ultra ATA Controller" = OEM

[OEMBootFiles]
INTELATA.INF
INTELATA.SYS
TXTSETUP.OEM

Microsoft Windows 2000 and Windows XP:

// Insert the lines below into the UNATTEND.TXT file

[MassStorageDrivers]
"Intel(R) 82801BA Ultra ATA Controller" = OEM
"Primary IDE Channel" = OEM
"Secondary IDE Channel" = OEM

[OEMBootFiles]
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys
Txtsetup.oem

The IprtCnst.dll file must be placed in the following
folder in your directory structure in order to be loaded
during driver installation:

C:\I386\$Oem$\$$\System32

Please refer to the following Microsoft Knowledge Base
article for information on why the IprtCnst.dll file
cannot be listed in the [OEMBootFiles] location in the
unattend.txt file:

http://support.microsoft.com/support/kb/articles/Q275
/3/34.ASP?LN=EN-US&SD=gn&FR=0&qry=Q275334&rnk=1&src=
DHCS_MSPSS_gn_SRCH&SPR=CHS
 
I think I follow what your trying to say….I think.

If you pull a non HT CPU out and install an HT you can indeed create this problem. It’s similar to running an SMP machine.

Sometimes you can luck out and turn CPU-1 on, sometimes not. HT is interesting in that it tricks your OS into thinking your running HT.

Do you have two sticks of RAM in the slots allocated for HT?
Are you running XP Pro?

Try a clean install after checking both of those items above, it just might fix your problem.

I only found all this out after I did a clean install on a dually board with only one CPU. After adding the second CPU similar stuff started happening.

Just some thoughts
 
This is a board with a Single Processor, and the options for memory, has nothing related to HT as far as I could make out.

I did managed to get rid of the problem while in SP1, without reformatting/re-Install.

SP2 screwed it up again, and so far I cannot get rid of it.......I'll 1st dig for a couple of months before re-install.

If I take the reference for SP2 memory management complete out of the boot.ini file, things change a bit....Then Norton Unerase Wizard start appearing in Eventviewer...Never happened before.
 
Moto Guzzi said:
This is a board with a Single Processor, and the options for memory, has nothing related to HT as far as I could make out.

I did managed to get rid of the problem while in SP1, without reformatting/re-Install.

SP2 screwed it up again, and so far I cannot get rid of it.......I'll 1st dig for a couple of months before re-install.

If I take the reference for SP2 memory management complete out of the boot.ini file, things change a bit....Then Norton Unerase Wizard start appearing in Eventviewer...Never happened before.

Understood, but windows "SEES" HT as two cpus, not one. As such it tends to treat the machine as SMP. If in fact the motherboard is an HT motherboard then is a different way the memory is allocated, as in which slots are used.
 
I picked up more info:Another guy has 2x PC's with XP/SP1 & Win2000/SP3..He managed to solve problem on these Service Packs as I did, but it came back on both systems with XP/SP2 & Win200/SP4....He then only could solve the problem by replacing both motherboards with slightly different Versions...ASUS MB's.

It is interesting to see that it happens on completely different MB's.

I don't think I want to reformat at this stage.......I think Microsoft should take responsibility for this bug, even if it does not happen all machines[Thats by Eventviewer entry], they may discover a selution to various other problems in subsystems that we are not even aware of, to greater stability and in the end to their own benifit.

I think when I run out of Norton2004, and switch to 2005, I'll buy a new disk, and do a clean install, then use it without any Norton to see what happens.

$$$$$$
I also noticed that the entry for this in EventViewer, is always "BackTimed" in relation to the other entries before and after it, I.E it's time does not fit to those entries around it.
The EventLog Service is handling this, but cannot be stopped.
 
Moto Guzzi said:
I picked up more info:Another guy has 2x PC's with XP/SP1 & Win2000/SP3..He managed to solve problem on these Service Packs as I did, but it came back on both systems with XP/SP2 & Win200/SP4....He then only could solve the problem by replacing both motherboards with slightly different Versions...ASUS MB's.

It is interesting to see that it happens on completely different MB's.

I don't think I want to reformat at this stage.......I think Microsoft should take responsibility for this bug, even if it does not happen all machines[Thats by Eventviewer entry], they may discover a selution to various other problems in subsystems that we are not even aware of, to greater stability and in the end to their own benifit.

I think when I run out of Norton2004, and switch to 2005, I'll buy a new disk, and do a clean install, then use it without any Norton to see what happens.

$$$$$$
I also noticed that the entry for this in EventViewer, is always "BackTimed" in relation to the other entries before and after it, I.E it's time does not fit to those entries around it.
The EventLog Service is handling this, but cannot be stopped.

Microsoft take responsibility? That was a joke, right? ;)

There is a huge difference in Norton 2005. For some reason Norton figured out that the NTFS file system is in wide use, and they fixed 2005 so it actually sees and works with it. System works will also replace Ad aware and what ever other spyware you are running and it works well. For once Norton did a good thing.

Have fun, enjoy
 
Back
Top