Problem with a specific game.

Hey, this may be related to the other stuff that I brought up before, but just in case it is a separate subject on its own, here is the jist of the problem.

With the only game program I use online play, game crashes have been occuring. I've posted this stuff on the official web site, but no help has come yet to help me. The usual thing happens, the game crashes, the window closes itself, an error page then appears. Its usually a general protection fault. But on rare occasions, an assertion failed appears as the problem. The crashes happen online when I go to a game server online. The crashes have been happening more and more often.

Here are some crash reports. If you can tell what the problem is, or how to fix it, that would be perfect.

UT2004 Build UT2004_Build_[2005-11-23_16.22]

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 1800 MHz with 1023MB RAM
Video: RADEON 9600 SERIES (6575)

Assertion failed: ProjectorInfo->Projector [File:.\UnRenderVisibility.cpp] [Line: 1642]

History: RenderLevel <- DM-Surf[SXDT]nv.myLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine:raw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 10910191 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free


OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 1800 MHz with 1023MB RAM
Video: RADEON 9600 SERIES (6575)

General protection fault!

History: FDynamicActor::Update <- AActor::UpdateRenderData <- UObject::GetFullName <- IterateOverActors <- RenderLevel <- DM-[UI]-TheEZKILLINGMAP-JINK_V2.myLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine:raw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- Level 攀¦昀¦最¦栀¦椀¦樀¦欀¦氀¦洀¦渀¦漀¦瀀¦焀¦爀¦쐀猀¦琀¦甀¦瘀¦眀¦砀¦礀¦稀¦笀¦簀¦紀¦縀¦缀¦耀¦脀¦舀¦茀¦萀¦蔀¦蘀¦蜀¦蠀¦褀¦言¦謀¦谀¦贀¦踀¦輀¦退¦鄀¦鈀¦錀¦鐀¦销¦鸀‡阀¦需¦頀¦餀¦騀¦鬀¦鰀¦鴀¦鸀¦鼀¦ꀀ¦ꄀ¦ꈀ¦ꌀ¦ꐀ¦ꔀ¦ꘀ¦꜀¦ꠀ¦꤀¦ꨀ¦꬀¦가¦관¦글¦꼀¦뀀¦넀¦눀¦대¦됀¦딀¦伀Œ豈H䰀*䀀*稀_똀¦뜀¦렀¦뤀¦먀¦묀¦밀¦봀¦븀¦뼀¦쀀¦섀¦숀¦ <- UpdateWorld <- MainLoop <- FMallocWindows::Free <- FMallocWindows::Realloc <- 10910191 0 FArray <- FArray::Realloc <- 0*2 <- FMallocWindows::Free

 

Hi, FK.

Yes, such issues might be related to your hardware issues and/or your malware issues.

I suggest you first address and take care of your hardware issues (as noahdfear has already suggested a couple times).

Then I suggest you take care of your malware issues after you resolve all your hardware issues.

If you still get similar issues related to your game(s) after you have resolved your hardware issues and malware issues, then that would be the time to tackle your game issue(s).

 

Just some thoughts, answer if you can.

Hey, I was wondering, I've noticed that the only time that the BSOD appears any more is when I try to play an online game normally, or run Spybot S&D scan. I've wondered what the connection those two programs would have, and after looking at the task manager, I Think I might have a lead. The category that states CPU, with numbers associated with programs that are running. Now, the BSOD has not done so for a while with serfing the internet, which I think is because of noahdfear's advice on certain programs to remove. It has though happened when my O.S. has tried to load up, and at times when I logged in. Anyways, when running either a game program, or Spybot, they both would run normally for a little while, and then the BSOD would hit it. Various unique statements were made in this BSOD image, but I've only taken note, and posted that which is unique and uncommon. I should also add, that when playing a game online, and trying to download maps, it sometimes has a blank BSOD. I'm not sure if this information narrows down the culpurate of my pc problems, but it wouldn't hurt to post the information of the possibility. If you think of some sort of sollution towards my problem based on the information I have posted, please state any advice you might have that I can do to remedy my situation.

 

Hey, sorry I haven't been around.

Hey, as for those whom have been keeping an eye on things here, I've been busy, and this pc is being a persistant pain. Anyways, I've tried out the 450W PSU at my school like I said, but the BSOD happened at the same thing that happened last time. I noticed my pc's drives got wicked hot, so I've left it alone for a while. I know, I should post this particular part of info on the hardware thread, but, I'm tired, its almost morning, and I'm REALLY, tired. So, anyways, after doing the usual struggle of turning my pc on, I logged in, and went back to trying to figure the problem out. I followed the instructions. I downloaded the debugger, but I'm not sure if I'm using it right. I did a scan by opening up the program, choosing file, choosing executable files, and then choosing dumpchk.exe. This is the results.


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: "C:\Program Files\Debugging Tools for Windows\dumpchk.exe "
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
ModLoad: 01000000 01006000 dumpchk.exe
ModLoad: 7c900000 7c9b0000 ntdll.dll
ModLoad: 7c800000 7c8f5000 C:\WINDOWS\system32\kernel32.dll
ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 02000000 02339000 C:\Program Files\Debugging Tools for Windows\dbgeng.dll
ModLoad: 03000000 03115000 C:\Program Files\Debugging Tools for Windows\dbghelp.dll
ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f02000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.dll
(8f8.8a0): Break instruction exception - code 80000003 (first chance)
eax=00181eb4 ebx=7ffd9000 ecx=00000004 edx=00000010 esi=00181f48 edi=00181eb4
eip=7c901230 esp=0006fb20 ebp=0006fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!DbgBreakPoint:
7c901230 cc int 3

 

F.K.,

