Sign in with
Sign up | Sign in
Your question

Games stop working - crash to desktop

Last response: in Video Games
Share
April 23, 2011 11:42:38 AM

ok ive been having the problem of games crashing to desktop for a while now. i have recently installed windows 7 to see if it was a software issue (clean formatting of my HD ect to see if that helped) no luck there. I had the CTD problems in XP also.

tried other Ram from a friends computer which didnt help.

the games in question are:

Portal 2
Magicka
Assassins Creed Brotherhood
The Last Remnant
Dead Space 2

this is magicka's error log from when it crashed:

Version: 1.3.6.1
Thread: RenderThread
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Microsoft.Xna.Framework.Gjk.UpdateDeterminant(Int32 xmIdx)
at Microsoft.Xna.Framework.Gjk.AddSupportPoint(Vector3& newPoint)
at Microsoft.Xna.Framework.BoundingFrustum.Intersects(BoundingBox& box, Boolean& result)
at Microsoft.Xna.Framework.BoundingBox.Contains(BoundingFrustum frustum)
at PolygonHead.Models.BiTreeModel.RenderData.Cull(BoundingFrustum iViewFrustum)
at PolygonHead.Scene.DrawShadows(DataChannel iDataChannel, BoundingFrustum iViewFrustum, Single iDeltaTime)
at PolygonHead.Lights.DirectionalLight.DrawShadows(DataChannel iDataChannel, Single iDeltaTime, Scene iScene)
at PolygonHead.Scene.DrawLightShadows(DataChannel iDataChannel, Single iDeltaTime, BoundingFrustum iViewFrustum)
at PolygonHead.RenderManager.RenderScene(Scene currentScene, DataChannel iDataChannel, GameTime& iGameTime)
at Magicka.Game.Draw(GameTime gameTime)
at Microsoft.Xna.Framework.Game.DrawFrame()
at Microsoft.Xna.Framework.Game.Tick()
at Microsoft.Xna.Framework.Game.HostIdle(Object sender, EventArgs e)
at Microsoft.Xna.Framework.GameHost.OnIdle()
at Microsoft.Xna.Framework.WindowsGameHost.ApplicationIdle(Object sender, EventArgs e)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Microsoft.Xna.Framework.WindowsGameHost.Run()
at Microsoft.Xna.Framework.Game.Run()
at Magicka.Program.Main(String[] args)


previously in XP i suffered from a few BSOD's straight from the games. the 3 error codes i recieved were

Attempt to execute non-executable memory
NTFS.sys - page fault in non paged area
Driver IRQL not less or equal

as yet i havent BSOD in windows 7 though.

finally a DXdiag in the hope it helps.

