PROBLEM memory
#1
Scooby Regular
Thread Starter
Join Date: Feb 2002
Location: Lurkin Somewhere
Posts: 7,951
Likes: 0
Received 0 Likes
on
0 Posts
the instruction at "0x004a87dd" referenced memory @ "0x00000000". The memory could not be "read".
ok to terminate
cancel to debug
hmmmmmmmmmmm?
ok to terminate
cancel to debug
hmmmmmmmmmmm?
Trending Topics
#12
Scooby Regular
Thread Starter
Join Date: Feb 2002
Location: Lurkin Somewhere
Posts: 7,951
Likes: 0
Received 0 Likes
on
0 Posts
loading exe generally, when i was loading Half life, Colin Mcrae also noticing when playing UR that my musics going all juddery and so is the screen!
Which it could handle before
Si
Which it could handle before
Si
#15
Get a dependancy walker - Sysinternals do a free download or you could install your stolen copy of VS.NET.
When it crashes again Find out which module has crashed, and which application it belongs to (with the dependancy walker).
Uninstall and then reinstall said application, or if it is some dodgy 3rd party stuff, don't reinstall it.
When it crashes again Find out which module has crashed, and which application it belongs to (with the dependancy walker).
Uninstall and then reinstall said application, or if it is some dodgy 3rd party stuff, don't reinstall it.
#20
You can use this handy app - total overkill but I am sure you can cope
It tells you what is doing what on your system, so you can find out which application is using the dll that crashed (if it was indeed a dll - if it was an exe then it is even easier).
EDIT: mumble friday evening mumble brain fade mumble
[Edited by MrDeference - 4/5/2002 6:03:33 PM]
It tells you what is doing what on your system, so you can find out which application is using the dll that crashed (if it was indeed a dll - if it was an exe then it is even easier).
EDIT: mumble friday evening mumble brain fade mumble
[Edited by MrDeference - 4/5/2002 6:03:33 PM]
Thread
Thread Starter
Forum
Replies
Last Post