When you use DebugWiz according to the instructions Arie linked above, use the "Browse..." button in DebugWiz to locate the dump file. Then click the "Generate Log" button. (Click on the attached thumbnail below for details.)

I just had a Blue Screen of Death (BSOD) system crash this evening and the MEMORY.DMP file was located in C:\WINDOWS\ so you might want to check there as well.

If choosing a Mini-dump file, then the format of the file name will be Minixxxxxx-yy.dmp where the xxxxxx represents the date of the crash (in MonthDayYear format) and the yy represents the crash count for that day.

NOTE: You should be connected to the Internet when you use DebugWiz to generate a dump log (so the proper "symbols" can be retrieved from Microsoft as necessary).

 

here's one.

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032107-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers

 

here's another one.

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032107-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Mar 21 09:37:44.781 2007 (GMT-5)
System Uptime: 0 days 2:55:54.346
Loading Kernel Symbols
............................................................................................................................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck EA, {85af9518, 86eac5a8, 870523a0, 1}

ATI Rev3 buffer
Bucket = ATI_CP_2D


Probably caused by : ati2cqag.dll ( ati2cqag!AsicR6::readRetiredTimestamp+d )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 85af9518, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 86eac5a8, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 870523a0, Pointer to offending driver name.
Arg4: 00000001, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.

Debugging Details:
------------------

ATI Rev3 buffer
Bucket = ATI_CP_2D



FAULTING_THREAD: 85af9518

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 2

BUGCHECK_STR: 0xEA

PROCESS_NAME: FEAR.exe

LAST_CONTROL_TRANSFER: from bfa3254a to bfa162dd

STACK_TEXT:
b8705194 bfa3254a b8705230 e28001c0 e296e444 ati2cqag!AsicR6::readRetiredTimestamp+0xd
b87051a8 bfa370a3 e2949410 b8705210 00000000 ati2cqag!QS_PRIVATE::cleanTSnodes+0x2a
b8705200 bf9fa20f e2952100 b8705200 00000000 ati2cqag!uQSAllocList+0x233
b8705210 bfa56020 e5364200 b8705230 00001000 ati2dvag!vUpdateCursorPositionMVPU_r520+0x95
b870526c bfa4e910 b8705790 0000f044 b87052e0 atikvmag!QsAllocCmdBuff+0x80
b8705364 bfa4f5f1 00000005 00000000 00055580 atikvmag!bHostDataBltCopy+0x680
b87053f0 bfa5300b b8705790 00000005 00000000 atikvmag!BcCopyBuffer+0x611
b8705428 bfa5333f b8705790 e2977e90 e29975f0 atikvmag!CiuUpdateResourcePointers+0x4b
b8705458 bfa534c6 b8705790 e2977f24 e2977f20 atikvmag!CiuUpdateResourcePointers+0x37f
b8705480 bfa53609 b8705790 e2977f24 e2977f20 atikvmag!CiuUpdateResourcePointers+0x506
b87054d4 bfa537cc b8705790 e29975f0 00000080 atikvmag!CiuUpdateResourcePointers+0x649
b87054e4 bfa539b6 e29975f0 e29964f0 e294b050 atikvmag!CiuUpdateResourcePointers+0x80c
b8705708 bfa5840f b8705790 e29964f0 00000052 atikvmag!CiuAllocatePhysicalMemoryList+0x176
b8705770 bfa5fd25 b8705790 b87057c8 b8705808 atikvmag!ProcessVirtualCommandBuffer+0x35f
b87057a4 bfa94b4c e5364200 00000000 b87057c8 atikvmag!VCAMSubmitCommandBuffer+0xb5
b870584c bfb2eb78 b8705a60 00000000 e6789948 ati3duag!cmdBufSubmit+0xbc
b87058dc bfb023ce 00000019 00000000 00000400 ati3duag!r300HostDataBlt+0x288
b870595c bfa8b939 00000400 00000040 00000000 ati3duag!r300HostBlt+0x29e
b87059c8 bfb75964 e6789948 e5f2d018 e4ee5010 ati3duag!ddHwlHostBlt+0x89
b8705afc bfb850d3 e4ee5010 e5f2d018 e6789948 ati3duag!d3dTexBlt+0x644
b8705b28 bfb7214b 00e20068 00e20070 00000000 ati3duag!d3dBltTexture+0x63
b8705b44 bfb73629 e4ee5010 00e1cde0 b8705ce4 ati3duag!d3dDp2TexBlt+0x2b
b8705bf8 bfb73dba e4ee5010 b8705c20 00e20dd8 ati3duag!d3dPrim2ProcCmdBuf+0xdb9
b8705c2c bf9602dd b8705ce4 00000020 00003749 ati3duag!atiD3dDrawPrimitive2+0xda
b8705c68 bf9c2663 b8705ce4 b8705d64 0022ed74 win32k!WatchdogDdDrawPrimitives2+0x4e
b8705d40 804dd99f 1c400002 03400009 00dbe8e0 dxg!DxD3dDrawPrimitives2+0x1b9
b8705d40 7c90eb94 1c400002 03400009 00dbe8e0 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0022ed84 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .thread 0xffffffff85af9518 ; kb

FOLLOWUP_IP:
ati2cqag!AsicR6::readRetiredTimestamp+d
bfa162dd 7536 jne ati2cqag!AsicR6::readRetiredTimestamp+0x45 (bfa16315)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ati2cqag!AsicR6::readRetiredTimestamp+d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati2cqag

IMAGE_NAME: ati2cqag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4328d577

FAILURE_BUCKET_ID: 0xEA_IMAGE_ati2cqag.dll_DATE_2005_09_14_ATI_CP_2D