------------------
System Information
------------------
Time of this report: 4/22/2011, 22:09:25
Machine name: MURDROBE
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: M68M-S2P
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ (2 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 4094MB RAM
Page File: 1923MB used, 6264MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 8800 GT
Manufacturer: NVIDIA
Chip type: GeForce 8800 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0611&SUBSYS_34721458&REV_A2
Display Memory: 2030 MB
Dedicated Memory: 239 MB
Shared Memory: 1791 MB
April 23, 2011 5:37:44 PM

have you ran chkdsk recently. if your games arnt legit are you sure there clean?
is the system eventlog showing any hardware errors.
as pagefile violations and not less than errors tend to be down to bad drivers.

make sure you install everything under admin privs especially drivers. make sure all your motherboard drivers installed properly especially the cpu info 1 (you may need to run it in vista compatability mode to get this 1 to install propperly)
April 23, 2011 10:27:45 PM

chkdsk doesnt seem to run for me. just a cmd box for a second or 2 then disappears.

in the event viewer i have a few errors showing up.
The Driver Detected a a Controller Error on \Device\HardDisk1\DR1.

Faulting application name: portal2.exe, version: 0.0.0.0, time stamp: 0x4d4c804d
Faulting module name: studiorender.dll, version: 0.0.0.0, time stamp: 0x4da8d7eb
Exception code: 0xc0000005
Fault offset: 0x0004f791
Faulting process id: 0x11e4
Faulting application start time: 0x01cc01a09cab2618
Faulting application path: C:\Users\bob\Downloads\Portal.2.Skidrow\common\portal 2\portal2.exe
Faulting module path: c:\users\bob\downloads\portal.2.skidrow\common\portal 2\bin\studiorender.dll
Report Id: c0caa7e8-6d94-11e0-9233-1c6f655233dc

Faulting application name: portal2.exe, version: 0.0.0.0, time stamp: 0x4d4c804d
Faulting module name: studiorender.dll, version: 0.0.0.0, time stamp: 0x4da8d7eb
Exception code: 0xc0000005
Fault offset: 0x0004efcd
Faulting process id: 0x4a4
Faulting application start time: 0x01cc01a23f4578c8
Faulting application path: C:\Users\bob\Downloads\Portal.2.Skidrow\common\portal 2\portal2.exe
Faulting module path: c:\users\bob\downloads\portal.2.skidrow\common\portal 2\bin\studiorender.dll
Report Id: f895fde8-6d95-11e0-9233-1c6f655233dc

Faulting application name: ACBSP.exe, version: 0.0.0.0, time stamp: 0x4d8cb6d5
Faulting module name: nvd3dum.dll, version: 8.17.12.7061, time stamp: 0x4d9e7b5d
Exception code: 0xc0000005
Fault offset: 0x004dc4a9
Faulting process id: 0x1498
Faulting application start time: 0x01cc01a7973f3168
Faulting application path: C:\Program Files (x86)\Ubisoft\Assassin's Creed Brotherhood\ACBSP.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: c79030c8-6d9b-11e0-9233-1c6f655233dc

there are other errors there but none seem to be linked to my CTD problem at least as far as i can tell.
Related resources
April 23, 2011 11:17:07 PM

I have had similar BSOD screens with my overclocking
values were wrong. If overclockig try setting everything
to default and playing some of those games and see if you still have issue. As for Portal 2, Skidrow has a patch up to fix some of the horrible bugs that were released with it ;)  Hope this helps.
April 23, 2011 11:49:39 PM

as far as im aware, nothing on my computer should be overclocked but i will check with the friend that built it for me as soon as i can.

i did try the portal 2 patch.... on a side note, this is the 2nd time hes fixed a steam game when the dev's take a long time to sort it.

if its any use i could try running the other games see if it narrows down what my problem is via the error log..
April 24, 2011 2:22:42 AM

dont run chkdsk from the run prompt run it from inside the cmd prompt
start/allprogramms/accessories right click on cmd and select run as administrator.

when the cmd opens type chkdsk /f

1s done reinstall the games if they dont work.
also you may want to update your gfx/audio and system drivers
April 24, 2011 4:43:14 AM

On your post it looks as though you may be also
having issues with .netframework. Try uninstalling and reinstalling
with the most recent .netframework
April 25, 2011 2:51:56 AM

ran chkdsk on reboot, it closed faster than i could see if it mentioned any problems.

updated all drivers.
reinstalled games.
updated to .netframework 4.

the games still CTD :( 
April 25, 2011 2:55:48 AM

an XML view of the latest error incase it helps

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-04-25T02:49:31.000000000Z" />
<EventRecordID>1529</EventRecordID>
<Channel>Application</Channel>
<Computer>murdrobe</Computer>
<Security />
</System>
- <EventData>
<Data>ACBSP.exe</Data>
<Data>0.0.0.0</Data>
<Data>4d8cb6d5</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>00000000</Data>
<Data>d6c</Data>
<Data>01cc02f2602e0680</Data>
<Data>C:\Program Files (x86)\Ubisoft\Assassin's Creed Brotherhood\ACBSP.exe</Data>
<Data>unknown</Data>
<Data>a4dfa300-6ee6-11e0-923f-1c6f655233dc</Data>
</EventData>
</Event>
April 25, 2011 3:33:54 PM

after searching around on google, i saw a possible solution that says the 0xc0000005 error code can be caused by the programs in question not being allowed by the windows DEP..... when trying to add portal 2 to the exceptions list earlier it just said it cant be added and it must be run with the DEP enabled for it... could this be my issue?
April 25, 2011 7:12:47 PM

unlikley as i have portal 2 and it works perfectly. without adjusting any of that. in fact i have played all the games you have listed (apart from reminant)with no issues.

u did run the a games as admin? not doing so can cause basic crashes that have no crash number...
April 25, 2011 8:28:42 PM

running as admin didnt help. there seems to be a million and 1 posible solutions to the error code and the nvd3dum.dll file but i cant seem to find 1 that corrolates to both.

thanks for the help so far :) 
April 26, 2011 12:14:46 AM

