Vista SP1 BSOD's?

LightningRider

Senior member
Feb 16, 2007
558
0
0
Lately I've been having some weird issues with random BSODs every one in a while. They are pretty intermittent so they don't really bother me that much, but I'd still like to know what's causing them.

They usually only happen on start up or shutdown of the system and the message is usually the famous IRQL_NOT_LESS_OR_EQUAL. Sometimes I get the message saying ntfs.sys was responsible.

I've run memory diagnostics and everything passes. I've also tried installing my OS on multiple drives once I saw the ntfs.sys message since I thought it might be a defective hard drive. Different drives seem to have it happen in different frequencies but it could be just completely random. It seems that it happened a lot more with my Samsung F1 1TB though before I replaced it thinking it was defective because of the BSODs.

I've also read that my keyboard, Logitech G15's driver has a known issue with Vista SP1 and that a BSOD may sometimes occur on start up or shutdown. Strangely though when this happens it is supposed to reset your G15's settings, which never happens to me, leading me to think this is not my issue.

The only other thing I can think of is that it is either my motherboard (which I doubt), or Microsoft has brought on new driver bugs with their SP1 for Vista. I'm wondering if anyone else has had this sort of issue or has experienced any new problems with SP1. I seem to have only gotten these issues since I installed Vista SP1 almost a month and half ago. That's why I think that these issues may not be my machine's fault. If this is the case, I guess I have no choice but to wait on Microsoft to release a patch (if they ever do).

I know that's a lot of stuff but you don't have to read all of it to understand my issue.

Basically: Does anyone have any recent issues with SP1 on their Vista machines (BSODs)?
 

mb

Lifer
Jun 27, 2004
10,233
2
71
Basically: Does anyone have any recent issues with SP1 on their Vista machines (BSODs)?

Haven't had a single problem since the betas when nvidia still had immature drivers. 0 problems since RTM.

Nice PC, BTW :)
 

soonerproud

Golden Member
Jun 30, 2007
1,874
0
0
Try uninstalling the keyboard software and drivers first. If that doesn't work then hook another keyboard up to the computer and see if you still have the same issue. That is about the best way to determine if it really is the keyboard.

 

LightningRider

Senior member
Feb 16, 2007
558
0
0
For some reason I don't think it is the G15 though as my settings never get deleted.

Here's the minidump trace if anyone's interested:


NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904aa
Arg2: fffffa600cf8f898
Arg3: fffffa600cf8f270
Arg4: fffffa600101e6a3

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


EXCEPTION_RECORD: fffffa600cf8f898 -- (.exr 0xfffffa600cf8f898)
ExceptionAddress: fffffa600101e6a3 (Ntfs!NtfsSetCcbAccessFlags+0x0000000000000023)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008

CONTEXT: fffffa600cf8f270 -- (.cxr 0xfffffa600cf8f270)
rax=fffffa8004020f68 rbx=fffffa600e3c8c70 rcx=0000000000000000
rdx=fffffa8004020c10 rsi=fffffa8004020c10 rdi=fffffa600e3c8c70
rip=fffffa600101e6a3 rsp=fffffa600cf8fad0 rbp=fffffa8004020c10
r8=fffffa600e3c8c70 r9=0000000000000000 r10=0000000000000000
r11=fffff80001e80640 r12=fffffa8004020c10 r13=fffff88006b7c398
r14=fffffa600e3c8c70 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
Ntfs!NtfsSetCcbAccessFlags+0x23:
fffffa60`0101e6a3 4c8b4908 mov r9,qword ptr [rcx+8] ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e80080
0000000000000008

BUGCHECK_STR: 0x24

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffffa60010d9710 to fffffa600101e6a3

STACK_TEXT:
fffffa60`0cf8fad0 fffffa60`010d9710 : fffffa60`0e3c8c70 fffffa60`0e3c8c70 fffffa80`04020c10 fffffa60`6d4e6f49 : Ntfs!NtfsSetCcbAccessFlags+0x23
fffffa60`0cf8fb30 fffffa60`0101e10d : fffffa80`040f4ba0 fffffa80`04020c10 fffffa60`0e3c8c70 fffffa80`09399001 : Ntfs!NtfsCommonCreate+0x2109
fffffa60`0cf8fd30 fffff800`01ca6677 : fffffa60`0e3c8be0 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffffa60`0cf8fd60 fffff800`01ca662e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffffa60`0e3c8b00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


FOLLOWUP_IP:
Ntfs!NtfsSetCcbAccessFlags+23
fffffa60`0101e6a3 4c8b4908 mov r9,qword ptr [rcx+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Ntfs!NtfsSetCcbAccessFlags+23

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1

STACK_COMMAND: .cxr 0xfffffa600cf8f270 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsSetCcbAccessFlags+23

BUCKET_ID: X64_0x24_Ntfs!NtfsSetCcbAccessFlags+23

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