Windows 7: Windows 7 x64 BSOD KERNEL_DATA_INPAGE_ERROR

Urgo · 05 Sep 2010

Hello,
I've started getting bluescreens while playing certain games. It only happens when i'm playing those games, never else. ( Call of Duty Modern Warfare 2, Fallout 3 ).
I also play other games, but they never give me bluescreen. This is the BSOD i get:

Code:

KERNEL_DATA_INPAGE_ERROR      0x0000007a
Caused by Driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+70740

For more information i attached a zip with my minidump files.
I also ran Driver verifier and it gave me this:

Code:

DRIVER_VERIFIER_DETECTED_VIOLATION      0x000000c4
Caused by Driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+70740

I ran Memtest and checked HDD and all good. Please help! I really want to solve this.

Lomai · 05 Sep 2010

Hi Urgo

Welcome to Seven Forums
Have you tried updating those two games to the latest patches?

Urgo · 05 Sep 2010

Quote: Originally Posted by Lomai

Hi Urgo

Welcome to Seven Forums
Have you tried updating those two games to the latest patches?

Thank you, and yes, both games have the latest patches. Actually there's one more game that caused the same bluescreen. World of Tanks closed beta.
When i start playing, first it works very well for a few minutes. Then it can freeze for few seconds. Sometimes only audio freezes. Few minutes later the bluescreen appears.

Lomai · 05 Sep 2010

Hi
I'm gonna ask one of the BSOD experts to have a look at your dump-file.
In the mean-time, have a look at the following thread - may mention something that we have not considered

Tips on Troubleshooting Game Issues

Regards

richc46 · 05 Sep 2010

I have looked at your reports. You must have 25 or more dump reports going back for months. I have looked only at the last 10. These reports indicated the various codes

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
STOP 0x00000027: RDR_FILE_SYSTEM Usual causes: Insufficient physical memory, Indexing, Device driver

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\N5BQNVW9\Minidump[1]\090510-19500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0284b000 PsLoadedModuleList = 0xfffff800`02a88e50
Debug session time: Sat Sep  4 19:34:59.846 2010 (GMT-4)
System Uptime: 3 days 3:54:02.409
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fb80000000, ffffffffc000000e, 3e042880, fffff70000000000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c0e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb80000000, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000003e042880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff70000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
 
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c000000e
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  nvvsvc.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff8800317bf90 -- (.trap 0xfffff8800317bf90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000b7 rbx=0000000000000000 rcx=00000000000000b7
rdx=0000000000008000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002bd0651 rsp=fffff8800317c120 rbp=000007fffffdffff
 r8=fffff70000000000  r9=fffff70001080040 r10=8000000000000000
r11=fffffa8004176060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiFindEmptyAddressRange+0xc1:
fffff800`02bd0651 a10000000000f7ffff mov   eax,dword ptr [FFFFF70000000000h] ds:e060:fffff700`00000000=b8b6b7b4
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002930168 to fffff800028bb740
STACK_TEXT:  
fffff880`0317bc78 fffff800`02930168 : 00000000`0000007a fffff6fb`80000000 ffffffff`c000000e 00000000`3e042880 : nt!KeBugCheckEx
fffff880`0317bc80 fffff800`028ad52b : fffffa80`088b2010 fffff880`0317bdf0 fffffa80`041763f8 fffff880`0121c700 : nt! ?? ::FNODOBFM::`string'+0x34c0e
fffff880`0317bd60 fffff800`028d68bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`0317bf00 : nt!MiIssueHardFault+0x28b
fffff880`0317be30 fffff800`028b982e : 00000000`00000000 ffffffff`ffffffff fffff700`01080000 00000000`00000004 : nt!MmAccessFault+0x14bb
fffff880`0317bf90 fffff800`02bd0651 : 00000000`00000000 fffffa80`041be060 fffffa80`041be4a8 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0317c120 fffff800`02bbd804 : ffffffff`ffffffff ffffffff`ffffffff fffff880`0317c430 00000000`00002000 : nt!MiFindEmptyAddressRange+0xc1
fffff880`0317c190 fffff800`028ba993 : ffffffff`ffffffff fffff880`0317cad8 00000000`00000100 fffff880`0317c648 : nt!NtAllocateVirtualMemory+0x724
fffff880`0317c340 fffff800`028b6f30 : fffff800`02b84aa8 fffffa80`041763f8 fffff800`028f3ee2 00000000`00000023 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0317c548 fffff800`02b84aa8 : fffffa80`041763f8 fffff800`028f3ee2 00000000`00000023 00000000`00000000 : nt!KiServiceLinkage
fffff880`0317c550 fffff800`028ba993 : fffff880`0317c930 fffff800`028b993d 00000000`00000000 00000000`00001000 : nt!NtSetInformationProcess+0x7d7
fffff880`0317c8a0 fffff800`028b6f30 : fffff800`02b87c16 00000000`00000000 00000001`400000f0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0317ca38 fffff800`02b87c16 : 00000000`00000000 00000001`400000f0 00000000`00000000 fffff800`02bb4754 : nt!KiServiceLinkage
fffff880`0317ca40 fffff800`02b863f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00001000 : nt!RtlCreateUserStack+0x122
fffff880`0317cb30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateThread+0x29e
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34c0e
fffff800`02930168 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34c0e
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c0e
BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c0e
Followup: MachineOwner
---------