he ran chkdisk m8
Quote:

More Information

ran chkdsk on reboot, it closed faster than i could see if it mentioned any problems.

updated all drivers.
reinstalled games.
updated to .netframework 4.

the games still CTD

im really baffled as to why he's having so many issues. im starting to think its malware or a hardware fault myself. but without actually looking at the machine im stumped.
April 26, 2011 1:51:55 AM

will work through that list of stuff to try tomorrow morning.

i did get chkdsk to run as administrator. it ran on reboot but it closed without showing me if there is any problems after it completed. unless it saves a log somewhere?

before i switched to windows 7, on XP memtest did cause me to BSOD, but as mentioned in the 1st post, i have tried other RAM without it solving anything.

my games crash after starting up, longest ive got to play was about 10 min on portal 2. shortest, maybe a minute.

i do have to right click things to run as admin, is there a way to make sure im always admin? its a home comp and theres only really me using it so it wouldnt cause a problem.
April 26, 2011 2:32:00 PM

[Tue Apr 26 15:26:52 2011]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
prime 95 results

i cant find the stress.txt though....

it didnt get to run for 10 mintutes. lasted about 2 before it found that error

V24OptionsConverted=1
WGUID_version=2
StressTester=1
UsePrimenet=0
MinTortureFFT=8
MaxTortureFFT=64
TortureMem=8
TortureTime=15
Windows95Service=0

[PrimeNet]
Debug=0

is from the other file it saves
April 26, 2011 2:49:18 PM

running furmark, the temp sensor went nuts after about 4 minutes.

CPUID HWMonitor Report
-------------------------------------------------------------------------

Binaries
-------------------------------------------------------------------------

HWMonitor version 1.1.7.0

Monitoring
-------------------------------------------------------------------------

Mainboard Model M68M-S2P (0x0000020A - 0x00A969C4)

LPCIO
-------------------------------------------------------------------------

LPCIO Vendor ITE
LPCIO Model IT8720
LPCIO Vendor ID 0x90
LPCIO Chip ID 0x8720
LPCIO Revision ID 0x8
Config Mode I/O address 0x2E
Config Mode LDN 0x4
Config Mode registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20 87 20 08 09 3A 00 80 00 40 00 00 00 00 00 00 00
30 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60 02 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 02 00 00 04 04 00 00 00 00 00 00 00 00 00 00
Register space LPC, base address = 0x0290


Hardware Monitors
-------------------------------------------------------------------------

Hardware monitor ITE IT87
Voltage 0 1.42 Volts [0x59] (CPU VCORE)
Voltage 1 1.90 Volts [0x77] (VIN1)
Voltage 2 3.41 Volts [0xD5] (+3.3V)
Voltage 4 12.35 Volts [0xC1] (+12V)
Voltage 5 -8.58 Volts [0x86] (-12V)
Voltage 6 -13.63 Volts [0xD5] (-5V)
Voltage 7 3.63 Volts [0x87] (+5V VCCH)
Voltage 8 3.10 Volts [0xC2] (VBAT)
Temperature 0 45°C (113°F) [0x2D] (TMPIN0)
Temperature 1 52°C (125°F) [0x34] (TMPIN1)
Temperature 2 50°C (122°F) [0x32] (TMPIN2)
Fan 0 3027 RPM [0xDF] (FANIN0)
Fan PWM 0 0 pc [0x0] (FANPWM0)
Fan PWM 1 2 pc [0x3] (FANPWM1)
Fan PWM 2 0 pc [0x0] (FANPWM2)
Register space LPC, base address = 0x0290

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 13 10 08 00 FF FF 00 37 FF 87 58 0F 07 DE FF 00
10 FF FF FF 33 D7 82 03 82 00 FF 00 FF FF FF FF FF
20 50 77 D2 FF C1 86 D3 87 C2 2D 34 2F 80 CD B7 B7
30 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00
40 7F 7F 7F 7F 7F 7F 5F 74 2D 40 95 00 FF FF FF FF
50 FF 1C 7F 7F 7F 50 00 00 90 00 04 12 60 00 00 00
60 FF 14 41 27 90 03 00 FF 7F 7F 7F 00 00 7F 00 FF
70 FF 14 41 20 90 03 00 FF FF FF FF FF FF FF FF FF
80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
90 FF 00 00 00 FF 00 00 00 FF FF FF FF FF FF FF FF
A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Hardware monitor NVIDIA NVAPI
Voltage 0 0.00 Volts [0x0] (VIN0)
Temperature 0 88°C (190°F) [0x58] (TMPIN0)
Fan PWM 0 100 pc [0x64] (FANPWMIN0)