BUCKET_ID: 0xEA_IMAGE_ati2cqag.dll_DATE_2005_09_14_ATI_CP_2D

Followup: MachineOwner
---------

eax=e28001c0 ebx=00000080 ecx=e2800000 edx=e114b94c esi=e28001c0 edi=b8705230
eip=bfa162dd esp=b8705198 ebp=e296e444 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000246
ati2cqag!AsicR6::readRetiredTimestamp+0xd:
bfa162dd 7536 jne ati2cqag!AsicR6::readRetiredTimestamp+0x45 (bfa16315) [br=0]
ChildEBP RetAddr Args to Child
b8705194 bfa3254a b8705230 e28001c0 e296e444 ati2cqag!AsicR6::readRetiredTimestamp+0xd (FPO: [0,0,0])
b87051a8 bfa370a3 e2949410 b8705210 00000000 ati2cqag!QS_PRIVATE::cleanTSnodes+0x2a (FPO: [Uses EBP] [0,0,0])
b8705200 bf9fa20f e2952100 b8705200 00000000 ati2cqag!uQSAllocList+0x233 (FPO: [Uses EBP] [2,17,0])
b8705210 bfa56020 e5364200 b8705230 00001000 ati2dvag!vUpdateCursorPositionMVPU_r520+0x95 (FPO: [Non-Fpo])
b870526c bfa4e910 b8705790 0000f044 b87052e0 atikvmag!QsAllocCmdBuff+0x80 (FPO: [Uses EBP] [4,16,0])
b8705364 bfa4f5f1 00000005 00000000 00055580 atikvmag!bHostDataBltCopy+0x680 (FPO: [Uses EBP] [8,53,0])
b87053f0 bfa5300b b8705790 00000005 00000000 atikvmag!BcCopyBuffer+0x611 (FPO: [Uses EBP] [10,22,0])
b8705428 bfa5333f b8705790 e2977e90 e29975f0 atikvmag!CiuUpdateResourcePointers+0x4b (FPO: [3,0,0])
b8705458 bfa534c6 b8705790 e2977f24 e2977f20 atikvmag!CiuUpdateResourcePointers+0x37f (FPO: [Uses EBP] [5,4,0])
b8705480 bfa53609 b8705790 e2977f24 e2977f20 atikvmag!CiuUpdateResourcePointers+0x506 (FPO: [Uses EBP] [4,0,0])
b87054d4 bfa537cc b8705790 e29975f0 00000080 atikvmag!CiuUpdateResourcePointers+0x649 (FPO: [Uses EBP] [2,12,0])
b87054e4 bfa539b6 e29975f0 e29964f0 e294b050 atikvmag!CiuUpdateResourcePointers+0x80c (FPO: [Uses EBP] [1,0,0])
b8705708 bfa5840f b8705790 e29964f0 00000052 atikvmag!CiuAllocatePhysicalMemoryList+0x176 (FPO: [Uses EBP] [4,131,0])
b8705770 bfa5fd25 b8705790 b87057c8 b8705808 atikvmag!ProcessVirtualCommandBuffer+0x35f (FPO: [Non-Fpo])
b87057a4 bfa94b4c e5364200 00000000 b87057c8 atikvmag!VCAMSubmitCommandBuffer+0xb5 (FPO: [4,6,0])
b870584c bfb2eb78 b8705a60 00000000 e6789948 ati3duag!cmdBufSubmit+0xbc (FPO: [Uses EBP] [0,34,0])
b87058dc bfb023ce 00000019 00000000 00000400 ati3duag!r300HostDataBlt+0x288 (FPO: [Uses EBP] [8,32,0])
b870595c bfa8b939 00000400 00000040 00000000 ati3duag!r300HostBlt+0x29e (FPO: [Uses EBP] [0,19,0])
b87059c8 bfb75964 e6789948 e5f2d018 e4ee5010 ati3duag!ddHwlHostBlt+0x89 (FPO: [Uses EBP] [0,23,0])
b8705afc bfb850d3 e4ee5010 e5f2d018 e6789948 ati3duag!d3dTexBlt+0x644 (FPO: [Uses EBP] [7,72,4])
start end module name
804d7000 806fd000 nt ntkrnlmp.exe Tue Dec 19 09:14:53 2006 (4587F3DD)
806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
b7654000 b767e180 kmixer kmixer.sys Wed Jun 14 04:47:45 2006 (448FCD31)
b7f10000 b7f32080 RDPWD RDPWD.SYS Thu Jun 09 19:52:39 2005 (42A8D647)
b7f5b000 b7f6cf20 NAVENG NAVENG.Sys Mon Jan 22 20:05:17 2007 (45B55F4D)
b7f6d000 b803b740 NavEx15 NavEx15.Sys Mon Jan 22 20:39:38 2007 (45B5675A)
b803c000 b8094000 SAVRT SAVRT.SYS Mon Dec 19 23:24:48 2005 (43A78790)
b8ade000 b8af2400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
b8b1b000 b8b6c480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
b8c85000 b8cb1400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
b8cda000 b8ce8d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
b92be000 b92c1280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
b9342000 b9359480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
b935a000 b937d000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
b95ab000 b95c8000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Wed Jan 31 19:54:39 2007 (45C13A4F)
b95e8000 b95ea900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
b95f0000 b9651000 eeCtrl eeCtrl.sys Wed Jan 31 19:54:39 2007 (45C13A4F)
b9651000 b96bfa00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
b96c0000 b96eaa00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
b96eb000 b96ff000 SAVRTPEL SAVRTPEL.SYS Mon Dec 19 23:24:50 2005 (43A78792)
b96ff000 b9761000 SPBBCDrv SPBBCDrv.sys Thu Nov 03 23:37:18 2005 (436AD76E)
b9761000 b9782d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
b9783000 b97aac00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
b97ab000 b97dc000 symidsco symidsco.sys Fri Jan 12 18:29:35 2007 (45A819DF)
b981c000 b9820500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
b984e000 b9877000 SYMFW SYMFW.SYS Mon Aug 07 18:52:33 2006 (44D7C431)
b9877000 b98d0aa0 CamDrL21 CamDrL21.sys Sat Jun 08 14:38:00 2002 (3D024F08)
b997b000 b999e000 SYMEVENT SYMEVENT.SYS Fri Dec 15 19:30:34 2006 (45833E2A)
b9a3e000 b9a5ef00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
bac44000 bac7f000 SYMTDI SYMTDI.SYS Mon Aug 07 18:52:32 2006 (44D7C430)
bac7f000 bacd6d80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
bacd7000 bace9400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)

 