We cannot check everything so a decision has to be made as to what is the most likely cause. Since there are so many different BCs and they almost all indicate memory or driver. These are the two most likely suspects. Another clue is the number of different BCs that are present which normally indicates memory. May I suggest that you follow these instructions and take the memtest86

Download memtest86 and test RAM
RAM - Test with Memtest86+
If the memory test shows no errors take the driver verifier for 36 hours, so that the results will be meaninful.

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
Remember that several attempts may be required before we can solve your BSOD problem. These reports are not definitive but merely point the way to a solution.

Urgo · 05 Sep 2010

Thanks for your quick replies.
I already ran MemTest86 on Ultimate Boot Disk and it gave me 0 errors. When i enabled driver verifier, every time i logged in to windows, it gave me that DRIVER_VERIFIER_DETECTED_VIOLATION bsod.
This might help you determine the cause: I started playing that World of Tanks closed beta and when i play it, the BSOD happens ONLY at certain moment. Match begins with 25 seconds countdown. It works perfectly until the countdown is at 00:00. That's when the game freezes and gives BSOD.

richc46 · 05 Sep 2010

Well the driver verifier has to be used for 36 hours for a true picture and maybe you should try that game on another computer and see what happens. If its beta that is probably the problem, not the computer, the game.

Did you run the memtest for 6 passes, which is overnight?

Urgo · 06 Sep 2010

I just realised that i only get BSOD if i play games in fullscreen mode. If i changed to windowed, i never get BSOD.

Lomai · 06 Sep 2010

Hi Urgo

Have you tried updating your video card drivers - while at it, could you post a little more of your system specs?
Could you also download and update your directx to the current release - DirectX?

Keep us posted and regards

Urgo · 14 Dec 2010

Hi, and sorry for not posting for a long time.

Some of my previous problems have been solved but i've been getting many KERNEL_DATA_INPAGE_ERROR bsod recently. It only happens when playing games.
I have latest drivers, directx, i've checked hard disk and memory = no errors.

Yesterday when i was playing, suddenly my pc just turned off without any warning and i couldn't turn it on by clicking the power button. I unplugged power cable and replugged it and then tried clicking power button and then it worked.

I've checked all temperatures, they aren't too high.

( Few minutes before BSOD, my pc makes a sound that sounds like HDD or FAN stops spinning and start again )

PC SPECS:
OS: Windows 7 Ultimate 64-bit
CPU: Pentium Dual-Core E2500 2.50GHz ~3GHz
(CPU Overclocked 20%. Tried without overclocking and no change )
MEMORY: 3GB RAM
GPU: Nvidia GeForce GTS 250
MB: ASUS P5KPL-AM

new minidump files attached. Ignore the ones i sent before.

Any help is appreciated, please reply soon.

Windows 7: Windows 7 x64 BSOD KERNEL_DATA_INPAGE_ERROR

Windows 7 x64 BSOD KERNEL_DATA_INPAGE_ERROR problems?