Force an error log?

Kalmah

Diamond Member
Oct 2, 2003
3,692
1
76
This computer keeps rebooting while playing battlefield 2. It happens often in other games as well. I turned off the auto-reboot so I could see the blue-screen errors. So far I've gotten a 'page fault in non-paged area' error and all other errors don't give me any info.. it just says 'your computer needs to reboot to avoid damage... bla bla'

I ran a memory tester and turned up no errors. Dxdiag looks ok. All drivers are up to date.

I get no error reports in the system logs. Is their a way to force one or something? Does battlefield2 have its own error logs? (I havn't looked, just thought of it. Will do that after this post)

I think my computer problems started about year ago when lighting struck it. (fried my onboard ethernet... and who knows what else) Actually I think it surged the dsl modem and probably just toasted the jack. (dsl modem and computer speakers fried)
I'm guessing I have some faulty hardware or something do to it. Just need to figure out what it is and I don't have spare components to switch out.

Other than the random blue screen crashes the computer works fine.

 

Lord Evermore

Diamond Member
Oct 10, 1999
9,558
0
76
If the system crashes hard, then there's no chance for anything to write a log. Even on servers, the best you'll get is after a reboot, an event saying "the previous reboot was unexpected".

You can set the system to do a full memory dump, and then attempt to analyze the dump file, but that's not exactly easy. By default you should be at least getting a small memory dump where you could at least find out what file is crashing it.

Do a chkdsk of the hard drive, use the /r option, you'll probably have to reboot to let it happen.

If you have two memory modules, and your system will run with only one, see if you get the problem with only one module installed. Even though memtest said they're good, it's still possible one is causing your problem, if it's intermittent. Even just reseating the modules could fix it.

As described here, the error you saw indicates that the system tried to read a memory address that was invalid. It could be the main memory, your video card memory, or even the CPU cache memory, and other problems could also cause it (since hardware is usually assigned its own memory addresses as well).

Given that it started after a lightning strike which you KNOW damaged part of the computer, it seems certain that something else was damaged. You may be using the computer slightly differently now, so that the failure is more pronounced and encountered more often. Your only real options are going to be to send it to someone for testing, or get some spare components. I would bet your mainboard was damaged, possibly the memory. However since the memory tested okay, it could well have been some other item that you can't easily test.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Originally posted by: Kalmah
This computer keeps rebooting while playing battlefield 2. It happens often in other games as well. I turned off the auto-reboot so I could see the blue-screen errors. So far I've gotten a 'page fault in non-paged area' error and all other errors don't give me any info.. it just says 'your computer needs to reboot to avoid damage... bla bla'

I ran a memory tester and turned up no errors. Dxdiag looks ok. All drivers are up to date.

I get no error reports in the system logs. Is their a way to force one or something? Does battlefield2 have its own error logs? (I havn't looked, just thought of it. Will do that after this post)

I think my computer problems started about year ago when lighting struck it. (fried my onboard ethernet... and who knows what else) Actually I think it surged the dsl modem and probably just toasted the jack. (dsl modem and computer speakers fried)
I'm guessing I have some faulty hardware or something do to it. Just need to figure out what it is and I don't have spare components to switch out.

Other than the random blue screen crashes the computer works fine.

Do you have dump files in c:\windows\minidump? If so, analyze those, and that should tell you why the machine crashed.