Here's the one that mailman said to look in.

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Could not open dump file [C:\WINDOWS\MEMORY.DMP], NTSTATUS 0xC000011E
"An attempt was made to map a file of size zero with the maximum size specified as zero. "

 

That dump file appears rather old (032107 = March 21, 2007).

If possible, please post a dump log for a MOST RECENT system crash dump file.

When using the DebugWiz tool to browse to the C:\WINDOWS\Minidump\ folder, look for dump files that are named as follows.

After using DebugWiz to generate a C:\debuglog.txt file, you should paste the entire contents of that debuglog.txt file into a forum message before you generate another dump log with DebugWiz. (Alternatively, you could rename the debuglog.txt file or copy it to another location on your hard drive before generating another dump log with DebugWiz.)

The DebugWiz tool will overwrite any existing C:\debuglog.txt file when you generate a new dump log.

If possible, whenever you paste the contents of a dump log into a forum post, please tell us details about what you were doing with the computer (and what applications were open) when that crash occurred.

If any of these instructions are not clear, then please let us know what part(s) of the instructions you have difficulty understanding.

 

F.K.,

I just re-read your first post in this thread and it appears you want assistance with your game program crashes instead of system crashes (BSODs). In that case, you should ignore my posts above for the time being.

If you want to generate a dump log for a program crash, then use DebugWiz (immediately after the program crash occurs) to browse to the following location and generate a dump log.

• C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

Reminder: You should be connected to the Internet when you run DebugWiz so the proper "symbols" can be retrieved from Microsoft while generating a dump log.


BTW, I still think you should tackle and resolve all of your hardware issues (in your Hardware forum thread) before trying to fix malware and software issues. Hardware issues are complicated enough without throwing malware and software issues into the mix. If I were in your shoes, I would focus on the hardware forum thread and leave your other threads alone until all of your hardware issues are resolved.

 

Just so its clear, I want to tackle all problems. I just started specific parts in order to clarify to problem, and possibly narrow it down to an area, (such as a gaming program). I'll do as you said, but the most up to date dmp file is today, but that one, along with others, has a problem of being accessed by the dumpwiz. Why?; I don't know why, but I'll try again though.

 

Oh, and I already knew that little trick of moving an file that you want to keep untouched, while knowinga new one will be remade/updated. In addition, the part where you clarified where the .dmp file indicates its date of creation, yeah, I knew that too. Thats why I posted multiple posts of dump files, because the latest one, (in c:windows) does not let me make a file of it, or for that matter, open it up. so, I just kept going around, seeing if it would work with other dump files. One of them did, which is why I posted it.

I've looked in all of the areas specified areas that dmp files should be located. I think my system has them enabled, but I don't know why in the minidump folder, that current BSOD don't happen. I've found one in the windows folder, but its all the way in the back, it has a problem, and every time, it doesn't want to open fully.

 

