Thread: l4d2 crashes computer

Originally Posted by jamgam

360safe was introduced to me from a friend which also plays l4d2 with no problem. I well try MalwareBytes and see if it helps. I tried l4d2 when i just built the computer so i dont think i got any malware but since im desperate to play ill give it a try. And the gamebooster did not help, i just played a game and my comp still crashed.

P.S i also have kaspersky internet security and so does my friend that has 360safe, but can an AV software crash your computer?

Anything is possible. Crashes are typically caused by conflicting programs or faulty hardware.

Originally Posted by jamgam

i scanned and got 3 files infected, i fixed it. I tried left4dead and still crashed. I tried fixing registry keys, but still crashing. I have no idea what causes my comp to crash.

Have you read through:

http://www.left4deadforums.com/3363-...e-posting.html

or

http://www.left4deadforums.com/19453...tic-guide.html

to see if anything there helps?

just a quick note regarding DEP... although dep wants you to specify an .exe file you can manually fill in the name of the .dll file instead.

Although typically exe's are the things the are executed, in this case it's a dll being loaded as an exectuable through rundll32 (or whatever win7 uses)

Originally Posted by jamgam

i reinstalled my windows and still crashing, i got nothing installed but the video card, steam, and left4dead2 so i dont think any anti-virus or other process is crashing my comp.
I get this error i wonder if it has to do with the crashing of my computer.

A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor ID: 0

The details view of this entry contains further information.

Then your problem is not with the game, your PC has other issues.

I Googled it, and there are others who have had the same problem.

Google

Good Luck!!

Originally Posted by jamgam

problem solved! My ram's timing were not correct so i had to manually change it myself in bios. Thanks anyways guys

Yea, that was one of the fixes listed in the google stuff.

Cheers!!