Log in

01 September 2012 @ 10:24 pm
Gaming Crashes  
I've been seeing a a lot of BSODs in the last couple of weeks. Most typically when I'm trying to game. For the most part WWindows failed to log these events, leaving me to writing down their codes. Fior these, if anyone can tell me what they mean then that would be great. I get mixed answers from google such as "page fault in non-paged area" and "bad_pool_header"

These four happened in the last 7 days while trying to play STO or Skyrim.
1) 0x00000050
2) 0x0000007F
3) 0x00000024
4) 0x0000000A (it mentioned WIN32k.sys)

This is one of the only two reports that Windows actually logged (It was labled as a Bad_Pool_Header and is as old as March 1st):
*** STOP: 0x00000019 (0x00000022, 0x00000000, 0x00000000, 0x00000000)
*** ntkrnlpa.exe - Address 0x82cb0e80 base at 0x82c1d000 DateStamp 0x4ea76eb4

This one is the only other crash that windows logged and as such is the only other detailed report. This one and the four above happened in the last 24 hours.

*** STOP: 0x00000124 (0x00000000, 0x8542101c, 0xb64a4000, 0x00000135)
*** halmacpi.dll - Address 0x8222dfcd base at 0x8221f000 DateStamp 0x4ce788d2

I recognize that both ntkrnlpa.exe and halmacpi.sys are both core system files. So these two get the most attention. I also notice that Bad_Pool_Header has something to do with RAM. Same thing with "page fault in non paged area". But that last error with halmacpi doesn't have a bug-check string so I don't know what it is except its code being more or less a hardware fault.

Anyone know anything more than I do about these? Getting tired of my games freezing up or making my glory rig go into BSOD. Making this thing turn from a gaming rig into a "sit and net surf" rig. >_<

"SFC /scannow" says nothing is wrong. Defrag says nothing is fragmented above 6%. And dskchk shows no errors in the hard drive. So its either my Video Card or RAM or CPU or a combination of the 3.

EDIT: Ran the built-in Driver Verifier. It asked me to reboot. During boot check it did another BSOD.

*** STOP: 0x000000c9 (0x0000023b, 0x923fb37c, 0xa2df2e28, 0x00000000)
*** ASACPI.sys - Address 0x923fb37c base at 0x923fb000 DateStamp 0x411c2d04

It came up to a "DRIVER_VERIFIER_IOMANAGER_VIOLATION" in this case since it happened in a Driver Verifier boot. >_> Checked the file in question and it was "created on" and "modified" on August 8th 2004. That's outright ANCIENT. o_O Think I should replace it with a more current version, don't you?

Edit x2:
Updated ASACPI.sys. The version I had was listed for use in Windows 2000/XP and is notoriously unstable if used in Windows 7. The most recent available version is from 2009, so I used that.
Current Mood: aggravatedaggravated