This is the latest game BSOD crash.

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [G:\UT2004\System\minidump-v3369.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Sat Jan 19 06:58:45.000 2008 (GMT-5)
System Uptime: not available
Process Uptime: 0 days 0:03:28.000
................................................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(8a0.960): Access violation - code c0000005 (first/second chance not available)
eax=22b00000 ebx=00000000 ecx=00000007 edx=7c90eb94 esi=00148128 edi=000008a0
eip=7c90eb94 esp=0012c60c ebp=0012c61c iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200246
ntdll!KiFastSystemCallRet:
7c90eb94 c3 ret
0:000> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify checksum for D3DDrv.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for D3DDrv.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ole32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for user32.dll -
*** WARNING: Unable to verify checksum for ALAudio.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ALAudio.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
UT2004+4485
10904485 8910 mov dword ptr [eax],edx

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
.exr 0xffffffffffffffff
ExceptionAddress: 10904485 (UT2004+0x00004485)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

DEFAULT_BUCKET_ID: NULL_POINTER_READ

PROCESS_NAME: UT2004.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

WRITE_ADDRESS: 00000000

LAST_CONTROL_TRANSFER: from 1010ec66 to 10904485

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012d82c 1010ec66 10910191 1017fe90 ffffffff UT2004+0x4485
0012e1e0 7c358e6b 10918fe0 0012fc9c 00000103 Core!TArray<unsigned short>::~TArray<unsigned short>+0x86
7c34347e 104d8b5d 81eb8b55 000100f9 b9057500 MSVCR71!__FrameUnwindToState+0x6d
7c343492 f13fe851 595dffff 0cc2c95b 66c03300 0x104d8b5d
7c343496 595dffff 0cc2c95b 66c03300 0424548b 0xf13fe851
7c34349a 0cc2c95b 66c03300 0424548b 8b66c3ec 0x595dffff
7c34349e 66c03300 0424548b 8b66c3ec 66042454 0xcc2c95b
7c3434a2 0424548b 8b66c3ec 66042454 8b66c3ed 0x66c03300
7c3434a6 8b66c3ec 66042454 8b66c3ed ed042454 0x424548b
7c3434aa 66042454 8b66c3ed ed042454 66c033c3 0x8b66c3ec
7c3434ae 8b66c3ed ed042454 66c033c3 0424548b 0x66042454
7c3434b2 ed042454 66c033c3 0424548b 0824448a 0x8b66c3ed
7c3434b6 66c033c3 0424548b 0824448a 8b66c3ee 0xed042454
7c3434ba 0424548b 0824448a 8b66c3ee 66042454 0x66c033c3
7c3434be 0824448a 8b66c3ee 66042454 0824448b 0x424548b
7c3434c2 8b66c3ee 66042454 0824448b 66c3ef66 0x824448a
7c3434c6 66042454 0824448b 66c3ef66 0424548b 0x8b66c3ee
7c3434ca 0824448b 66c3ef66 0424548b 0824448b 0x66042454
7c3434ce 66c3ef66 0424548b 0824448b 8b55c3ef 0x824448b
7c3434d2 0424548b 0824448b 8b55c3ef 08ec83ec 0x66c3ef66
7c3434d6 0824448b 8b55c3ef 08ec83ec 55575653 0x424548b
7c3434da 8b55c3ef 08ec83ec 55575653 0c5d8bfc 0x824448b
7c3434de 08ec83ec 55575653 0c5d8bfc f708458b 0x8b55c3ef
7c3434e2 55575653 0c5d8bfc f708458b 00060440 0x8ec83ec
7c3434e6 0c5d8bfc f708458b 00060440 77750000 0x55575653
7c3434ea f708458b 00060440 77750000 8bf84589 0xc5d8bfc
7c3434ee 00060440 77750000 8bf84589 45891045 0xf708458b
7c3434f2 77750000 8bf84589 45891045 f8458dfc 0x60440
7c3434f6 8bf84589 45891045 f8458dfc 8b144389 0x77750000
7c3434fa 45891045 f8458dfc 8b144389 7b8b0c73 0x8bf84589
7c3434fe f8458dfc 8b144389 7b8b0c73 fffe8308 0x45891045
7c343502 8b144389 7b8b0c73 fffe8308 0c8d5674 0xf8458dfc
7c343506 7b8b0c73 fffe8308 0c8d5674 8f7c8376 0x8b144389
7c34350a fffe8308 0c8d5674 8f7c8376 3a740004 0x7b8b0c73
7c34350e 0c8d5674 8f7c8376 3a740004 6b8b5556 0xfffe8308
7c343512 8f7c8376 3a740004 6b8b5556 8f54ff10 0xc8d5674
7c343516 3a740004 6b8b5556 8f54ff10 8b5e5d04 0x8f7c8376
7c34351a 6b8b5556 8f54ff10 8b5e5d04 c00b0c5d 0x3a740004
7c34351e 8f54ff10 8b5e5d04 c00b0c5d 31782874 0x6b8b5556
7c343522 8b5e5d04 c00b0c5d 31782874 53087b8b 0x8f54ff10
7c343526 c00b0c5d 31782874 53087b8b ffefd3e8 0x8b5e5d04
7c34352a 31782874 53087b8b ffefd3e8 04c483ff 0xc00b0c5d
7c34352e 53087b8b ffefd3e8 04c483ff 56106b8b 0x31782874
7c343532 ffefd3e8 04c483ff 56106b8b f008e853 0x53087b8b
7c343536 04c483ff 56106b8b f008e853 c483ffff 0xffefd3e8
7c34353a 56106b8b f008e853 c483ffff 760c8d08 D3DDrv!UD3DRenderDevice::UD3DRenderDevice+0x2582f
7c34353e f008e853 c483ffff 760c8d08 898f048b 0x56106b8b
7c343542 c483ffff 760c8d08 898f048b 54ff0c43 0xf008e853
7c343546 760c8d08 898f048b 54ff0c43 7b8b088f 0xc483ffff
7c34354a 898f048b 54ff0c43 7b8b088f 760c8d08 msvcp60!$$VProc_ImageExportDirectory+0x1bd60
7c34354e 54ff0c43 7b8b088f 760c8d08 eb8f348b 0x898f048b
7c343552 7b8b088f 760c8d08 eb8f348b 0000b8ac 0x54ff0c43
7c343556 760c8d08 eb8f348b 0000b8ac 1ceb0000 0x7b8b088f
7c34355a eb8f348b 0000b8ac 1ceb0000 000001b8 msvcp60!$$VProc_ImageExportDirectory+0x1bd60
7c34355e 00000000 1ceb0000 000001b8 5515eb00 0xeb8f348b


STACK_COMMAND: ~0s; .ecxr ; kb

FAULTING_THREAD: 00000960

PRIMARY_PROBLEM_CLASS: NULL_POINTER_READ

BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ_STACK_CORRUPTION

SYMBOL_NAME: UT2004.exe!Unknown

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: UT2004

IMAGE_NAME: UT2004.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4384debf

FAILURE_BUCKET_ID: UT2004.exe!Unknown_c0000005_NULL_POINTER_READ

BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_READ_STACK_CORRUPTION_UT2004.exe!Unknown

Followup: MachineOwner
---------

eax=22b00000 ebx=00000000 ecx=00000007 edx=7c90eb94 esi=00148128 edi=000008a0
eip=7c90eb94 esp=0012c60c ebp=0012c61c iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200246
ntdll!KiFastSystemCallRet:
7c90eb94 c3 ret
ChildEBP RetAddr Args to Child
0012c614 7c864359 00000948 ffffffff 0012c664 ntdll!KiFastSystemCallRet (FPO: [0,0,0])
0012c61c ffffffff 0012c664 00000000 00000000 kernel32!Module32NextW+0x45 (FPO: [Non-Fpo])
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012c630 7c90e96c 7c86439a ffffffff 22b00000 0xffffffff
0012c634 7c86439a ffffffff 22b00000 21c2f674 ntdll!NtUnmapViewOfSection+0xc (FPO: [2,0,0])
0012ce74 00000000 000008a0 00000001 00000001 kernel32!Module32NextW+0x86 (FPO: [Non-Fpo])
start end module name
00320000 0095e000 Engine Engine.dll Wed Nov 23 16:25:36 2005 (4384DE50)
04c10000 04d0d000 D3DDrv D3DDrv.dll Wed Nov 23 16:26:50 2005 (4384DE9A)
04d50000 04d61000 XGame XGame.dll Wed Nov 23 16:26:02 2005 (4384DE6A)
04fb0000 050fc000 Editor Editor.dll Wed Nov 23 16:26:30 2005 (4384DE86)
05190000 0519d000 UWeb UWeb.dll Wed Nov 23 16:25:59 2005 (4384DE67)
05270000 05303000 XInterface XInterface.dll Wed Nov 23 16:27:05 2005 (4384DEA9)
05540000 05578000 Onslaught Onslaught.dll Wed Nov 23 16:28:50 2005 (4384DF12)
07130000 07178000 ALAudio ALAudio.dll Wed Nov 23 16:26:39 2005 (4384DE8F)
07180000 07188000 vorbisfile vorbisfile.dll Wed Nov 23 16:23:32 2005 (4384DDD4)
07190000 07196000 ogg ogg.dll Wed Nov 23 16:23:25 2005 (4384DDCD)
071a0000 071c1000 vorbis vorbis.dll Wed Nov 23 16:23:31 2005 (4384DDD3)
071e0000 072c3000 DefOpenAL32 DefOpenAL32.dll Fri Jul 11 15:23:01 2003 (3F0F0E95)
10000000 1003c000 IFC23 IFC23.dll Wed Sep 17 19:44:49 2003 (3F68F1F1)
10100000 102a2000 Core Core.dll Wed Nov 23 16:23:44 2005 (4384DDE0)
10500000 1051a000 Fire Fire.dll Wed Nov 23 16:26:09 2005 (4384DE71)
10700000 1073c000 IpDrv IpDrv.dll Wed Nov 23 16:25:55 2005 (4384DE63)
10900000 10956000 UT2004 UT2004.exe Wed Nov 23 16:27:27 2005 (4384DEBF)
11000000 11068000 Window Window.dll Wed Nov 23 16:25:48 2005 (4384DE5C)
11100000 111d1000 WinDrv WinDrv.dll Wed Nov 23 16:27:18 2005 (4384DEB6)
20000000 20011000 spgrmr spgrmr.dll Wed Aug 04 03:57:15 2004 (411096DB)
5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 03:56:43 2004 (411096BB)
5b860000 5b8b4000 netapi32 netapi32.dll Thu Aug 17 08:28:27 2006 (44E460EB)
5c200000 5c2be000 spttseng spttseng.dll Sat Aug 18 01:37:06 2001 (3B7DFF02)
5c2c0000 5c300000 sptip sptip.dll Wed Aug 04 03:59:01 2004 (41109745)
5c3b0000 5c3c4000 spcommon spcommon.dll Sat Aug 18 01:36:58 2001 (3B7DFEFA)
5d090000 5d12a000 comctl32 comctl32.dll Fri Aug 25 11:45:58 2006 (44EF1B36)
605d0000 605d9000 mslbui mslbui.dll Wed Aug 04 03:58:39 2004 (4110972F)
629c0000 629c9000 lpk lpk.dll Wed Aug 04 03:56:26 2004 (411096AA)
651b0000 651d2000 asOEHook asOEHook.dll Fri Sep 23 21:38:10 2005 (4334AE02)
662b0000 66308000 hnetcfg hnetcfg.dll Wed Aug 04 03:56:16 2004 (411096A0)
688f0000 688f9000 hid hid.dll Wed Aug 04 03:56:12 2004 (4110969C)
6af90000 6afee000 CCL40 CCL40.DLL Tue Jan 23 01:13:25 2007 (45B5A785)
6ce10000 6ce48000 dinput8 dinput8.dll Wed Aug 04 03:56:32 2004 (411096B0)
6d510000 6d58d000 dbghelp dbghelp.dll Thu Aug 29 06:40:22 2002 (3D6DFA16)
6d6e0000 6d797000 sapi sapi.dll Wed Aug 04 03:56:32 2004 (411096B0)
6d990000 6d996000 d3d8thk d3d8thk.dll Wed Aug 04 03:56:02 2004 (41109692)
6d9a0000 6dac8000 d3d8 d3d8.dll Wed Aug 04 03:56:02 2004 (41109692)
71a50000 71a8f000 mswsock mswsock.dll Wed Aug 04 03:59:20 2004 (41109758)
71a90000 71a98000 wshtcpip wshtcpip.dll Wed Aug 04 03:57:49 2004 (411096FD)
71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 03:57:39 2004 (411096F3)
71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 03:57:38 2004 (411096F2)
71ad0000 71ad9000 wsock32 wsock32.dll Wed Aug 04 03:57:51 2004 (411096FF)
72280000 722aa000 dinput dinput.dll Wed Aug 04 03:56:31 2004 (411096AF)
72d10000 72d18000 msacm32_72d10000 msacm32.drv Sat Aug 18 01:33:30 2001 (3B7DFE2A)
72d20000 72d29000 wdmaud wdmaud.drv Wed Aug 04 03:56:54 2004 (411096C6)
732e0000 732e5000 riched32 riched32.dll Sat Aug 18 01:33:28 2001 (3B7DFE28)
73760000 737a9000 ddraw ddraw.dll Wed Aug 04 03:56:16 2004 (411096A0)
73b50000 73b67000 avifil32 avifil32.dll Wed Aug 04 03:57:07 2004 (411096D3)
73bc0000 73bc6000 dciman32 dciman32.dll Wed Aug 04 03:56:15 2004 (4110969F)
73ee0000 73ee4000 ksuser ksuser.dll Wed Aug 04 03:56:29 2004 (411096AD)
73f10000 73f6c000 dsound dsound.dll Wed Aug 04 03:57:08 2004 (411096D4)
74720000 7476b000 msctf msctf.dll Wed Aug 04 03:57:30 2004 (411096EA)
74c80000 74cac000 oleacc oleacc.dll Sat Aug 18 01:33:18 2001 (3B7DFE1E)
74d90000 74dfb000 usp10 usp10.dll Wed Aug 04 03:56:42 2004 (411096BA)
74e30000 74e9c000 riched20 riched20.dll Mon Nov 27 09:54:06 2006 (456AFC0E)
751d0000 751ee000 wshbth wshbth.dll Wed Aug 04 03:57:43 2004 (411096F7)
755c0000 755ee000 msctfime msctfime.ime Wed Aug 04 03:57:31 2004 (411096EB)
75a70000 75a91000 msvfw32 msvfw32.dll Wed Aug 04 03:59:15 2004 (41109753)
76080000 760e5000 msvcp60 msvcp60.dll Wed Aug 04 03:59:13 2004 (41109751)
76360000 76370000 winsta winsta.dll Wed Aug 04 03:56:40 2004 (411096B8)
76390000 763ad000 imm32 imm32.dll Wed Aug 04 03:56:30 2004 (411096AE)
763b0000 763f9000 comdlg32 comdlg32.dll Wed Aug 04 03:56:32 2004 (411096B0)
76780000 76789000 shfolder shfolder.dll Wed Aug 04 03:56:40 2004 (411096B8)
76b40000 76b6d000 winmm winmm.dll Wed Aug 04 03:57:10 2004 (411096D6)
76bf0000 76bfb000 psapi psapi.dll Wed Aug 04 03:56:58 2004 (411096CA)
76c30000 76c5e000 wintrust wintrust.dll Wed Aug 04 03:56:41 2004 (411096B9)
76c90000 76cb8000 imagehlp imagehlp.dll Wed Aug 04 03:56:25 2004 (411096A9)
76f20000 76f47000 dnsapi dnsapi.dll Mon Jun 26 13:37:10 2006 (44A01B46)
76f50000 76f58000 wtsapi32 wtsapi32.dll Wed Aug 04 03:57:55 2004 (41109703)
76f60000 76f8c000 wldap32 wldap32.dll Wed Aug 04 03:56:43 2004 (411096BB)
76fb0000 76fb8000 winrnr winrnr.dll Wed Aug 04 03:56:35 2004 (411096B3)
76fc0000 76fc6000 rasadhlp rasadhlp.dll Mon Jun 26 13:37:10 2006 (44A01B46)
76fd0000 7704f000 clbcatq clbcatq.dll Tue Jul 26 00:39:44 2005 (42E5BE90)
77050000 77115000 comres comres.dll Wed Aug 04 03:56:36 2004 (411096B4)
77120000 771ab000 oleaut32 oleaut32.dll Thu May 17 07:28:05 2007 (464C3C45)
773d0000 774d3000 comctl32_773d0000 comctl32.dll Fri Aug 25 11:45:55 2006 (44EF1B33)
774e0000 7761d000 ole32 ole32.dll Tue Jul 26 00:39:47 2005 (42E5BE93)
77920000 77a13000 setupapi setupapi.dll Wed Aug 04 03:56:32 2004 (411096B0)
77a80000 77b14000 crypt32 crypt32.dll Wed Aug 04 03:56:01 2004 (41109691)
77b20000 77b32000 msasn1 msasn1.dll Wed Aug 04 03:57:23 2004 (411096E3)
77bd0000 77bd7000 midimap midimap.dll Wed Aug 04 03:56:25 2004 (411096A9)
77be0000 77bf5000 msacm32 msacm32.dll Wed Aug 04 03:57:03 2004 (411096CF)
77c00000 77c08000 version version.dll Wed Aug 04 03:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 03:59:14 2004 (41109752)
77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 03:56:23 2004 (411096A7)
77e70000 77f02000 rpcrt4 rpcrt4.dll Mon Jul 09 09:09:42 2007 (46923396)
77f10000 77f57000 gdi32 gdi32.dll Tue Jun 19 09:31:19 2007 (4677DAA7)
77f60000 77fd6000 shlwapi shlwapi.dll Thu Oct 11 02:13:45 2007 (470DBF19)
77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 03:56:49 2004 (411096C1)
7c340000 7c396000 MSVCR71 MSVCR71.dll Fri Feb 21 07:42:20 2003 (3E561EAC)
7c3a0000 7c41b000 msvcp71 msvcp71.dll Wed Mar 19 00:14:51 2003 (3E77EEBB)
7c800000 7c8f5000 kernel32 kernel32.dll Mon Apr 16 11:52:53 2007 (46239BD5)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 03:56:36 2004 (411096B4)
7c9c0000 7d1d6000 shell32 shell32.dll Thu Oct 25 23:36:50 2007 (472160D2)
7e1e0000 7e280000 urlmon urlmon.dll Thu Oct 11 02:13:45 2007 (470DBF19)
7e410000 7e4a0000 user32 user32.dll Thu Mar 08 10:36:28 2007 (45F02D7C)
Closing open log file c:\debuglog.txt

 

Your thread title states, "Problem with a specific game." but I do not think you identified which "specific game" you have issues with.

From what I could gather, your first post in this thread and your most recently posted dump log seem to implicate UT2004. I think UT2004.exe belongs to "Unreal Tournament 2004 ".

If this is the case, then perhaps your best course of action is to contact Unreal Tournament 2004's official technical support (if such support exists) to help you resolve your issue with Unreal Tournament 2004.

Might be helpful for them if you send/post your UT-related dump log(s) for them to analyze.

The best I could do for locating UT2004-related links are as follows.

• ComputerHope.com: Information about the game Unreal

• unrealtournament2003.com: Unreal Tournament

• Epic Games Forums > Unreal Tournament 2003/2004 > Troubleshooting & Technology

 

I've tried the UT2004 forums, no one posted anything for weeks there. In addition, like I stated in a previous post, I want to tackle my pc problems for all aspects. When I make progress in one area, I can make leaway in another area. I've posted in the other threads I started here, but no one seems to be having an idea of how to help me. I think the problem lies in the IQ Manager because of recent, (and if I think about it, past), BSOD messages. I've posted something regarding this recently in the spyware & Virus thread I started.

Oh, and just so its clear, there is no other help than the ut forums offered for that game. So, my best bet would be to come to a place where guru's on the net are located, (I.E. here).

Look, I really, really, don't want to wipe out my pc. That would be just like saying, "Hey, person whom made the file that ****** up my pc, you won. Hope I never run into that program you made, cause I'd would have no choice but to erase all that is precious to me on my home pc." That, is what I don't want to come to. Oh, and when I tried to generate a log from files other than the game crash files, it either told me "access denied ", or "unable to access the file ". I'll post where the files are located on my pc that give these messages.

1. The one located in my documents and settings:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Orion\SMSTUB16.DMP]
Could not match Dump File signature - invalid file format
Could not open dump file [C:\Documents and Settings\Orion\SMSTUB16.DMP], HRESULT 0x80004002
"No such interface supported "