Processors
-------------------------------------------------------------------------

Number of processors 1
Number of threads 2

APICs
-------------------------------------------------------------------------

Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1

Processors Information
-------------------------------------------------------------------------

Processor 1 ID = 0
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name AMD Athlon 64 X2 6400+
Codename Windsor
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 6400+
Package Socket AM2 (940)
CPUID F.3.3
Extended CPUID F.43
Brand ID 4
Core Stepping JH-F3
Technology 90 nm
Core Speed 1004.8 MHz
Multiplier x FSB 5.0 x 201.0 MHz
HT Link speed 1004.8 MHz
Stock frequency 3200 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64, AMD-V
L1 Data cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 2 x 1024 KBytes, 16-way set associative, 64-byte line size
FID/VID Control yes
Max FID 16.0x
Max VID 1.450 V
P-State FID 0x2 - VID 0x12 (5.0x - 1.100 V)
P-State FID 0xA - VID 0x10 (9.0x - 1.150 V)
P-State FID 0xC - VID 0x10 (10.0x - 1.150 V)
P-State FID 0xE - VID 0x10 (11.0x - 1.150 V)
P-State FID 0x10 - VID 0x0E (12.0x - 1.200 V)
P-State FID 0x12 - VID 0x0C (13.0x - 1.250 V)
P-State FID 0x14 - VID 0x0A (14.0x - 1.300 V)
P-State FID 0x16 - VID 0x08 (15.0x - 1.350 V)
P-State FID 0x18 - VID 0x06 (16.0x - 1.400 V)

K8 Thermal sensor yes
K8 Revision ID 5.3
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3

those are the HW monitor results from running furmark. if you need any other information let me know.

im not sure where to find the idle and max load numbers unless its in there somewhere
April 26, 2011 7:52:36 PM

you definatly have some failing hardware. and its motherboard related. either the cpu the memory or the motherboard itself.

go into bios and load the optimized defaults.
make sure your memory is running at the rite speed, latencies and voltage.
they should be running at 1.8-2.2v depending on make and model

check your cpu and turn off auto and set it to normal or 200. make sure your voltage is between 1.35 and 1.45 the lower the better but dont adjust it yet.

check for hpet (high precision event timer) and make sure it matches your o.s 32 for 32bit 64 for 64bit.

save and reboot.
run prime 95 again

April 26, 2011 8:33:19 PM

the motherboard is brand new, the last 1 died recently. so its a possibility it took the processor with it i suppose.

i dont have the box for my RAM any more, any idea how to check what it should be running at?

As for the RAM being the problem, it runs well in a friends PC and his doesnt make a difference to my problems. should be safe to rule that out pretty much from that right?

you dont think with the NVD3Dum.dll being listed as 1 of the errors it could be the graphics card? although the games do look nice for the few minutes i get to play them :p 
April 26, 2011 9:06:55 PM

loaded optimised defaults, Ram is running at 1.9V when it should be 1.8, couldnt find a bios page to change that. didnt see anything about latancies or speed either.

the HPET was wrong so i fixed that.

CPU voltage is set at 1.4V

couldnt see what you meant by "
check your cpu and turn off auto and set it to normal or 200"
April 26, 2011 9:40:34 PM

[Tue Apr 26 15:26:52 2011]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Tue Apr 26 22:36:02 2011]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Resulting sum was 1.564874981634867e+017, expected: 1.763624395874896e+017
Hardware failure detected, consult stress.txt file.


The Results from Prime95 this time.

HWMonitor version 1.1.7.0

Monitoring
-------------------------------------------------------------------------

Mainboard Model M68M-S2P (0x0000020A - 0x00A969C4)

LPCIO
-------------------------------------------------------------------------

