BSOD help needed

edilee012 · 30 Nov 2010

I have had a couple blue screens the last couple days which I believe to be driver related...specifically Nvidia video card drivers. Check the attached files to see what you might be able to get out of them.

My problem is when I installed the latest Nvidia drivers (260.99) I get long delays for the video (graphics cards and monitor) to become active after resuming from sleep. These delays range from 3-5 minutes which is not normal since the previous driver set (258.96) operated normal and the monitor came up withing a few seconds of resuming from sleep mode.

I have did the extensive driver removal procedure and reverted back to the 258.96 set but the problem that started with the newer set remained with the older drivers back on my machine. I used the driver sweeper method in safe mode, etc, etc so I have done everything I know to get rid of this problem.

The BSOD's started yesterday when I attempted a more extensive method of driver removal which involved manually deleting some Nvidia folders but this did not help I am still stuck with the long delay and NOW blue screens that have happened at random times.

Files are attached so let me know what you see in them.

OS-Win 7 64bit-fresh install at 7's release date
Custom built PC-will add specs if they aren't there but ask if need more info

zigzag3143 · 01 Dec 2010

edilee012 said:

I have had a couple blue screens the last couple days which I believe to be driver related...specifically Nvidia video card drivers. Check the attached files to see what you might be able to get out of them.

My problem is when I installed the latest Nvidia drivers (260.99) I get long delays for the video (graphics cards and monitor) to become active after resuming from sleep. These delays range from 3-5 minutes which is not normal since the previous driver set (258.96) operated normal and the monitor came up withing a few seconds of resuming from sleep mode.

I have did the extensive driver removal procedure and reverted back to the 258.96 set but the problem that started with the newer set remained with the older drivers back on my machine. I used the driver sweeper method in safe mode, etc, etc so I have done everything I know to get rid of this problem.

The BSOD's started yesterday when I attempted a more extensive method of driver removal which involved manually deleting some Nvidia folders but this did not help I am still stuck with the long delay and NOW blue screens that have happened at random times.

Files are attached so let me know what you see in them.

OS-Win 7 64bit-fresh install at 7's release date
Custom built PC-will add specs if they aren't there but ask if need more info

Several Problems

1-ASACPI.SYS used in alcohol120 and daemon tools.

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- NETIO.sys. usually caused by one Alarm. Remove and replace with Microsoft Security Essentials and win 7 firewall.

http://download.zonealarm.com/bin/fr...cpes_clean.exe

http://www.microsoft.com/security_essentials/

3-Kaspersky caused these three so remove it as well.

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\113010-27253-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\symbols;srv*e:\symbols
*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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Tue Nov 30 19:38:41.621 2010 (GMT-5)
System Uptime: 1 days 1:21:02.649
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001bf6238, fffff880039b62c8, fffff880039b5b30}

