As you might have understood from the post i have bluescreens quite often. Thought im also having game freezes during game play. And i dont know why. I've been in contact with the Nvidia support and they said the following:
Some of the possible reasons are:
1. Corrupted drivers
2. Issue could due to the OS.
3. Or, issue could be due to the other hardware components like motherboard, processor or system memory.
4. Defective graphics card.
Thought i've reinstalled my drivers (Removed them with Driver Sweeper). Repaired my OS a "couple" of times. And i dont get bluescreens when my computer is idle, only when im running something graphic "heavy".
- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
Yes
- an OEM or full retail version?
Full Retail
- What is the age of system (hardware)?
Everything apart from my Power supply is 2 years old and the power supply is 1½ year
- What is the age of OS installation (have you re-installed the OS?)
I resently repaired it with the Windows 7 repair tool but i have not reinstalled the os "properly" since i bought the computer.
Ok
Lets start here
1-SPTD.SYS. used by alcohol/daemon tools, is almost always a cause of BSOD's
ASACPI.sys Sun Mar 27 22:30:36 2005
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
2-Memory corruption--May be caused by spdt.sys or be bad itself run memtest
Download a copy of
Memtest86 and burn the ISO to a CD using
Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\111110-33212-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;srv*e:\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`02c1c000 PsLoadedModuleList = 0xfffff800`02e59e50
Debug session time: Thu Nov 11 12:06:08.726 2010 (GMT-5)
System Uptime: 1 days 5:51:21.334
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 89fff, 3, ac4ff}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
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: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000089fff, page frame number
Arg3: 0000000000000003, current page state
Arg4: 00000000000ac4ff, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Wow.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002d1c38c to fffff80002c8c740
STACK_TEXT:
fffff880`059b1818 fffff800`02d1c38c : 00000000`0000004e 00000000`00000099 00000000`00089fff 00000000`00000003 : nt!KeBugCheckEx
fffff880`059b1820 fffff800`02c3c5e8 : 00000000`00000001 00000000`00000001 fffffa80`019dffd0 fffff680`002abff8 : nt!MiBadShareCount+0x4c
fffff880`059b1860 fffff800`02cbd8e5 : fffffa80`07358b30 00000000`557ff000 92300000`2edd3c66 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x204da
fffff880`059b1970 fffff800`02cce0da : 00000000`00000000 00000000`558c1fff fffffa80`00000000 fffffa80`07358b30 : nt!MiDeleteVirtualAddresses+0x96c
fffff880`059b1b30 fffff800`02c8b993 : ffffffff`ffffffff 00000000`001ee2a0 00000000`001ee298 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`059b1c20 00000000`76d1ff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ee268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d1ff3a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`02d1c38c cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
---------
Other items of interest
Video driver-- re-install using these
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using
Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Let us know if you need further assistance
Ken
-
