Jump to content

Surael

Member
  • Content Count

    6
  • Joined

  • Last visited

  • Medals

Everything posted by Surael

  1. I tried causing another crash, but I didn't have any luck with previous methods. I only reinstalled my USB drivers, which makes me suspect that they had just corrupted or were damaged somehow at some point. I use a wired Razer Deathadder, because I hate wireless peripherals. I cannot stand the input latency. The thought that, perhaps A2 uses my mouse in a way that other programs do not, and thus is causing the crashes that way, did cross my mind. It does appear to be at least partially accurate, since the problem WAS found to be with the USB drivers, at least as far as we know now. I want to thank everyone who helped me through this issue directly. The prompt and informed posts are both a relief and a credit to this forum. I would like to mark this [sOLVED] if possible. If the problem returns, I will come back and update this thread. Thank you again!
  2. I've searched this forum for even vaguely related issues, but I've only found two threads regarding BSODs and Arma II: OA, one of which was locked and directed to the other, and the other was not a similar issue. I have also checked "if already posted," but do not expect my naming scheme to be common. About a week ago, I started playing Arma II: OA. Getting hooked on Day Z, I spent the next several days accumulating 50+ hours of playtime, without a single issue. Being that most, if not all, of my time had (up to this point) been wholly consumed by playing, no software or hardware changes were made to my machine. Around the 52-55 hour total playtime mark, I'm beginning my play session for the day and within 5 minutes, receive a blue screen. Not to be deterred, I ignored it and carried on. Stuff happens, right? Everything goes well until the next day, where I receive another the first time I start playing (again after a short time of playing perfectly). Now mildly concerned, but still undeterred, I continue playing until the next day, where the blue screens are continuous. One happens as normal, then every time I play for more than 3-5 minutes, crash. This includes playing the Single Player campaign, Multiplayer via Day Z (on multiple servers), and in various Boot Camp scenarios. I update my video drivers. Problem continues. I verify the OA integrity through Steam. One file (1.4kb) is downloaded each verification, so I figure it's nothing important. Problem continues. I reinstall Arma II. Problem...ceases. Until today. This is a .rar of all available related minidumps. tl;dr Arma II: OA blue screens consistently after 55 hours of problem-free play with no system changes occurring. Reinstalling Arma II fixes/reduces frequency for a few days (~10 hours playtime). Notes: 1. Some minidumps available here. 2. Crash only occurs while playing Arma II, Arma II: OA, and Arma II: Combined Operations. 3. Arma does not need to be active (can be minimized) for crash to occur. 4. Problem began before updating video drivers, continued after updating video drivers. System: Motherboard: ASUS M4A87TD EVO Processor: AMD Phenom II X4 965 (~3.4GHz) RAM: G.SKILL Ripjaws 2x2GB Video Card: GeForce GTX 460 (1GB, 256-bit, v301.42) OS: Windows 7 64-bit (6.1, B.7600) HDD: WD Black 500GB / 1TB
  3. I caused crash two, but it exhibited interesting tendencies that I have not seen before. I intended to take a photo of the blue screen, in case I could not get the information in time, so I went into the Armory and drove a vehicle around Chernarus for awhile with just my keyboard. After 10+ minutes of this, nothing had happened, so I decided to go back to boot camp and try the normal way. Within a minute (at the firing range using both keyboard and mouse), I caused another crash. This time, REFERENCE_BY_POINTER and BCCode 18 (or at least 0x00000018). This would lead me to believe that it's being caused at least in part by the mouse, or at least further suggests a USB issue. The reason I am reluctant to believe in that result is that A) the problems only exhibit with A2. B) If it were the mouse, playing Diablo III would surely trigger it as well, as I use the mouse more in that game than any other. I am running a System File Check, as per BoogieManFL's suggestion, and the results are available in the log file here. Additionally, after some research on the new error, I ran a basic memory diagnostic as well (mdsched.exe), and no errors were found. I can run memtest86+, but I don't expect it to get different answers. I checked on my motherboard drivers. Everything is still up to date, save my BIOS. I haven't updated my BIOS because I'm concerned with the possible danger it represents, but if it ends up being the solution, it must be better than going without. In the meantime, I will reinstall them (just in case) and incur another crash. EDIT: This is interestingly similar to the problem I had before, except that other games do not rarely cause the blue screen, but rather never cause it. The only other example would be ANNO 2070, which would cause the blue screen, and then after reboot, it would happen again after X amount of time, in which X got smaller with every successive reboot until I severed power entirely for several seconds. The current problem does not exhibit these behaviors, but the "cause" of the BSODs does seem to vary as they did before. I eventually RMA'd my motherboard for this and it worked fine when they sent it back.
  4. This is a composite of HWMonitor screenshots. 1 2 3 4 5 6 1. Idle temperatures with 4 Chrome tabs. 2. Arma II opened and loaded into Boot Camp. 3. 2 Minutes Later 4. ~2 Minutes Later 5. ~2 minutes later, the crash occurred. This is the initial reading immediately after restart (hence the window size.) 6. The same reading as 5, but resized and several (15-20) seconds later. I missed the error code, and it did not produce a minidump, but the offending file was usbohci.sys. Performing crash two.
  5. First time for everything. I've tried every other game on my system, some with higher system demands, some with lower, but no others cause this problem. I'm sincerely hoping it is caused by A2, because if it is not, it's a much more serious issue. I have performed stability tests in the past, and they have all passed perfectly, but this was several months ago. I will consider the tests as a last resort, due to the significant time investment, and shall hope it does not come to that.
×