BSOD Only When Gaming

#1
Hi all, great looking site you have here. I discovered it while tearing my hair out trying to look for a solution. Anyway, to the point.

Over the past two weeks I have had 4 BSODs. 1 around two weeks ago, and three in the last two days. I had two on the 14th so I updated to the latest ATI 10.10 but I had a BSOD again today.

I only had it with one game, unlike others, that was demanding on the PC. However, I had one with another game that was a predecessor so the engine was similar. I doubt it is an issue with any of the games.

I downloaded a tool called BlueScreenView and in all of the dump files ntoskrnl.exe was highlighted. One of them also had atikmdag.sys listed. That's ATI I'm guessing but I updated the drivers after that. I have read discussions about ATI being a major cause of BSOD.

I don't know what is exactly at fault (I would think GPU related) as I have seen discussions that blame all sorts.

PC (built myself):

- Windows 7 64-bit Home Premium
- Intel Core i7 920 D0 Stepping 2.66GHz
- 4870 512MB GDDR5
- Samsung SpinPoint F1 1TB SATA II 32MB cache
- 6GB RAM DDR3 PC3 (2GB sticks)
- Gigabyte GA-EX58-UD3R Intel X58 PCIE DDR3 Motherboard

Any help will be greatly appreciated.

Regards


Jimpy
 


Attachments

Last edited:
#2
Hi and welcome.

BSV is well...blah...not so much help usually and unprofessional.

Uninstall Kaspersky, as it is responsible for crashes.

