Task scheduler engine not working

[shuggie]

Turned on laptop Gateway MT6722b this morning, would not start, pop up said Windows Explorer not working, another said, Task scheduler engine has stopped working.

Windows Vista home premiun 32-bit

2007 year

Shut down nornal last night

[KenB]

Hi and welcome to ExTS

 

Can you boot up at all and get to the desktop ?

 

If not .......

 

Safe Mode.

Switch on > constantly tap F8 about once per second.

From the list of options select Safe Mode

 

Does it boot up with this ?

[shuggie]

Task scheduler engine not working

 

Thank you, I have tried your suggestion, Started in safe mode, it started to load Windows Files, then pop up stating," Application has failed to start because SHELL32.dll was not found, reinstalling the application may fix this problem". When i removed the pop up it tries to start up, then just a black screen, with safe mode in each corner and Microsoft Windows (build 6002:servive pack 2) to top of screen.

Any other suggestions I could try, every had been ok with the laptop untill yesterday morning when this happened, it had closed down the night before normally.

[KenB]

Hi

 

Go back to the Advanced Startup Options ( F8 ) and select "Safe Mode with Command Prompt"

At the prompt type in ...

rstrui.exe

 

This will start System Restore.

 

Select a date that is just before the start of your problems.

This will restore your system to the system settings on that specific date.

Your files and data will be fine.

[BenchZowner]

If I were you, running Memtest86+ would be my very first move ( what you're describing sounds like a malfunctioning memory DIMM/s ).

Can you follow the on-site instructions ( http://www.memtest.org/ ) to create a bootable USB/CD/DVD/Floppy to run memtest86+ from ?

 

Once you're in memtest86+ press C -> 1 -> 3 -> 5 -> enter -> 0 to make it run unlimited loops of test #5.

If any red lines with errors appear in the middle to bottom part of the screen you have a memory related problem ( dieing memory, malfunctioning memory, improperly set up memory settings in the BIOS, or even (very rarely) a malfunctioning or dieing memory controller if your CPU has an integrated memory controller like the Core 2 Duo series have for example )

[shuggie]

Thanks again, my son-in-law came yesterday while i was out, took my laptop away and left it in to be repaired, so i was unable to try your suggestion.

Thanks Shuggie