LPCIO Vendor ITE
LPCIO Model IT8720
LPCIO Vendor ID 0x90
LPCIO Chip ID 0x8720
LPCIO Revision ID 0x8
Config Mode I/O address 0x2E
Config Mode LDN 0x4
Config Mode registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20 87 20 08 09 3A 00 80 00 40 00 00 00 00 00 00 00
30 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60 02 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 02 00 00 04 04 00 00 00 00 00 00 00 00 00 00
Register space LPC, base address = 0x0290


Hardware Monitors
-------------------------------------------------------------------------

Hardware monitor ITE IT87
Voltage 0 1.12 Volts [0x46] (CPU VCORE)
Voltage 1 1.90 Volts [0x77] (VIN1)
Voltage 2 3.38 Volts [0xD3] (+3.3V)
Voltage 4 12.35 Volts [0xC1] (+12V)
Voltage 5 -8.58 Volts [0x86] (-12V)
Voltage 6 -13.63 Volts [0xD5] (-5V)
Voltage 7 3.63 Volts [0x87] (+5V VCCH)
Voltage 8 3.10 Volts [0xC2] (VBAT)
Temperature 0 59°C (138°F) [0x3B] (TMPIN0)
Temperature 1 68°C (154°F) [0x44] (TMPIN1)
Temperature 2 58°C (136°F) [0x3A] (TMPIN2)
Fan 0 3054 RPM [0xDD] (FANIN0)
Fan PWM 0 0 pc [0x0] (FANPWM0)
Fan PWM 1 2 pc [0x3] (FANPWM1)
Fan PWM 2 0 pc [0x0] (FANPWM2)
Register space LPC, base address = 0x0290

00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 13 10 08 00 FF FF 00 37 FF 87 58 0F 07 DC FF 00
10 FF FF FF 33 D7 82 03 82 00 FF 00 FF FF FF FF FF
20 46 77 D4 FF C1 86 D4 87 C2 3B 44 3A 80 DC 97 97
30 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00 FF 00
40 7F 7F 7F 7F 7F 7F 5F 74 2D 40 95 00 FF FF FF FF
50 FF 1C 7F 7F 7F 50 00 00 90 00 04 12 60 00 00 00
60 FF 14 41 27 90 03 00 FF 7F 7F 7F 00 00 7F 00 FF
70 FF 14 41 20 90 03 00 FF FF FF FF FF FF FF FF FF
80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00
90 FF 00 00 00 FF 00 00 00 FF FF FF FF FF FF FF FF
A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Hardware monitor NVIDIA NVAPI
Voltage 0 0.00 Volts [0x0] (VIN0)
Temperature 0 52°C (125°F) [0x34] (TMPIN0)
Fan PWM 0 30 pc [0x1E] (FANPWMIN0)


Processors
-------------------------------------------------------------------------

Number of processors 1
Number of threads 2

APICs
-------------------------------------------------------------------------

Processor 0
-- Core 0
-- Thread 0 0
-- Core 1
-- Thread 0 1

Processors Information
-------------------------------------------------------------------------

Processor 1 ID = 0
Number of cores 2 (max 2)
Number of threads 2 (max 2)
Name AMD Athlon 64 X2 6400+
Codename Windsor
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 6400+
Package Socket AM2 (940)
CPUID F.3.3
Extended CPUID F.43
Brand ID 4
Core Stepping JH-F3
Technology 90 nm
Core Speed 1808.3 MHz
Multiplier x FSB 9.0 x 200.9 MHz
HT Link speed 1004.6 MHz
Stock frequency 3200 MHz
Instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64, AMD-V
L1 Data cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L1 Instruction cache 2 x 64 KBytes, 2-way set associative, 64-byte line size
L2 cache 2 x 1024 KBytes, 16-way set associative, 64-byte line size
FID/VID Control yes
Max FID 16.0x
Max VID 1.450 V
P-State FID 0x2 - VID 0x12 (5.0x - 1.100 V)
P-State FID 0xA - VID 0x10 (9.0x - 1.150 V)
P-State FID 0xC - VID 0x10 (10.0x - 1.150 V)
P-State FID 0xE - VID 0x10 (11.0x - 1.150 V)
P-State FID 0x10 - VID 0x0E (12.0x - 1.200 V)
P-State FID 0x12 - VID 0x0C (13.0x - 1.250 V)
P-State FID 0x14 - VID 0x0A (14.0x - 1.300 V)
P-State FID 0x16 - VID 0x08 (15.0x - 1.350 V)
P-State FID 0x18 - VID 0x06 (16.0x - 1.400 V)

