WSOD on administration pages Here are the facts:


Made a clean install of Drupal 6.20
Installed and enabled Admin Menu module


From this point on I can't access any admin/* page however I can access to both node/* and user/*...

PHP log:

No entries


Apache error log:

No entries


Apache access log: 

127.0.0.1 - - [10/Mar/2011:16:22:16 +0000] "GET /drupal_testes/ HTTP/1.0" 200 5771
127.0.0.1 - - [10/Mar/2011:16:22:14 +0000] "GET /drupal_testes/admin HTTP/1.1" 200 -


DB table watchdog:

Nothing serious... 


And that's all, for a single access to /drupal_testes/admin...
Disabling admin_menu (at the system table) does work. Also, as a side note, when I go to admin/build/modules and try to enable Admin Menu again the page will take forever to load and end in a WSOD.
After that if I go to drupal_testes/node the admin_menu is active and working, except for the admin/* pages.   

I'm aware of WSOD Walkthrough but none of the reasons seems to apply this case..
Any idea why can this be happening?  



Edit #4  


Exactly the same behaviour when installing Token  


Edit #5


Installing CCK, which in theory is much heavier than Token or Admin Menu, presents no problems.
Flushing the cache_* tables changes nothing.
Increasing php.ini memory_limit didn't make any difference...




Although the problem is solved by disabling the offending modules, the goal is to have them active and working properly...
If you just started a new site / doesn't contain any data yet as you seem to indicate in your question, it may be faster to reinstall Drupal than search for the source of the WSOD.



Otherwise, you could have a look in the database directly:


first, check the watchdog table: it may have error messages that don't show up in Apache and PHP logs
then, empty the caches by truncating every table named cache_something
then if you're sure this module is the one that caused the problem, you can edit the list of enabled modules in table system: find the module in the list and change its status to "0"


But if you make any modification directly in the database, make sure to save a backup first, just in case ;-)