itry to open this controll config but keep got this error that config.exe has stopped working.. Problem signature: Problem Event Name: BEX Application Name: config.exe Application Version: 0.0.0.0 Application Timestamp: 4918717c Fault Module Name: config.exe Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4918717c Exception Offset: 00001ec5 Exception Code: c0000417 Exception Data: 00000000 OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 18441 Additional Information 1: bace Additional Information 2: baceddf1a91e73e9df012b4c6ad4da72 Additional Information 3: ffbe Additional Information 4: ffbe6cbb4d0bb13108cb4b6aa1b596f8 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt how to slove the problem??

anyone out there can help??? my vista com can open.. but window 7 cant open sobb

I don't have a config.exe. What does the program? The WER dialog shows BEX, so you have an issue with the NX Bit (http://en.wikipedia.org/wiki/NX_bit#Microsoft_Windows). Try to exclude the program from DEP: http://vlaurie.com/computers2/Articles/dep.htm André"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

I don't have a config.exe. What does the program? The WER dialog shows BEX, so you have an issue with the NX Bit (http://en.wikipedia.org/wiki/NX_bit#Microsoft_Windows). Try to exclude the program from DEP: http://vlaurie.com/computers2/Articles/dep.htm André thx problem slove after restarted my com haha thx anyway:) "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

BEX refers to Buffer Overflow Exception. For more details on BEX, please refer to this article: Data Execution Prevention You can try the suggestions provided by Andre.Ziegler. Also, access Clean Boot to check the issue. If the issue disappears in the Clean Boot environment, you can continue to narrow down which entry is causing the issue. If the issue persists, could you please let us know the exact name of "controll config"?