Several 31004 event IDs, Windows Startup Repair launched - but now ok?

[450125]

This concerns a Win7 ASUS laptop we have.

My wife restarts it every night before winding up her day (good), but I just learned she often closes it (putting it into sleep I guess) before it has booted to the login screen. I cannot imagine this is very good, and she's going to be more careful in the future.

Tonight when she opened the computer and pressed the power button, she got the normal "Windows 7 is starting" graphic, which seemed to take longer than usual, and then the "Windows Startup Repair" began. Not good.

It ran for maybe 45 minutes, and we got an error saying that startup repair couldn't repair the computer, and there was a "more information" presentation that I did not write down (how does one electronically save such information, or is it retained somewhere on the hard drive?). I clicked "finish" and the machine smoothly shut down.

Just for giggles - what else could go wrong, right? - I pressed the power button and this time it went through what appeared to be a normal Windows boot, right to the login screen, the login went fine, and the computer has been running fine for a while now.

I looked at the event log, filtered down to "critical" and "error" messages, and there was nothing critical - BUT - at startup the last several days, it's been logging a "31004" event ID error. "The DNS proxy agent was unable to allocate 0 bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error" is the Windows message associated with this.

Since the computer is functioning fine, seemingly, and has through several days of this error message, I'm not "too too" concerned. But since it's appearing, and especially since we got the Windows startup repair today (perhaps caused by closing the computer at an inopportune time during startup?), I'm not "too too" happy either.

Any ideas what's happening, or what I should check?

Thanks.

 

[gregrocker]

I like to use Hibernate for closing the lid or power button, or to time into after 45 minutes, since it starts back up twice as fast and saves all my work if I walk away and dont wanna come back for an hour or a week.

As long as you do reboots when requested for Updates or if it gets sluggish, there's no reason to restart a lot.

Since you have an interest you can go over your system and optimize it working through these Troubleshooting Steps for Windows 7. Anything that's a problem should show up, and you might head some off. For example, how many freeloaders are starting on Win7's back?