Event viewer id help please

hi guys,

I have had windows 8 installed for about 4 days now and I just looked in event viewer and there are lots of kernel power and kernel pnp warnings and errors.

event id 137 says. . . The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S5). This can result in reduced resume performance

and event id 219 says... The driver \Driver\WudfRd failed to load for the device SWD\SensorsAndLocationEnum\LPSensorSWDevice.

can anyone help me with these please or are they ok ?

pc is running ok I think, just a few app errors and steam errors in the event viewer aswell.
the event id 219 I just started getting today but the event id 137 has been happening a lot

Do you think it could have anything to do with the fast start up option on off thing on the power options. I have turned it off now coz I don't use hybrid sleep.

It may - what's the source of the event ID 137 messages in the event viewer? It can be many, including NTFS, VSS, etc - it helps to know the source as well as the event ID number.

hi there,

it says source Kernel-Power they both do.

I haven`t had anymore of the warning in event viewer thismorning at the moment

hi,
my pc has just bsod on me, I ran who crashed and it cam up with this can you help me please?

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 20/01/2013 09:04:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012013-13010-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x109 (0xA3A039D898AC57FC, 0x0, 0x506EAA98182E4ACB, 0x102)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 20/01/2013 09:04:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA3A039D898AC57FC, 0x0, 0x506EAA98182E4ACB, 0x102)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

---

Conclusion

---

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


my ram has been fine the only thing I have done different is install windows 8

The first one about the Sleep states seems to involve a system that is basically shutdown, or a Soft Off. Could it be related to Fast Boot, possibly, since they both involve booting the system. But I have Fast Boot enabled, and it doesn't always work without complaining, but I have not see that error or warning.

Soft Off
S5
The system appears to be off. Some components remain powered so the computer can wake from input from the keyboard, LAN, or a USB device. The working context can be restored if it is stored on nonvolatile media.

Click to expand...

System Power States (Windows)
System Shutdown State S5 (Windows Drivers)

This from my system when doing a Powercfg -A command in a Command Prompt window.

The following sleep states are available on this system:
Standby (S3)
Hibernate
Hybrid Sleep
Fast Startup

The following sleep states are not available on this system:
Standby (S1)
The system firmware does not support this standby state.

Standby (S2)
The system firmware does not support this standby state.

Standby (Connected)
The system firmware does not support this standby state.

Click to expand...

As far as the other one, are you using a device that tracks locations, like a cell phone? But there are several references online to the WudfRd driver problem mentioned.

I haven`t had the warning thismorning. but I have had the BSOD

not sure how to zip my mem dump file its not letting me, do I need to make it a complete mem dump file or something? Im still a bit of a noob when it come to computers

Might want to post specifically in the BSOD section for help once you follow the instructions on posting there.

Turn off hibernation

I solved that problem by turning off hibernation.

In my case (win8.1 on laptop HP 6730b) the state resulted in the network card not functioning, needing some (any) change to the BIOS to make it work again.

A few experiments revealed that this thing occurs when the system automatically goes from sleep to hibernate.
Standard setting was sleep after 30 minutes and hibernate after 180 minutes. For the experiments I changed these to 1 and 2 minutes.
Waking before hibernate never gives a problem.
Waking beyond the hibernate threshold always produces the problem.

So I opened an administrator elevated command prompt and gave the command
powercfg /hibernate off

Problem solved.