Sign in with
Sign up | Sign in
Your question

Gaming problem on win7

Last response: in Windows 7
Share
May 16, 2011 4:00:17 PM

Hey all,

I recently upgraded to windows 7, from XP and when i was on XP i had no problems running games on my current rig. However, since ive upgraded all the games i've tried have had similar problems, after a while of gaming the game will either freeze and then crash to the desktop where you get the generic windows has encountered a problem and must close or whatever. Then the other crash is where it stays frozen until i ctrl alt delete and close the program via the task manager. Granted this is 2 games, but both games ran fine in XP with no problems so i'm assuming it can only be a windows 7 error? I like windows 7 and i dont wanna stop using it because of this, i'd rather get it fixed. Oh and the games are The first templar and Just cause 2.
Everything is up to date, GPU drivers, NET framework, directx11 and obviously because i upgraded to windows 7 i did a clean install, wiped the entire hard disk. I really can't figure out the problem and i would greatly appreciate it if anyone could help

Specs:
PSU: 1000w
CPU: AMD athlon II 64 X2 dual core 6000+ 3.0ghz
GPU: Geforce GTX 275
MB: Gigabyte M720-US3
OS: Win7 32bit
RAM: 4GB

A fairly average rig, which could handle all the games on XP, including Crysis, Far cry 2, mass effect etc etc.

Thanks in advanced.

More about : gaming problem win7

May 16, 2011 7:51:00 PM

its not the games, i have just cause 2 and it works great.

did you check the logs in windows? right click on computer> manage> event viewer> windows logs> application logs and system logs
see if any warnings happened while you were gaming
m
0
l
May 16, 2011 7:54:22 PM

I know its not the games, all things lead me to believe its windows 7. Yeah i did look at them but they mean nothing to me.

Just cause demo

Faulting application name: JustCause2.exe, version: 1.0.0.2, time stamp: 0x4ba03354
Faulting module name: JustCause2.exe, version: 1.0.0.2, time stamp: 0x4ba03354
Exception code: 0xc0000005
Fault offset: 0x0051a422
Faulting process id: 0x4ac
Faulting application start time: 0x01cc13fd0b0df720
Faulting application path: c:\program files\steam\steamapps\common\just cause 2 demo\JustCause2.exe
Faulting module path: c:\program files\steam\steamapps\common\just cause 2 demo\JustCause2.exe
Report Id: cdd4e690-7ff2-11e0-8ee9-6cf0491de83e

The first templar

Faulting application name: TFT.exe, version: 1.0.595.4005, time stamp: 0x4da5a0c7
Faulting module name: d3d9.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b7b3
Exception code: 0xc0000005
Fault offset: 0x00007271
Faulting process id: 0xe74
Faulting application start time: 0x01cc140057ddc910
Faulting application path: c:\program files\steam\steamapps\common\the first templar\TFT.exe
Faulting module path: C:\Windows\system32\d3d9.dll
Report Id: 1e3ffd20-7ff5-11e0-8ee9-6cf0491de83e
m
0
l
Related resources
May 16, 2011 8:24:01 PM

If that comes out clean, try rolling back your video driver.
m
0
l
May 16, 2011 8:30:55 PM

I'll give the memtest ago, i did recently upgrade my RAM, but after this crashing started happening i did take it out and it did it, only tested one of the games though. I'll give this a try.

Oh i've downgraded the video drivers, twice
m
0
l
May 16, 2011 9:28:47 PM

The memtest passed twice, no errors were found.

and like i said, tried rolling back the drivers.

Is there anything else? I'm very eager to get this problem solved
m
0
l
May 17, 2011 10:10:31 AM

Okay thanks, i'll give that ago and reply back with the outcome.
m
0
l
May 17, 2011 10:47:49 AM

I'm afraid it didnt work, it let me play for a bit longer though, and i believe the error that i got is different?

Faulting application name: JustCause2.exe, version: 1.0.0.2, time stamp: 0x4ba03354
Faulting module name: fmodex.dll, version: 0.4.20.26, time stamp: 0x4a31e551
Exception code: 0xc0000005
Fault offset: 0x000427d9
Faulting process id: 0x1030
Faulting application start time: 0x01cc147b1047e5b0
Faulting application path: c:\program files\steam\steamapps\common\just cause 2 demo\JustCause2.exe
Faulting module path: c:\program files\steam\steamapps\common\just cause 2 demo\fmodex.dll
Report Id: 94d570f0-8072-11e0-9193-6cf0491de83e

