Tech Support Forum - View Single Post

hellraiser357 · 10-08-2005, 05:40 AM

Before the BSOD's, we had a game on the PC that would cause it to reboot while playing. We figured it was that particular game, because it would only reboot while playing that game. So, we uninstalled it, and the BSOD's started. My dad say's it did okay until he got online to check his e-mail today, and bam it hit again. I am going to run a RAM check on it, and see if it comes up with any thing.

In the KB article I linked to, there is metion of a file called ntstatus.h that is supposed to list the drivers and where they are located in memory by hex addy. This is apparently how the BSOD error codes are supposed to be translated. Since 2000 is NT based, should I be able to locate this file and how?

10-08-2005, 05:40 AM	#3 (permalink)
hellraiser357 Registered User Join Date: Aug 2004 Location: Texas Posts: 66 OS: Win2000	Before the BSOD's, we had a game on the PC that would cause it to reboot while playing. We figured it was that particular game, because it would only reboot while playing that game. So, we uninstalled it, and the BSOD's started. My dad say's it did okay until he got online to check his e-mail today, and bam it hit again. I am going to run a RAM check on it, and see if it comes up with any thing. In the KB article I linked to, there is metion of a file called ntstatus.h that is supposed to list the drivers and where they are located in memory by hex addy. This is apparently how the BSOD error codes are supposed to be translated. Since 2000 is NT based, should I be able to locate this file and how?