Forum Home
Press F1
Thread ID: 37093	2003-08-28 08:50:00	Application error - memory could not be "read"	PoWa (203)	Press F1

Post ID	Timestamp	Content	User
171175	2003-08-29 08:14:00	Ok I've turned AGP fastwrites and shadowing on again in the bios, thanks for the enlightenment there fellas. Strangely in the PCco default/ settings for the motherboard it has AGP fast writes disabled - but that might have been more specific to the gf2mx200 card I had in when the compuer was purchased. I have since also removed the newer nvidia drivers (not completely because Detonator-RIP wouldn't work and was giving the same error when I tried to run it. - Detonator RIP removes every last trace of the old drivers). Anyway I've installed the older 44.03 drivers and they seem to be going a bit better. What the heck could be wrong with the newer ones? I can still get the memory error if I try and open a divx file in Media Player, and another divx file in winamp? -whys that?	PoWa (203)
171176	2003-08-30 05:14:00	I think I've fixed the problem guys!! Keep this in mind for future reference :) I got an idea from a site that the error might be causes by a corrupt profile, so I created a new profile, then copied all my settings from the old profile into the new one following this advice here (support.microsoft.com). Then I booted into the new profile and everything works great as it used to! I even tested it by opening up 5 different DivX's and in different players incl winamp and they were all playing their thing without crashing. I can actually play 4 divx's at once and have them all on screen, quite cool! After 4 though the system starts to crawl :) Thanks for your help guys - and lets hope the problem is fixed - if its not then I'll be posting back ;)	PoWa (203)
1 2