Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Data Execution Prevention Error - After SP3 Upgrade

Sep 4, 2010 1:00AM PDT

I have searched everywhere on google for solution on this and hoping forum can help

I just upgraded to XP SP3. My box was virus free and running fine before the upgrade. Now after the upgrade many times after I boot up (or within 30 mins thereafter) I get a popup "Data Execution Prevention". It says Windows Explorer. Close the message then shortly after the desktop crashes

What is causing this and what is the fix? Many thanks!!

Discussion is locked

- Collapse -
BTW, I have XP Home Edition
Sep 4, 2010 1:01AM PDT

BTW, I have XP Home Edition

- Collapse -
Most people
Sep 4, 2010 3:05AM PDT

Most people who have DEP errors have an old/buggy driver.

- Collapse -
Ok
Sep 4, 2010 3:11AM PDT

Thanks for the reply but thats not much direction on how to fix. Anyone else have detailed suggestions on how to fix?

- Collapse -
Actually it is a direction.
Sep 4, 2010 3:52AM PDT

You look at the errors to see if they yield any clue which driver and if the machine is BSOD'ing you look in the event viewer for more clues then you look for updated drivers from the makers of the machine, card or component that is failing.
Bob

- Collapse -
Data Execution Prevention
Sep 4, 2010 6:24AM PDT

You my need to go into safe mode to do this...

Go to SYSTEM PROPERTIES, (right click my computer, go to properties) Then go to advanced, under performance click settings, next click the DATA EXECUTION PREVENTION tab, put a bullet in, Turn on DEP for all programs and services except those I select, then make sure Windows Explorer has a check in box next to it. Now restart your computer...

If that doesn't work go into BIOS and under advanced or something like it, find EXECUTE DISABLE BIT or something like it and disable it. You should be rid of the error. Let me know if you need more detailed information, hope I helped...

- Collapse -
Thanks adm3rd!
Sep 4, 2010 8:37AM PDT

Your post was helpful
I have had people suggest to configure DEP to ignore the error (ie add an exception in DEP config box) but I am hesitant to start adding exceptions in DEP becase doesnt that leave those programs unprotected? I'd rather fix the ROOT cause. Does anyone have any inisght into what would be causing this to suddenly happen on SP3 but not before when I was on SP2? I'd like to identify and fix root cause.

Also, in order to add an exception I have to switch from DEP on "essential windows programs and services only" to "ALL programs and services except...". Isn't the latter a much larger list of programs/services and could cause even more DEP errors, which would be ironic given orginal problem.

Whats is root cause causing this after the SP3 upgrade and what is the fix? Many thanks!!

- Collapse -
Re: Thanks adm3rd
Sep 4, 2010 9:37AM PDT

DEP wasn't even introduced until XP Sp2, there were some changes in service pack 3 that are contributing to your issue but I will tell you that this is one of the first feature that most computer enthusiasts and overclockers disable. It is more trouble than it is worth, I have had all processor features disabled on my computers for years with no issues. Use good Virus Protection, I recommend Bitdefender, don't sweat it. Make your life easier and just disable it...

- Collapse -
My system...
Sep 4, 2010 9:51AM PDT