Eek! Scary error message!

[baarod]

But I already have the latest firmware!!!

Anyone else seeing this in the Administrative Events custom view in Event Viewer?

Log Name:      System
Source:        Microsoft-Windows-HAL
Date:          12/22/2008 12:10:13 PM
Event ID:      12
Task Category: None
Level:         Error
Keywords:      (1)
User:          N/A
Computer:      Orion7
Description:
The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-HAL" Guid="{63D1E632-95CC-4443-9312-AF927761D52A}" />
    <EventID>12</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000001</Keywords>
    <TimeCreated SystemTime="2008-12-22T18:10:13.993078300Z" />
    <EventRecordID>9603</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="3916" />
    <Channel>System</Channel>
    <Computer>Orion7</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="Count">1</Data>
    <Data Name="FirstPage">14</Data>
    <Data Name="LastPage">14</Data>
  </EventData>
</Event>

 

[johngalt]

I just looked, and other than a *lot* of DHCP v6 Client errors, I don't have that one in there

 

[baarod]

I had those DHCPv6 messages too until I disabled the IPv6 binding on my primary NIC.

 

[darkassain]

does your router support Ipv6???
then i am guessing that it would be it....

 

[NormCameron]

But I already have the latest firmware!!!

Anyone else seeing this in the Administrative Events custom view in Event Viewer?

Log Name: System
Source: Microsoft-Windows-HAL
Date: 12/22/2008 12:10:13 PM
Event ID: 12
Task Category: None
Level: Error
Keywords: (1)
User: N/A
Computer: Orion7
Description:
The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-HAL" Guid="{63D1E632-95CC-4443-9312-AF927761D52A}" />
<EventID>12</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000001</Keywords>
<TimeCreated SystemTime="2008-12-22T18:10:13.993078300Z" />
<EventRecordID>9603</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="3916" />
<Channel>System</Channel>
<Computer>Orion7</Computer>
<Security />
</System>
<EventData>
<Data Name="Count">1</Data>
<Data Name="FirstPage">14</Data>
<Data Name="LastPage">14</Data>
</EventData>
</Event>

I've seen those in Vista too. I disabled Ipv6, don't need it as my router won't use it.

Norm

 

[p7ast1k]

Hi all, first post
was there any solution to this?
i've started seeing these event 12, HAL errors in the 7048 x64 build after waking the PC from sleep

 

[mtp]

also getting this error

I am using Windows 7 RC build 7100 and am also getting this error (HAL event ID 12), but it does not seem to be causing any troubles - everything seems to be working.

It seems to be related to going to or coming out of sleep.

Anyone know anything more?

Thanks

Mark

 

[swarfega]

If the router doesnt support IPv6 then turn IPv6 off.

 

[dmex]

If the router doesnt support IPv6 then turn IPv6 off.

Swarfega,

That advice is completely unrelated to the problem they are experiencing :sarc:

 

[mtp]

ipv6 not relevant in my case

I was not getting any IPV6 warnings or messages (and my router is IPv6 capable), but I disabled IPv6 on my NIC to test anyway and found that the problem remains....


Any other suggestions

 

[SoLoR]

I had this error as well, until i was using that defaul teredo tunnel ****. Now i fixed my own tunnel over sixxs and made whole home network ipv6 as well and now everything works fine. Disabling ipv6 shouldnt be solution since, that will be the future in about a year or so (when ips for ipv4 runs out). So rather start to use ipv6 with ipv4 and not just disable it

 

[p7ast1k]

i still get these HAL error messages when sending the PC to sleep
haven't got a clue how to prevent them from appearing

don't think my router supports IPv6, it's an old D-Link DGL-4300 *shrug*

should i be leaving IPv6 enabled anyway since it uses teredo tunneling to send IPv6 packets over IPv4 UDP ?
or have i got this completely wrong ?

 

[SoLoR]

nah teredo tunnel is seperate thing from network adapter. You should not need ipv6 on network adapter to have teredo working (unticked, protocol however still needs to be installed). However teredo is so unstable thats is basickly not usuable at all.

anyway how if fixed this msges was, to disable everything from ipv6 compleatly, this inclueds removing ipv6, teredo and disabling 1 (or maybe 2) services from ipv6. However like i said, this should not be solution..

 

[Hammerhead786]

But I already have the latest firmware!!!

Anyone else seeing this in the Administrative Events custom view in Event Viewer?

Log Name: System
Source: Microsoft-Windows-HAL
Date: 12/22/2008 12:10:13 PM
Event ID: 12
Task Category: None
Level: Error
Keywords: (1)
User: N/A
Computer: Orion7
Description:
The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system.
[/quote]
 
I get that error message too when going into sleep mode. Contacted Asus support about it and got no real response from them.

 

[ncguy]

I'm receiving this message also. I have an Intel Dp35DP motherboard and I just flashed to the latest BIOS. I'm running W7 RC1. So far this message doesn't seem to have caused any apparent problems but it is a bit worrisome. I dual boot this machine to vista ultimate and I'm not seeing anything related when I boot into Vista. I think its definitely W7 related. I wonder what the common hardware is that's causing this to show up?

 

[mtp]

P35

I wonder what the common hardware is that's causing this to show up?

I have this problem on 2 of 3 computers that I have installed W7 on. I do not get the error on an Asus laptop. I do get the error with my Gigabyte Ga-p35-ds4 and my Gigabyte ga-p35-dq6. Perhaps it is related to the p35?

I also seem to have other problems with the p35 boards in that if i put a second hard drive in (data only drive), quite often it is not found when the computer wakes up. I have avoided the problem by putting the second drive on the secondary (Jmicron controller) on the board.

I wonder if there is a problem with the p35 or the chipset driver. What chipset driver areyou using?

Mark

 

[ncguy]

I wonder if there is a problem with the p35 or the chipset driver. What chipset driver areyou using?

I'm using the default's after the RC1 install. There weren't any problems showing up in device manager after the install. Since W7 isnt supported yet by any of the HW guys I felt that Microsoft might actually have chosen the best drivers in the case.

Anyhow, when it comes to chipset, which device do you look at in device manager to see the driver that Microsoft actually used? How risky do you think it would be to install Intel's latest chipset driver?

Update: From looking at all the MB devices best I can tell the default chipset drivers from the RC1 install are Microsoft drivers.

 

[jarealest]

aftering disabling teredo

All I did was disable teredo through netsh command and gained 10% system resources back and a pesky Symantec network pop-up went away. I agree that hopefully I can figure out how to make this IPv6 tunnel work so when the internet does upgrade I won't have the same problems.

 

[Teerex]

This is nothing to be worried about - Microsoft has issued a paper detailng what this message is about and what its purpose is.

Firmware Corruption of Memory During Sleep Transitions

 

[Bobdeer]

This is nothing to be worried about - Microsoft has issued a paper detailng what this message is about and what its purpose is.

Firmware Corruption of Memory During Sleep Transitions

Nothing to worry about?? Thats easy to say cept when my SATA drive vanishes when that error pops up.