PC frozen for c.30 secs after boot

[martinlest]

When I boot the (Win7 x64) PC (but not usually after a reboot: at least I think that's true) many functions take up to 30" to start: various applications won't run (e.g. Task manager, MS Office; no desktop gadgets appear - a mixed bag) for this period, then suddenly everything comes to life, including applications I tried to open initially. After that everything seems to run normally.

The only thing I see in Event Viewer is (the dreaded) "The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2" warning (yes, Asus M/B) Event ID = 219.

Thousands of posts around about that - and seems that so far there's no solution, unless I missed something recent.

What I wanted to ask, as I haven't been able to verify, is it that error that's the reason for the partial freeze-up of the PC after booting? Or do I need to troubleshoot something else? If so, ideas welcome!

Thanks.

 

[johnhoh]

try start > run > services.msc > enter > find "Windows Driver Foundation - User-mode Driver Framework" > right click it > change properties to automatic > click apply > reboot

 

[martinlest]

Ooops, sorry, I forgot to write that I already did that (I did try researching this a bit before posting) - it doesn't seem to help.

I was going to try msconfig (i still can I suppose) but reading all the info about this problem convinced me it'd be a bit pointless.

Many thanks

 

[johnhoh]

did you see this possible fix? post #9 refers to your issue

https://rog.asus.com/forum/showthre...ds-Unknown-Device-ACPI-PNP0A0A&highlight=amda

 

[martinlest]

No, I didn't see that, thank you very much for the link.

I tried the 'fix', and got the dll file generated: I don't (and didn't) have any unknown device showing in Device Manager though. I'll see what happens over the next day or two, nevertheless, and post back...

EDIT: Very next boot - same issue. About 45" before desktop items start responding/appear. Some programmes work, others only fire up after the time delay. Same warning in the Event Viewer.

I wonder if it's worth doing a boot trace. Is it sure the delay in the system getting up and running after the desktop appears (which in itself is very fast, about 35 seconds for a full reboot from desktop to desktop) is due to the ACPI issue?

 

[martinlest]

Actually, Task manager does run during the 'go slow'. It shows that that programmes do start up when you click on the exe file, but they remain at zero CPU usage for the duration... then everything comes alive and works as normal thereafter.

I tried starting Process Monitor to try to analyse what might be happening (added a shortcut to the Startup folder) but it hangs like most other stuff (not everything, ass I asay, some programmes, like cmd.exe, work straight away) until the issue clears itself.

If it were just the M/B problem, why has this come about only in the past few weeks? Same hardware configuration as ever. It's a bit awkward to troubleshoot, as it only tends to happen (as others have noted elsewhere) after a boot (not reboot) and when the machine has been off for a while.

Also, I get the WUDFRd failed to load error in Event Viewer, even when the startup is perfectly normal, with no hanging. So perhaps that error is nothing to do with my PC hanging for 30-45" at startup??

(Just tried a boot using msconfig - startup items unchecked. The PC started normally. Went back to normal config, and the PC still starts up properly. Which I why this stuff is often so hard to troubleshoot - nothing's consistent!).

 

[martinlest]

A supplementary question, relevant to my trying to get to the bottom of what's going on here!

Help interpreting a boot trace please

 

[Layback Bear]

martinlest could you post a couple of pictures for us to take a look at.

Examples.






Please use this tutorial by Brink to post the pictures.

Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Help Forums

Jack

 

[martinlest]

Gladly, but could you kindly elaborate on what steps/pictures would now be helpful? I have already run msconfig with no startup items (I unchecked 'Load Startup Items'), but the delay was still there.

Thanks.

 

[Layback Bear]

It would be helpful to me because I will be able to see what is and what is not checked.

Of course you don't have to post the pictures if you don't want to.
It was just a request from me to you.

Jack

 

[martinlest]

Of course you don't have to post the pictures if you don't want to.

?! I said I'd 'gladly' post screen shots but just asked for more details as to what you would need.. Why would you reply like that?? I can't see any way that my reply was open to misinterpretation and such an odd answer.

Forget it then, if you prefer. Thanks anyway.

 

[Layback Bear]

I have no idea what got your feather all fluffed up, but so be it.

Jack

 

[johnhoh]

couple ideas here, was just checking online regarding machines that boot normally on a reboot but have issues on a cold boot, came up with these:

- change your motherboard battery. If its weak or dead it won't matter on a reboot because it does not come into play but on a cold boot it does.
- reflash your bios in case it is corrupted, same principle as previous point
- one guy fixed his issue by reflashing his video card bios
- two guys had this issue and later determined their hard drive was going bad. I would not expect this to be your issue since you are on SSDs and they were on spinning drives.

anyway, you are on the right track by doing boot logging in various environments

 

[martinlest]

Thanks - I'll have a look at those.

 

[martinlest]

I don't think the CMOS battery is a problem, as I get an F1 prompt at bootup if that is the case. I'll leave flashing BIOS etc. for now, as things can go wrong and I am not at the stage yet where I want to risk it

The freeze/hang does in fact occur on reboot sometimes. I eliminated the All_CPU gadget from startup, but that didn't help.

I notice some odd things - for instance, batch files (.bat) that I run at statup (via startup folder) all seem to run immediately, but the one vbs script there doesn't run until the freeze-up clears itself.

It's really hard to know what to make of this! maybe there are some Windows updates I need to install - though that sometimes introduces fresh problems! (I wouldn't be surprised if it's a Windows upadte that has caused this issue all of a sudden. I never had this two or three weeks ago).