Windows 7 Woes

Hi guys,

I have been lurking these forums for a while and this I must say is one of my favourite sites.

Now, Since a lot of you are using an RTM version, I just wanted to ask if most of you see the same issues as I do with 7

1) I often see a lot of Hive issues in the event viewer especially with PGP disk.

2) Another pet peeve is the HAL issue when you wake from S3 mode.

3) Third is also the side by side issues that arise now and then. Especially with X64. I fixed one for Movie maker Live using Restuner. The issue is gone. I also have one with Nero but not all the time.

My question, do yoou guys see the same issues as I do??

Thanks to all.

2) Another pet peeve is the HAL issue when you wake from S3 mode.

Hey did you try the S1 mode instead?

Antman said:

For the record, woes.

Antman, Please excuse my English. Corrected.

Here is a typical side by side issue.

Activation context generation failed for "c:\program files (x86)\Nero\Nero 9\nero waveeditor\WEDll\waveedit.dll.Manifest". Dependent Assembly SMC,processorArchitecture="x86",type="win32",version="6.3.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

Here is A HAL issue.
."The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system"

Log Name: System
Source: HAL
Event ID: 12
Level: Error

This leads to supect that the bios has a config issue. Is this the case or is this just an ACPI conflict?

The article [KB314088] (XP though) describes the process used by Windows to enable and install Advanced Configuration and Power Interface (ACPI) functionality. An ACPI system consists of a series of 10 tables that define which devices are present on the system and what their capabilities are as to configuration and power management that are built by the system BIOS at startup. When the computer starts, the system BIOS looks for specific entries in two of these tables, 1) the Fixed ACPI Description table [FACP] and 2) the Root System Description table [RSDT] to determine whether the system is ACPI-compliant. Information is extracted from these tables in the form of an OEM ID, OEM TABLE ID, OEM REVISION and CREATOR REVISION. If these tables are not present or if the information in those four descriptors is invalid, the system is assumed not to be ACPI-compliant and the legacy hardware abstraction layer (HAL) is installed.


I don't know and not many seem to either.

Dinesh said:

2) Another pet peeve is the HAL issue when you wake from S3 mode.

Hey did you try the S1 mode instead?

S3 has always worked, why try S1??

kegobeer said:

Have you updated your BIOS to BTX3810J.86A, version 2000, posted July 1, 2009? Are you using the Windows 7 drivers available from Intel for your board?

I always use the latest updates.

Thanks.