10 replies to this topic

[roflplanes]

Alright, I'm going to apologize in advance. I've been experiencing a BSOD that only occurs when I run MW:O and am trying to troubleshoot it. I'm currently at work and can't actually PLAY, but I'm going to be running the game minimized on my machine to recreate the crashes for configuration testing.

If you see me in-game sitting at spawn doing nothing in a trial 'Mech, please don't report me for farming becasue I'm really not. I just spent a pretty penny on some nice memory that I'm about to return after work today and I'm trying to exhaust all software options and fixes before I drive a half-hour in the wrong direction to hit my "local" MicroCenter...

Thanks for understanding and again, I'm REALLY sorry to anyone who might end up on my team!

[sycocys]

What are the details on your video card? I'm going to initially guess that it is the culprit of having too little vram.

[Joseph Mallan]

We got your back ROFL.

[roflplanes]

Here's my original thread on the issue if you want to take a look and throw me pointers!

http://mwomercs.com/...64#entry1931264

And I thought that as well but my sheisty Insyde BIOS won't let me change ANY really useful settings........ Any pointers or suggestions are appreciated though! Thanks again guys!

[Voridan Atreides]

No probs.

[Henchman 24]

roflplanes...your first post makes me wonder whether or not you got a bad stick of mem when you upgraded.

I've seen this sort of thing happen too, new upgrade of ram, everything is fine until some app/game actually addresses a region above what you were using before and bam....bsod.

Try running memtest86+ (v4.20 currently) at boot if you can.

If you can't get your hands on a bootable memtest86+ disc(many recent linux distros have them on their boot menu if you interrupt initial boot with a key)...then remove one stick (I'm assuming you're at 2x8g in a laptop) and see what happens. If you can replicate, swap the sticks and try again....if you still have the same results, then I would most likely rule out faulty memory.

However, this doesn't rule out that your particular mobo/bios may not like your chosen ram either. And with no settings to loosen timings, etc...it's not like you could adjust a problem away.

The sad part is, you are trying to run this game on Intel HD graphics...and that will cause just as much headaches.

good luck

[roflplanes]

Henchman 24, on 22 February 2013 - 09:41 AM, said:

roflplanes...your first post makes me wonder whether or not you got a bad stick of mem when you upgraded.

I've seen this sort of thing happen too, new upgrade of ram, everything is fine until some app/game actually addresses a region above what you were using before and bam....bsod.

Try running memtest86+ (v4.20 currently) at boot if you can.

If you can't get your hands on a bootable memtest86+ disc(many recent linux distros have them on their boot menu if you interrupt initial boot with a key)...then remove one stick (I'm assuming you're at 2x8g in a laptop) and see what happens. If you can replicate, swap the sticks and try again....if you still have the same results, then I would most likely rule out faulty memory.

However, this doesn't rule out that your particular mobo/bios may not like your chosen ram either. And with no settings to loosen timings, etc...it's not like you could adjust a problem away.

The sad part is, you are trying to run this game on Intel HD graphics...and that will cause just as much headaches.

good luck

Already tried memtest86 and memtest86+, no errors found. Considered the bad sticks, and am returing them today for another set. I was just hoping to avoid the drive by finding a software issue... Thanks for the assist though! I've got a suggestions thread going on at the link above if you want to check my crash dumps!

Thanks again guys, this community is the shiznit.

[Kraven Kor]

Memtest is kind of terrible at testing modern ram, it seems.

Does your system have an on-board memory diagnostic?

What are the details of the BSOD?

[roflplanes]

Kraven Kor, on 22 February 2013 - 10:12 AM, said:

Memtest is kind of terrible at testing modern ram, it seems.

Does your system have an on-board memory diagnostic?

What are the details of the BSOD?

Tried both the onboard Windows one AND the onboard Ubuntu 12.10 one. All came back clean.

The details of the BSODs are EXTREMELY varied except for the common denominator being the ntoskrnl.exe file. Pasting a copy of my last dumps (since my Windows reinstall yesterday) in the next post!

Crash Dump Analysis

[color="#000000"]Crash dump directory: C:\windows\Minidump[/color]

[color="#000000"]Crash dumps are enabled on your computer.[/color]

[color="#000000"]On Fri 2/22/2013 5:28:23 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022213-18953-01.dmp
This was probably caused by the following module: [color="#000000"]ntoskrnl.exe[/color] (nt+0x7A040)
Bugcheck code: 0x1 (0x7702C90A, 0x0, 0x20000, 0xFFFFF880113F5B80)
Error: [color="#000000"]APC_INDEX_MISMATCH[/color]
file path: C:\windows\system32\ntoskrnl.exe
product: [color="#000000"]Microsoft® Windows® Operating System[/color]
company: [color="#000000"]Microsoft Corporation[/color]
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/color]



[color="#000000"]On Fri 2/22/2013 5:28:23 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: [color="#000000"]ntkrnlmp.exe[/color] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1 (0x7702C90A, 0x0, 0x20000, 0xFFFFF880113F5B80)
Error: [color="#000000"]APC_INDEX_MISMATCH[/color]
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/color]



[color="#000000"]On Fri 2/22/2013 4:08:36 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\022213-18250-01.dmp
This was probably caused by the following module: [color="#000000"]dxgkrnl.sys[/color] (dxgkrnl+0x4EBA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004256BA0, 0xFFFFF8800EC44D90, 0x0)
Error: [color="#000000"]SYSTEM_SERVICE_EXCEPTION[/color]
file path: C:\windows\system32\drivers\dxgkrnl.sys
product: [color="#000000"]Microsoft® Windows® Operating System[/color]
company: [color="#000000"]Microsoft Corporation[/color]
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. [/color]



[color="#000000"]On Fri 2/22/2013 1:03:30 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022113-26187-01.dmp
This was probably caused by the following module: [color="#000000"]igdkmd64.sys[/color] (0xFFFFF88004C00C68)
Bugcheck code: 0xD1 (0x486D458, 0x2, 0x0, 0xFFFFF88004C00C68)
Error: [color="#000000"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/color]
file path: C:\windows\system32\drivers\igdkmd64.sys
product: [color="#000000"]Intel Graphics Accelerator Drivers for Windows 8®[/color]
company: [color="#000000"]Intel Corporation[/color]
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: [color="#000000"]Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL[/color][/color]



[color="#000000"]On Fri 2/22/2013 12:02:59 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\022113-37140-01.dmp
This was probably caused by the following module: [color="#000000"]ntoskrnl.exe[/color] (nt+0x7A040)
Bugcheck code: 0x7F (0x8, 0xFFFFF880009A1DB0, 0x0, 0xFFFFF801E5534B1C)
Error: [color="#000000"]UNEXPECTED_KERNEL_MODE_TRAP[/color]
file path: C:\windows\system32\ntoskrnl.exe
product: [color="#000000"]Microsoft® Windows® Operating System[/color]
company: [color="#000000"]Microsoft Corporation[/color]
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [/color]

[Kraven Kor]

The IRQL_NOT_LESS_OR_EQUAL is usually a driver issue:

See http://answers.micro...c230b20a?page=2

The common causes seem to be a corrupt driver (from a recent driver update), a corrupted or invalid BIOS version (from a recent BIOS or firmware update), or Norton software.

The APC Mismatch entry is generally tied to bad RAM.

Has your system been overheating? Might want to just try "re-seating" your memory and add in cards - turn system off, ground yourself, and then remove and re-install all memory sticks and your add-in cards.

[roflplanes]

Just swapped my cards for a pair of Vengance cards with a lower latency. My motherboard seems happier so far, but I'm playing tomorrow night and I'll let you know. Thanks for the help though!