K8 Thermal sensor yes
K8 Revision ID 5.3
Attached device PCI device at bus 0, device 24, function 0
Attached device PCI device at bus 0, device 24, function 1
Attached device PCI device at bus 0, device 24, function 2
Attached device PCI device at bus 0, device 24, function 3


Thread dumps
-------------------------------------------------------------------------

CPU Thread 0
APIC ID 0
Topology Processor ID 0, Core ID 0, Thread ID 0
Type 02002008h
Max CPUID level 00000001h
Max CPUID ext. level 80000018h
Cache descriptor Level 1, I, 64 KB, 1 thread(s)
Cache descriptor Level 1, D, 64 KB, 1 thread(s)
Cache descriptor Level 2, U, 1 MB, 1 thread(s)

CPUID
0x00000000 0x00000001 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00040F33 0x00020800 0x00002001 0x178BFBFF
0x80000000 0x80000018 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00040F33 0x000009A7 0x0000001F 0xEBD3FBFF
0x80000002 0x20444D41 0x6C687441 0x74286E6F 0x3620296D
0x80000003 0x32582034 0x61754420 0x6F43206C 0x50206572
0x80000004 0x65636F72 0x726F7373 0x30343620 0x00002B30
0x80000005 0xFF08FF08 0xFF20FF20 0x40020140 0x40020140
0x80000006 0x00000000 0x42004200 0x04008140 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x0000003F
0x80000008 0x00003028 0x00000000 0x00000001 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00000040 0x00000000 0x00000000
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000

MSR 0x0000001B 0x00000000 0xFEE00900
MSR 0xC0010114 0x00000000 0x00000018
MSR 0xC001001E 0x00000000 0x00000053
MSR 0xC0010015 0x00000000 0x02000040
MSR 0xC0010042 0x3104120C 0x04180212
MSR 0xC0010041 0x00000001 0x00000C12

CPU Thread 1
APIC ID 1
Topology Processor ID 0, Core ID 1, Thread ID 0
Type 02002008h
Max CPUID level 00000001h
Max CPUID ext. level 80000018h
Cache descriptor Level 1, I, 64 KB, 1 thread(s)
Cache descriptor Level 1, D, 64 KB, 1 thread(s)
Cache descriptor Level 2, U, 1 MB, 1 thread(s)

CPUID
0x00000000 0x00000001 0x68747541 0x444D4163 0x69746E65
0x00000001 0x00040F33 0x01020800 0x00002001 0x178BFBFF
0x80000000 0x80000018 0x68747541 0x444D4163 0x69746E65
0x80000001 0x00040F33 0x000009A7 0x0000001F 0xEBD3FBFF
0x80000002 0x20444D41 0x6C687441 0x74286E6F 0x3620296D
0x80000003 0x32582034 0x61754420 0x6F43206C 0x50206572
0x80000004 0x65636F72 0x726F7373 0x30343620 0x00002B30
0x80000005 0xFF08FF08 0xFF20FF20 0x40020140 0x40020140
0x80000006 0x00000000 0x42004200 0x04008140 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x0000003F
0x80000008 0x00003028 0x00000000 0x00000001 0x00000000
0x80000009 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000A 0x00000001 0x00000040 0x00000000 0x00000000
0x8000000B 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000D 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000E 0x00000000 0x00000000 0x00000000 0x00000000
0x8000000F 0x00000000 0x00000000 0x00000000 0x00000000
0x80000010 0x00000000 0x00000000 0x00000000 0x00000000
0x80000011 0x00000000 0x00000000 0x00000000 0x00000000
0x80000012 0x00000000 0x00000000 0x00000000 0x00000000
0x80000013 0x00000000 0x00000000 0x00000000 0x00000000
0x80000014 0x00000000 0x00000000 0x00000000 0x00000000
0x80000015 0x00000000 0x00000000 0x00000000 0x00000000
0x80000016 0x00000000 0x00000000 0x00000000 0x00000000
0x80000017 0x00000000 0x00000000 0x00000000 0x00000000
0x80000018 0x00000000 0x00000000 0x00000000 0x00000000

MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0xC0010114 0x00000000 0x00000018
MSR 0xC001001E 0x00000000 0x00000053
MSR 0xC0010015 0x00000000 0x02000040
MSR 0xC0010042 0x31041212 0x04180202
MSR 0xC0010041 0x00000001 0x00001202



Storage
-------------------------------------------------------------------------

USB Device USB Input Device, class=0x00, subclass=0x00, vendor=0x046D, product=0xC01E
USB Device USB Composite Device, class=0x00, subclass=0x00, vendor=0x06A3, product=0x8020

Graphic APIs
-------------------------------------------------------------------------

API NVIDIA I/O
API NVIDIA NVAPI

Display Adapters
-------------------------------------------------------------------------

Display adapter 0
Name NVIDIA GeForce 8800 GT
Revision A2
Codename G92
Technology 65 nm
PCI device bus 2 (0x2), device 0 (0x0), function 0 (0x0)
Vendor ID 0x10DE (0x1458)
Model ID 0x0611 (0x3472)

HW monitor Running at the same time.
April 26, 2011 10:21:15 PM

if its a gigabyte board then press control f1 in bios it will open up the hidden M.I.T menu.

your ram voltage of 1.9 will have no adverse effects other than heat 1s you open the hidden menu you will probably see all the latency settings and voltage controls.
you may want to check the settings of the ram on the box then set it that way in the M.I.T... did you download the cpu timer fix from amd? its called the amd dual core opromizer.
April 27, 2011 1:35:05 AM

Almost sounds like the mobo is borked. The one error... NV.... is nvidia related. I'd dig up the earliest driver for your opsys/card combo and try it. The netframework thing. go to windows update and if nothing there check microsoft site til you find it and run the patches. You can also try running 1 stick of memory in different slots.
April 27, 2011 2:27:37 AM

as said. the motherboard is brand new... sealed from the shop shelf about a week ago. the crashing problems existed before then also. so i am certain that isnt the problem.

I have also tried other RAM which didnt help. mine ran flawlessly in a friends computer and his didnt solve my problems so its not that either.

I will try a google search later for which is the most stable graphics driver for the 8800GT with windows 7 64... and hope that helps.

I can see why the thoughts are directed at the motherboard though, with both graphical and processor errors comming up thats the only thing linking them both.

I downloaded the dual core optimizer, installed it but not been able to find where it installed to... are there any settings with that i need to change? if not it didnt help.
April 27, 2011 12:15:34 PM

did you try ms-update ? and did you seek netframework or did you just blow that off ? try swapping hd ?
April 27, 2011 6:31:10 PM

windows says its up to date. installed every version of .netframework. and i dont have a HD i can try swapping with.

tried what are supposed to be the most stable graphics drivers and they didnt help either.
April 27, 2011 8:12:33 PM

the dual core optimizer just works when its installed. its a fire and forget program.
there are no settings for it. it will just increase stability.

all i can suggest now is to check your hardware. remove all ram using 1 stick at a time run prime 95 and see which 1 if any are causing the problems.
April 27, 2011 9:45:59 PM

ok ill give that a go
May 1, 2011 12:03:22 AM

sorry been busy for the last few days but i just had the mindset to take a look at my processor incase there was any visible dammage ect... and i noticed there is none of the thermal paste left... is there a possibility even a slight 1 of that being the cause of my issues?
May 1, 2011 2:28:57 AM

erm!!! yes!!!...
dont use your pc without having replaced the tim. or you will be saying bye bye to it.
May 3, 2011 7:14:05 PM

the thermal paste seems to have done the job atm. just played portal for about an hour and a half with no issues. thanks all :) 
May 5, 2011 7:20:04 AM

seems like he managed to find and fix is problem
January 11, 2013 9:43:00 AM

maybe by Magicka for example
i have on steam
i go to the map

Program files than Steam
Steamapps than Common
Magicka than Dependencies map

In that map there is a exe.file
xnafx31_redist that is that you must instal for playing magicka

look at the maps where it hides look for this and install this file
xnafx31_redist it is in the game map Magicka

i hoop it works
Bye :hello: 
!