Probably caused by : kl1.sys ( kl1+1bd238 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001bf6238, The address that the exception occurred at
Arg3: fffff880039b62c8, Exception Record Address
Arg4: fffff880039b5b30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
kl1+1bd238
fffff880`01bf6238 ff9684020000    call    qword ptr [rsi+284h]

EXCEPTION_RECORD:  fffff880039b62c8 -- (.exr 0xfffff880039b62c8)
ExceptionAddress: fffff88001bf6238 (kl1+0x00000000001bd238)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880039b5b30 -- (.cxr 0xfffff880039b5b30)
rax=0000000000000000 rbx=00000000000000c9 rcx=00000000fffffa80
rdx=0000000000000016 rsi=fffffa800a20f520 rdi=0000000000000016
rip=fffff88001bf6238 rsp=fffff880039b6500 rbp=fffff880039b66d0
 r8=fffff880039b66d0  r9=0000000000000000 r10=000043502d454944
r11=fffff880039b6628 r12=fffffa8007707a40 r13=00000000000000c9
r14=fffffa8007707a40 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
kl1+0x1bd238:
fffff880`01bf6238 ff9684020000    call    qword ptr [rsi+284h] ds:002b:fffffa80`0a20f7a4=0a20f7a0fffffa80
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
kl1+1bd238
fffff880`01bf6238 ff9684020000    call    qword ptr [rsi+284h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffffa800a20f520 to fffff88001bf6238

STACK_TEXT:  
fffff880`039b6500 fffffa80`0a20f520 : fffff880`039b66d0 00000000`000000c9 00000000`00000016 00000000`00000000 : kl1+0x1bd238
fffff880`039b6508 fffff880`039b66d0 : 00000000`000000c9 00000000`00000016 00000000`00000000 00000000`00000004 : 0xfffffa80`0a20f520
fffff880`039b6510 00000000`000000c9 : 00000000`00000016 00000000`00000000 00000000`00000004 00000000`000000c9 : 0xfffff880`039b66d0
fffff880`039b6518 00000000`00000016 : 00000000`00000000 00000000`00000004 00000000`000000c9 00000000`000000c9 : 0xc9
fffff880`039b6520 00000000`00000000 : 00000000`00000004 00000000`000000c9 00000000`000000c9 fffff880`039b6658 : 0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  kl1+1bd238

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kl1

IMAGE_NAME:  kl1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0f985b

STACK_COMMAND:  .cxr 0xfffff880039b5b30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_kl1+1bd238

BUCKET_ID:  X64_0x7E_kl1+1bd238

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

4-Old drivers
These seriously need updating

Code:

RTCore64.sys        fffff880`0aabc000    5/25/2005 01:39:12    fffff880`0aac2000    0x42941d90    0x00006000                        
pcouffin.sys        fffff880`05e77000    12/5/2006 09:39:30    fffff880`05e8b380    0x457584a2    0x00014380                        
SiWinAcc.sys        fffff880`011a8000    6/14/2007 19:02:02    fffff880`011b1000    0x4671d6fa    0x00009000                        
SiRemFil.sys        fffff880`0168d000    6/20/2007 14:42:10    fffff880`01695000    0x46798312    0x00008000                        
ADIHdAud.sys        fffff880`0654d000    8/15/2007 16:28:53    fffff880`065ba000    0x46c37015    0x0006d000                        
SI3132.sys        fffff880`010f4000    10/3/2007 13:39:29    fffff880`0110e000    0x4703e1e1    0x0001a000                        
spldr.sys        fffff880`01685000    5/11/2009 11:56:27    fffff880`0168d000    0x4a0858bb    0x00008000                        
amdxata.sys        fffff880`0113d000    5/19/2009 12:56:59    fffff880`01148000    0x4a12f2eb    0x0000b000                        
nvstor.sys        fffff880`00c00000    5/20/2009 01:45:37    fffff880`00c2b000    0x4a13a711    0x0002b000

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

edilee012 · 02 Dec 2010

Thanks for the quick reply and I have been looking at certain items that were suggested.

I forgot to update the ATK thing on this last fresh re-install...woops...but it is updated now but that is an item for use with the Asus AIBooster which I do not use but I guess if it can cause BSOD then best to have it current. Not sure if the the ASACPI.sys was related to the ATK driver in your reply but I don't have daemon tools or alcohol 120 installed and they have never have been installed.

NETIO.sys-I have never used Zone Alarm either but I do have SuperAntispyware or something like that installed which I never use so I will uninstall it. More than likely that is what this file is related to.

Kaspersky-I just renewed for another year so unfortunately at this time I will have to leave it installed BUT I am awaiting an updated version that could possibly fix any issues it could be causing.

The BSOD's I mentioned happened the day and day before I posted this topic and other than those I have never had a blue screen on this PC since I built it 3 years ago. I haven't had anymore blue screens since posting maybe it was a random event but I am keeping an eye on it.

I am also going through that driver list and seeing if any updates to them are available and so far no luck. The RTcore64.sys I was able to locate as part of my EVGA Precision program for overclocking and fan control on my video cards and the version installed is a few weeks old so I am at a loss as to why that driver is so old unless it is just a standard file they use in each version that is not in need if an update yet.