This one has a date of the ninth of this month of 2008.

2. The one located in the Dr Watson folder:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
Could not open dump file [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp], Win32 error 0n5
"Access is denied. "

This one has the date of the 15th of december of 2007.

3. This one is located in the windows folder of the C: drive:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Could not open dump file [C:\WINDOWS\MEMORY.DMP], NTSTATUS 0xC000011E
"An attempt was made to map a file of size zero with the maximum size specified as zero. "

This one has todays date on it. It sometimes has something in it, but it still won't open even then.

When I tried to open up the one in my documents and setting earlier this week, it opened and worked completely. Unfortunately, a BSOD happened, and it didn't open up after that. I have run scans for .dmp files. I've found out by that that there are 17 .dmp files on my pc, (Thats including game .dmp files as well). When I ran the scan for the .dmp files the first time, a BSOD happened in the process. I don't know why it happened, I was only running the scan, a internet explorer window of this site, and a window opened up so I can open the debuglog.txt file.

If anyone, and I do mean anyone, has a clue, as to what the heck is making these events happen to my pc, then please, just post it. I want help, and I'm not going to turn any idea away.

 

Oh, and just so its clear, I have kept up with the other threads that I've started on this site. The problem is, that either people have no clue as to how to fix my problem, (or just stopped giving a hoot), or, those that have posted assistance have been preocupied with other areas of concern, that I'm put on the back burner, the way, way back, burner.

 

