Classic Shell: Forum

I've been using the laptop from Acer (see signature) and AMD processor is a problem with classic-shell version 4.0.2

If I install classic-shell it works flawlessly. I drive the Laptop down and start again, the error message:

"Attempted switch from DPC" with further explanation that an error at shutdown has occurred.

Windows 8.1 Prof. then repaired the PC and makes reboot.

The classic-shell I can then use as normal. Go down the next
comes the same procedure with the same error.

What is the cause of the error?

It happens ONLY at the laptop with the AMD processor.

In my desktop PC with an Intel processor I have no problems,
as does classic-shell version 4.0.2 with no problem.

_________________
Acer Aspire Laptop Series 5100, Typ: BL51 - 5105AWLMi, AMP-CPU Athlon64 X2=1,7GHz, Windows 8.1 Prof.

Try uninstalling Classic Shell temporarily from Programs and Features and see if the error goes away. What leads you to believe the error message is caused by Classic Shell?

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

This error appears to be caused by a driver. Check if you installed any new drivers recently.

Is not a Driver Problem... "Driver" is too general, what should it be for drivers? which is not correct?

I have long-term tests made ​​with sound. Graphics and other drivers.
All leif live error.

Just as I have the classic-shell 3.6.x or 4.0.2 version installed and the Laptop
've driven down, came this listed here Error message when you next start.

Let me know what drivers because even them work correctly?

_________________
Acer Aspire Laptop Series 5100, Typ: BL51 - 5105AWLMi, AMP-CPU Athlon64 X2=1,7GHz, Windows 8.1 Prof.

Can you please try uninstalling Classic Shell for troubleshooting temporarily to see if the error messages stops happening? "It started happening after installing Classic Shell" isn't a 100% reliable way to determine the cause. Classic Shell is just a regular application - it doesn't modify the system that ways that can cause a blue screen error. Check the Event Log (System Log in particular) or use NirSoft's BlueScreenView if there's a dump the OS created when it bug checked. This is a more serious kernel related error caused either by faulty hardware or drivers - not something at the shell/user mode level.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.