Same error for The first templar though

Faulting application name: TFT.exe, version: 1.0.595.4005, time stamp: 0x4da5a0c7
Faulting module name: d3d9.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b7b3
Exception code: 0xc0000005
Fault offset: 0x00007271
Faulting process id: 0x1644
Faulting application start time: 0x01cc147ff32de0b0
Faulting application path: c:\program files\steam\steamapps\common\the first templar\TFT.exe
Faulting module path: C:\Windows\system32\d3d9.dll
Report Id: cb078440-8074-11e0-9193-6cf0491de83e
m
0
l
May 17, 2011 1:31:42 PM

I had a similar problem. My problem was one stick of RAM. I bought new ram, installed and was back to gaming. Try out each stick 1 by 1. And see if you get those random crashes. I know it's kinda weird how before it worked and now it doesn't but you never know.
m
0
l
a b $ Windows 7
May 17, 2011 3:19:57 PM

Buyno said:
I'm afraid it didnt work, it let me play for a bit longer though, and i believe the error that i got is different?

Faulting application name: JustCause2.exe, version: 1.0.0.2, time stamp: 0x4ba03354
Faulting module name: fmodex.dll, version: 0.4.20.26, time stamp: 0x4a31e551
Exception code: 0xc0000005
Fault offset: 0x000427d9
Faulting process id: 0x1030
Faulting application start time: 0x01cc147b1047e5b0
Faulting application path: c:\program files\steam\steamapps\common\just cause 2 demo\JustCause2.exe
Faulting module path: c:\program files\steam\steamapps\common\just cause 2 demo\fmodex.dll
Report Id: 94d570f0-8072-11e0-9193-6cf0491de83e

Same error for The first templar though

Faulting application name: TFT.exe, version: 1.0.595.4005, time stamp: 0x4da5a0c7
Faulting module name: d3d9.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b7b3
Exception code: 0xc0000005
Fault offset: 0x00007271
Faulting process id: 0x1644
Faulting application start time: 0x01cc147ff32de0b0
Faulting application path: c:\program files\steam\steamapps\common\the first templar\TFT.exe
Faulting module path: C:\Windows\system32\d3d9.dll
Report Id: cb078440-8074-11e0-9193-6cf0491de83e

Verify your game cache files on Steam and if you still have problems dump the game and re-install it.
m
0
l
May 17, 2011 3:26:32 PM

I've tried that already, and now im having similar problem with a non-steam game, Witcher 2 which i just got today. This one doesnt give me an error, just crashes to the desktop and takes me back to the game launcher.

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

Theres obviously something seriously wrong, and its only started since windows 7 was installed. Something in my system isnt compatible with it? Should i try the 64bit version?
m
0
l
a b $ Windows 7
May 18, 2011 5:07:40 AM

All i can think of is firewall settings and connectivity issues you have to allow games through the firewall.
I also think you have corrupt or damaged dll files.
Did you do a clean install of Win7?
I'd run sfc/scannow and check your hdd for damaged and or missing files.
m
0
l
May 18, 2011 2:51:13 PM

Okay guys i tred everything and i think i may have made progress.

I tried what pierogi210 said, i removed all the RAM and tried it one by one, and when i had one gig of ram in the first slot, the crashes stopped, so i tried a second stick in the with the working stick, and the crashes started again, so i thought it may have been the slot, but i tried all different slots but it only seems to be working with one stick of ram in the MB, but the games are neigh on unplayable with just one stick.

Anyone have an idea as to whats wrong? I have 2 sticks of old ram and 2 sticks of the recent ones, i've tried mixing them all but it seems that only 1GB of ram is working in my PC.
m
0
l
a b $ Windows 7
May 19, 2011 12:40:29 PM

Unless the ram speeds,timings,and voltages are the same yes! you'll have problems.
I'd run a Memtest86+ one stick at a time.
m
0
l
!