Please Urgent Blue Screen of Death

mattbroski · Dec 16, 2010

So i been having these blue screens of death lately and its rather frustrating it only happens when i play this game call soldier front i get to play like 1 or 2 games then i blue screen so i tried to look into it and this is what i have now i need help i really wanna fix this issue asap since i play for a national team any help is appreciated thank you.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000009A
BCP2: 00000000
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini121510-03.dmp
C:\Users\Titan\AppData\Local\Temp\WER-40497-0.sysdata.xml
C:\Users\Titan\AppData\Local\Temp\WERB1F0.tmp.version.txt

Code:

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


Loading Dump File [C:\Windows\Minidump\Mini121510-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82614000 PsLoadedModuleList = 0x8272bc70
Debug session time: Wed Dec 15 19:57:43.709 2010 (UTC - 5:00)
System Uptime: 0 days 4:35:47.367
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {9a, 0, 0, 0}

Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000009a, 
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x4E_9a

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 826aab94 to 826e1b0d

STACK_TEXT:  
984a8978 826aab94 0000004e 0000009a 00000000 nt!KeBugCheckEx+0x1e
984a8990 82690fb4 810b24d0 81177838 00000000 nt!MiBadRefCount+0x26
984a89e0 82694fdd 84871340 00000000 00000000 nt!MiWaitForInPageComplete+0x5e1
984a89f4 8281f1ad 00000000 b4a60010 b4a60000 nt!MiPfCompletePrefetchIos+0x1a
984a8a20 827b9a0e 00000001 984a8a6c 00000000 nt!MmPrefetchPages+0x1c3
984a8aac 827b9527 004a8aec 984a8be4 00000001 nt!PfpPrefetchFilesTrickle+0x1a3
984a8b00 827b97c4 b48f1000 f0000e49 984a8bf8 nt!PfpPrefetchRequestPerform+0x295
984a8b54 827ec150 984a8be4 00000001 f0000905 nt!PfpPrefetchRequest+0x16e
984a8c18 827fb497 0195f8e0 00000014 00000001 nt!PfSetSuperfetchInformation+0x182
984a8d50 8265ec7a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
984a8d50 775e5e74 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0195f8f8 00000000 00000000 00000000 00000000 0x775e5e74


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadRefCount+26
826aab94 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadRefCount+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  49e0199e

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x4E_9a_nt!MiBadRefCount+26

BUCKET_ID:  0x4E_9a_nt!MiBadRefCount+26

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

mattbroski · Dec 16, 2010

· OS - Vista/ Windows 7 ? Vista
· x86 (32-bit) or x64 ? 32 bit
· What was original installed OS on system? vista
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? pre-installed from dell i have the same cds they use
· Age of system (hardware) about 2 years
· Age of OS installation - have you re-installed the OS? yes 1 week ago
· CPU Dell Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz 2.20 GHz
· Video Card Nvidia GeForce GT 220
· MotherBoard Intel Core 2 Duo E4500
· Power Supply - 500w

Sorry here are my attachments View attachment Windows7_Vista_jcgriff2.zip

View attachment PerfmonReport.zip

mattbroski · Dec 17, 2010

still need help anyone :sigh:

jcgriff2 · Dec 17, 2010

Hi -

The bugchecks were the same on all 5 BSODs -

0x4e (0x9a,,,) = driver attempted to free a page that is still locked for I/O

I see "memory" written all over the dumps. Could be virtual memory (HDD - page file), RAM itself or other unknown hardware failure affecting RAMs ability to properly hold kernel code. The 4th possible cause - a rogue driver.

Update these drivers first -

Code:

[font=lucida console]
e1e6032.sys  Mon Oct 29 17:43:48 2007 (47265414) - Intel Ethernet

VSTDPV3.SYS  Tue Jun 20 13:41:01 2006 (4498332D) - Conexant soft 56k modem driver
VSTCNXT3.SYS Tue Jun 20 13:39:37 2006 (449832D9) - Conexant soft 56k modem driver
VSTBS23.SYS  Tue Jun 20 13:39:54 2006 (449832EA) - Conexant soft 56k modem driver

npptNT2.sys  Thu Jan 06 01:43:06 2005 (41DCDDFA) - nProtect GameGuard NPSC Kernel Mode Driver for NT

vcsvad.sys   Sun Nov 16 04:50:37 2008 (491FECED) - Avnex Ltd. Virtual Audio Device
[/font]

Driver Reference Table - http://sysnative.com/0x1/DriverReference.html

Then onto hardware diagnostics -
- Run memtest86+ - http://www.techsupportforum.com/2863029-post5.html
- Run HDD diags - http://www.techsupportforum.com/2828431-post7.html

If BSODs persist after driver updates and hardware tests are clean, run the Driver Verifier -

Driver Verifier - http://sysnative.com/0x1/driver_verifier.htm

Windbg Logs
--> http://sysnative.com/BSOD_2010/jcgriff2/_99-dbug_mattbroski_VistaSP2x86_12-17-2010_jcgriff2_.txt
--> http://sysnative.com/BSOD_2010/jcgriff2/_99-dbug_mattbroski_VistaSP2x86_12-17-2010_jcgriff2_.txt.zip

Regards. . .

jcgriff2

`

BSOD BUGCHECK SUMMARY

Code:

[font=lucida console]
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Wed Dec 15 19:57:43.709 2010 (GMT-5)
System Uptime: 0 days 4:35:47.367
Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000004E
Arguments 0000009a 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Wed Dec 15 15:07:08.643 2010 (GMT-5)
System Uptime: 0 days 1:21:47.733
Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000004E
Arguments 0000009a 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Wed Dec 15 13:44:48.204 2010 (GMT-5)
System Uptime: 0 days 3:21:31.648
Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000004E
Arguments 0000009a 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Dec 14 14:55:48.895 2010 (GMT-5)
System Uptime: 0 days 4:07:00.513
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+899fe )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  soldierfront.ex
Bugcheck code 0000004E
Arguments 0000009a 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Debug session time: Tue Dec 14 10:48:16.025 2010 (GMT-5)
System Uptime: 0 days 1:17:51.091
Probably caused by : memory_corruption ( nt!MiBadRefCount+26 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000004E
Arguments 0000009a 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

by [color=navy]jcgriff2     
             
         J. C. Griffith, Microsoft MVP[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   


           [url=www.sysnative.com][color=#000033][u]www.sysnative.com[/u][/color][/url]
             
           [url=www.jcgriff2.com][color=#000055][u]www.jcgriff2.com[/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]

Please Urgent Blue Screen of Death

Top Contributors this Month

Recommended Communities