Here are locations where I started up threads on my pc problem.

Note: This list contains links to places on this site.

Warning: Its a lot of stuff to cover, once you go through all of it.

1. http://www.windowsbbs.com/showthread.php?t=70222

2. http://www.windowsbbs.com/showthread.php?t=69307

3. http://www.windowsbbs.com/showthread.php?t=70060

4. http://forums.epicgames.com/showthread.php?t=597294

5. http://unrealinsanity.com/modules.php?name=Forums&file=viewtopic&t=1680

 

Forsaken Knight, a BSOD will be most likely be due to hardware or drivers. You upgraded the power supply and that has apparently made a difference, but before that you had "noises" and that will relate to a hardware problem.

I would get "serious" if I were you and this may be the time to maybe go from Beginner experience to Intermediate.

Many hardware problems cannot be identified unless the parts are swapped with other, known working, parts.

Games depend mainly on graphics. If there is a possibility of the graphics overheating, leave the case open and direct a desk fan into it. Graphics drivers problems can mean complete removal and reinstallation.

You mention "scans ", that may be a file system problem. You will need to clean the drive. Make certain there is plenty of free-space (20-25%). Do a Disk Defragmentation. Run Error Checking (chkdsk) on the drive, with settings of checking the disk surface [see Help and Support]. You have only been able to open one dump, which may also point to a drive problem. You can also run the drive manufacturer's utilities.

Drivers run the hardware. Check for updates. Start with updating the chipset drivers (I mentioned this when you asked in the hardware forum, but you did not say if you followed it up).

Your computer has been "sick" (power supply and spyware) which does not help.

You will need to isolate the problem to hardware or software. As I said, hardware problems can be identified by swapping parts.

I can see you want to "defeat" the problem, but it may well take some drastic action. You don't want to reinstall Windows, so you will need to rely on tests, checks, diagnostics, swapping parts, etc, although I hope someone can "see" the problem for you.

Matt