Windows 7: BSOD When Idle WER-79030-0.sysdata.xml

My Windows 7 PC has recently started frequently crashing, apparently before it goes into sleep mode because I've never seen the blue screen myself, rather, when I go to turn it on after I've been away it is often turned off completely. When I re-apply power the BIOS tells me Windows recovered from a crash (and whether to start Windows in Safe Mode or not). The Crash Information from the window that pops up after booting in says the following:

The SF_DD_MM_YYYY.zip from the SF_Diagnostic_Tool.exe is attached. My PC Specs are uploaded to my Profile.

I don't believe I've done any major changes to my PC, though it did belong to someone else before; this kind of came out of nowhere nonetheless.

Help is much appreciated, thanks

Welcome
You have a common problem an anti virus playing bad with Windows
Make a system restore point.
Uninstall your anti virus,Eset.
Install Microsoft security essentials
This is the specific driver involed in each bsod
Epfwndis.sys file descriptionProductname:ESET Smart Security Description:ESET Personal Firewall NDIS filter Company:ESET

Hi, thanks for the reply, your diagnosis is exactly what I needed. I updated my ESET 4 to ESET 5 and that resolved the issue. Glad I didn't have to go to Security Essentials since ESET has more features (and is supposedly one of the best Anti-Virus software).

Thank you.

I and most of the senior members disagree about Security Essentials, but in any event I am glad that the BSOD problem is resolved.

Hello, sorry to bump this old thread back up, but shortly after I believed the issue to be resolved, I again started getting BSOD when going into sleep mode. So I uninstalled ESET and put Security Essentials, but this did not resolve the issue.

This time, however, I noticed the message in the BSOD was "DRIVER POWER STATE FAILURE," so I did some googling and went with the Diver Verifier guide here on the forums. After using it and reading the BSOD dump file from the crash with a dump file reader I found, the highlited red filename was not only ntoskrnl.exe, as all the previous dump files claimed was the issue (everyone says that's a critical windows system process and is usally an incorrect reading), but also wmBEnum.sys with a "Address in Stack" of WmBEnum.sys+28b8.

So I looked it up, and wmBEnum.sys is the "Logitech WingMan Virtual Bus Enumerator Driver." I searched in my device manager and found "Logitech Virtual Bus Enumerator Drive" under "System Devices. I disabled it, uninstalled it, verified my Wingman joystick still worked (this was not the joystick's driver apparently), restarted the computer, and now it goes into Sleep Mode just fine with no BSOD.

Thought I would put this up here for other people's reference in the off chance that someone else might in the future googe around for a solution to a similar issue. I'm not sure what the whole ESET thing was about. I guess I'll install ESET again and see what happens, but Security Essentials works fine I guess.

I have to thank you and the sevenforums for having all this useful information up here that let me solve this, thanks!