So yesterday all my games ran fine
this morning, I wake up my machine (I left it on for a download) and try launching a Red Orchestra 2. The game freezes and says "rogame.exe has stopped working" before I reach the main menu.
Next game, Wargame:EE. I launch it, it gets to the main menu, then an access violation pops up after ~10 seconds.
Next game, Men of War: Assault Squad. Game receives an access violation before the main menu.
I'm running memtest right now
does anyone know what's going on?
Usually a problem with RAM or corrupted files
ran memtest86+ and it came out clean
however when MoW:AS and Wargame:EE crash they reference the same memory address ( (Reading 0x74b2616e))
[editline]9th December 2012[/editline]
is it still probable that my memory is bad, or could this be a disk/VRAM problem
also of note is that when I try to shut down my machine normally I get a DPC WATCHDOG VIOLATION
Do you have an SSD?
[QUOTE=djjkxbox360;38770015]Do you have an SSD?[/QUOTE]
nope, 1 TB western digital caviar black.
[QUOTE=trotskygrad;38765412]So yesterday all my games ran fine
(I left it on for a download)[/QUOTE]
May I ask what you were downloading? :P
Possibly some adult films embedded with a virus...
[QUOTE=awcmon;38783663]May I ask what you were downloading? :P
Possibly some adult films embedded with a virus...[/QUOTE]
Or just a game. And even if it was, malware can't make hardware issues.
[QUOTE=awcmon;38783663]May I ask what you were downloading? :P
Possibly some adult films embedded with a virus...[/QUOTE]
rising storm beta
right because a mod team would infect their testers
[QUOTE=Mike Tyson;38784060]Or just a game. And even if it was, malware can't make hardware issues.[/QUOTE]
If you VirtualProtect() random patches of memory, you might be able to achieve the same effect.
[quote]An attempt to read or write to the committed region results in an access violation.[/quote]
It's probably faulty memory though.
[QUOTE=Se1f_Distruct;38798980]If you VirtualProtect() random patches of memory, you might be able to achieve the same effect.
It's probably faulty memory though.[/QUOTE]
reinstalled win8 on a new hard disk, it might have been an issue with win8's install or something
not having any issues so far.
what's the chance of having faulty memory and it not showing up on memtest86+?
[QUOTE=trotskygrad;38816040]
what's the chance of having faulty memory and it not showing up on memtest86+?[/QUOTE]
Pretty small/none.
[QUOTE=kaukassus;38817617]Pretty small/none.[/QUOTE]
looks like it was hard drive corruption then
weird
Sorry, you need to Log In to post a reply to this thread.