Then replace with MSE.

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Temp\Rar$DI02.914\111610-20576-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e63000 PsLoadedModuleList = 0xfffff800`030a0e50
Debug session time: Tue Nov 16 13:28:23.038 2010 (UTC - 5:00)
System Uptime: 0 days 2:06:37.287
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80023006e80, 8, fffff80023006e80, 2}

Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys

Could not read faulting driver name
Probably caused by : klif.sys ( klif+29dc9 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80023006e80, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80023006e80, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b0e0
 fffff80023006e80 

FAULTING_IP: 
+68072faf019cde28
fffff800`23006e80 ??              ???

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031cbab0 -- (.trap 0xfffff880031cbab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005250004 rbx=0000000000000000 rcx=fffff8a00e3f5000
rdx=fffffa8005258a81 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80023006e80 rsp=fffff880031cbc48 rbp=fffff800030785f8
 r8=fffffa8005258a80  r9=0000000000000050 r10=fffff88002f63b80
r11=fffffa8005d43250 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`23006e80 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f528f2 to fffff80002ed3740

STACK_TEXT:  
fffff880`031cb948 fffff800`02f528f2 : 00000000`00000050 fffff800`23006e80 00000000`00000008 fffff880`031cbab0 : nt!KeBugCheckEx
fffff880`031cb950 fffff800`02ed182e : 00000000`00000008 fffff8a0`0e3f5000 fffffa80`08a11b00 fffff880`0108021f : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`031cbab0 fffff800`23006e80 : fffff880`01829dc9 fffffa80`05d43250 fffffa80`05200b60 00000000`20206f49 : nt!KiPageFault+0x16e
fffff880`031cbc48 fffff880`01829dc9 : fffffa80`05d43250 fffffa80`05200b60 00000000`20206f49 00000000`00000000 : 0xfffff800`23006e80
fffff880`031cbc50 fffffa80`05d43250 : fffffa80`05200b60 00000000`20206f49 00000000`00000000 fffffa80`06123cf0 : klif+0x29dc9
fffff880`031cbc58 fffffa80`05200b60 : 00000000`20206f49 00000000`00000000 fffffa80`06123cf0 fffff800`031cfc43 : 0xfffffa80`05d43250
fffff880`031cbc60 00000000`20206f49 : 00000000`00000000 fffffa80`06123cf0 fffff800`031cfc43 00000000`00000000 : 0xfffffa80`05200b60
fffff880`031cbc68 00000000`00000000 : fffffa80`06123cf0 fffff800`031cfc43 00000000`00000000 fffffa80`05aca0d0 : 0x20206f49


STACK_COMMAND:  kb

FOLLOWUP_IP: 
klif+29dc9
fffff880`01829dc9 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  klif+29dc9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: klif

IMAGE_NAME:  klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4afabce0

FAILURE_BUCKET_ID:  X64_0x50_klif+29dc9

BUCKET_ID:  X64_0x50_klif+29dc9

Followup: MachineOwner
---------
-------------

I'd update that Saitek driver too, from their website:


SaiH0464 SaiH0464.sys Fri Mar 28 13:19:58 2008

------------

Update Realtek LAN driver:

Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009

RTL8111


----------

Uninstall all motehrboard utilities such as EasyTune or Overdriver. Then check to see that these old problem drivers are gone from C:\Windows. Delete them if not:

gdrv gdrv.sys Fri Aug 08 14:28:54 2008
GVTDrv64 GVTDrv64.sys Tue Sep 05 03:10:02 2006

Code:
2: kd> lmvm gvtdrv64
start             end                 module name
fffff880`06b81000 fffff880`06b8b000   GVTDrv64   (deferred)             
    Image path: \??\C:\Windows\GVTDrv64.sys
    Image name: GVTDrv64.sys
    Timestamp:        Tue Sep 05 03:10:02 2006 (44FD22CA)
    CheckSum:         00014D8A
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> lmvm gdrv
start             end                 module name
fffff880`06b78000 fffff880`06b81000   gdrv       (deferred)             
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Fri Aug 08 14:28:54 2008 (489C9066)
    CheckSum:         00009D45
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
------------

Visit Logitech's site and update the drivers to all you have from them., You have oldies.

-------------

Enjoy.
 


#3
This link will update Realtek lan. The last one is broken and just brings you to their site:

Realtek
 


#4
You, sir, rock.

I've done everything bar replace Kaspersky. I haven't got much longer on the licence so I'll wait till it runs out.

Fingers crossed there's no more BSOD. I'll test it out tonight.

I have one question though. My GPU is OEM so when I built my computer I installed drivers from the ATI site. Would it be better to get the drivers from the manufacturers site (HIS) or the ATI site?
 


#5
Kaspersky is going to crash the machine more whether it be today, tomorrow, etc....

Nope, the best place to get the driver is always ATI's site as it's always the latest. HIS gets the drivers later and posts them later. No sense in going to their site at all.

Cool though. I have a HIS AGP HD 3850 factory overclocked that gets 7.1 rating in both WEI scores, if you can believe that. :)
 


#6
Lies. :p

Sorry to bother you all again but I had another BSOD.

I was happily playing Bad Company 2 without issue but I start the game I normally play, ArmA 2 Operation Arrowhead, only to have another BSOD. My PC seems to have fallen out with the Real Virtuality engine. Real Virtuality (game engine) - Wikipedia, the free encyclopedia

Kaspersky's going. Meanwhile here's the .dmp.
 


Attachments

#7
1. Follow TG's suggestion to remove Kaspersky, esp. that your version is outdated:

klif.sys Wed Nov 11 08:32:16 2009

Removal tool for Kaspersky Lab products



2. Update:

speedfan.sys Sun Sep 24 09:26:48 2006
Speedfan

SaiH0464.sys Fri Mar 28 13:19:58 2008
Saitek Configuration Software



3. Should crashes persist, uninstall hamachi:

hamachi.sys Thu Feb 19 05:36:41 2009
 


#8
Yep, uninstall Kaspersky and Hamachi, and update Saitek.

Speedfan with that driver is fine and known well. It's on my systems and they have months of uptimes and all bsod-free.
 


#9
Thanks again, will do.

How is it that you read the .dmp files? I would like to know and save bothering other folks.
 


#10
It's a very complicated process which takes months or even years to learn and become professional with. Knowledge of all software and all drivers that exist in the world, is key.

We use WinDbg.
 


#11
Ah, OK. I put one .dmp through it but I couldn't identify any files that you guys did. There's probably specific commands to put through?

I had one a couple of days ago but I hadn't removed my AV software so I didn't post it here. After I replaced it with MSE I continued on to see if another would pop up. It did (this time with a non-real virtuality based game engine. This one is a bit older (BF1942) so the age might have been an issue.

On the actual blue screen message, usbuhci.sys was mentioned. From what I can tell after a quick search is a windows USB driver.

A new ATI driver has been released which I am downloading now.

Is there good software out there for identifying drivers that need to be updated? Are they worth while?

Thank you both very much for your help so far.
 


Attachments

Last edited:
#12
Your issue is that Saitek not updated yet. If there is not an update, remove the hardware from the system and uninstall the driver/software to stop bsods.
 


#13
Hopefully Saitek updates them, there goes IL2.

Thanks.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top