Too many BSODs

[slimbone]

I thought I had all my problems worked out. This is not the case. My computer was working fine. I installed most of my programs, surfin the web, doing what I do on my computers. So I shut it down for the night.

I turn it on the next day. BSOD. The first BSOD doesn't even have an error listed.

This BSOD happens a couple times.

Then I get a different BSOD saying APC_INDEX_MISMATCH. This one only shows up one time.

Then I get another saying SYSTEM_SERVICE_EXCEPTION. But I've already rolled back my ATI drivers to their original state. I try to run chkdsk /f but everytime the computer restarts it just goes back to the log in window, without running chkdsk.

I'm completely lost here. Where should I start?

 

[arges86]

well...
every BSOD has a minidump file that it puts into your C: drive
these can be viewed w/ the Windows Debugger

 

[slimbone]

What's Windows Debugger, and where do I find that? I think I'm just blind with rage right now.

 

[slimbone]

Here's the first one....


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112109-16208-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50
Debug session time: Sat Nov 21 10:27:01.486 2009 (GMT-6)
System Uptime: 0 days 0:01:47.781
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600014c671, fffff880088e0f60, 0}

Probably caused by : win32k.sys ( win32k!FreeInputContext+11 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600014c671, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880088e0f60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP:
win32k!FreeInputContext+11
fffff960`0014c671 488b9090020000 mov rdx,qword ptr [rax+290h]

CONTEXT: fffff880088e0f60 -- (.cxr 0xfffff880088e0f60)
rax=ffeff900c1cffc30 rbx=0000000000000000 rcx=fffff900c1e02450
rdx=fffff900c0401218 rsi=0000000077a12148 rdi=fffff900c1cffc30
rip=fffff9600014c671 rsp=fffff880088e1940 rbp=0000000000000001
r8=0000000000000003 r9=0000000000000000 r10=0000000000000000
r11=fffffa8004a56570 r12=fffff900c1cff010 r13=00000000000000ec
r14=fffff960003271b0 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
win32k!FreeInputContext+0x11:
fffff960`0014c671 488b9090020000 mov rdx,qword ptr [rax+290h] ds:002b:ffeff900`c1cffec0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: WerFault.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff9600014c671

STACK_TEXT:
fffff880`088e1940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!FreeInputContext+0x11


FOLLOWUP_IP:
win32k!FreeInputContext+11
fffff960`0014c671 488b9090020000 mov rdx,qword ptr [rax+290h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!FreeInputContext+11

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

STACK_COMMAND: .cxr 0xfffff880088e0f60 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!FreeInputContext+11

BUCKET_ID: X64_0x3B_win32k!FreeInputContext+11

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

 

[slimbone]

Here's one from earlier today.....



Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112209-14960-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Sun Nov 22 11:26:31.267 2009 (GMT-6)
System Uptime: 0 days 0:00:30.953
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002fb1282, fffff880033c4a48, fffff880033c42a0}

Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )

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


if I run the analyze on this, I get......


2: 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: fffff80002fb1282, The address that the exception occurred at
Arg3: fffff880033c4a48, Exception Record Address
Arg4: fffff880033c42a0, 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:
nt!CmpDelayDerefKCBWorker+d6
fffff800`02fb1282 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl

EXCEPTION_RECORD: fffff880033c4a48 -- (.exr 0xfffff880033c4a48)
ExceptionAddress: fffff80002fb1282 (nt!CmpDelayDerefKCBWorker+0x00000000000000d6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880033c42a0 -- (.cxr 0xfffff880033c42a0)
rax=fffffa80038a7090 rbx=0000000000000000 rcx=fffff8a001f6e6a8
rdx=0000000000000981 rsi=ffeff8a0000230d0 rdi=fffff8a001f6e5d0
rip=fffff80002fb1282 rsp=fffff880033c4c80 rbp=0000000000000001
r8=fffff8a000060c08 r9=000000000ac8ff2b r10=fffff8a003037de8
r11=fffffa80038a7040 r12=fffff80002ec4ee0 r13=fffff80002ec4f40
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!CmpDelayDerefKCBWorker+0xd6:
fffff800`02fb1282 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl ds:002b:ffeff8a0`00023c08=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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 fffff80002ef70e0
ffffffffffffffff

FOLLOWUP_IP:
nt!CmpDelayDerefKCBWorker+d6
fffff800`02fb1282 4038ae380b0000 cmp byte ptr [rsi+0B38h],bpl

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80002cce161 to fffff80002fb1282

STACK_TEXT:
fffff880`033c4c80 fffff800`02cce161 : fffff800`02fb11ac fffff800`02e645f8 fffffa80`038a7040 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xd6
fffff880`033c4cb0 fffff800`02f64166 : 00000560`00000000 fffffa80`038a7040 00000000`00000080 fffffa80`03897040 : nt!ExpWorkerThread+0x111
fffff880`033c4d40 fffff800`02c9f486 : fffff880`03164180 fffffa80`038a7040 fffff880`0316efc0 00000560`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033c4d80 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`033c49f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpDelayDerefKCBWorker+d6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

STACK_COMMAND: .cxr 0xfffff880033c42a0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayDerefKCBWorker+d6

BUCKET_ID: X64_0x7E_nt!CmpDelayDerefKCBWorker+d6

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

 

[slimbone]

This is the last dmp from earlier today, when I tried to shutdown/restart my computer.....



Loading Dump File [C:\Windows\Minidump\112209-18876-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Sun Nov 22 11:44:18.757 2009 (GMT-6)
System Uptime: 0 days 0:01:55.053
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002cf54a0, fffff880033b6578, fffff880033b5dd0}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetNext+5b )

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

3: 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: fffff80002cf54a0, The address that the exception occurred at
Arg3: fffff880033b6578, Exception Record Address
Arg4: fffff880033b5dd0, 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:
nt!ExfAcquireRundownProtection+0
fffff800`02cf54a0 488b01 mov rax,qword ptr [rcx]

EXCEPTION_RECORD: fffff880033b6578 -- (.exr 0xfffff880033b6578)
ExceptionAddress: fffff80002cf54a0 (nt!ExfAcquireRundownProtection)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff880033b5dd0 -- (.cxr 0xfffff880033b5dd0)
rax=0000000000000002 rbx=ffeff8a00215a070 rcx=ffeff8a00215a080
rdx=0000000000000000 rsi=0000000000000000 rdi=ffeff8a00215a070
rip=fffff80002cf54a0 rsp=fffff880033b67b8 rbp=fffffa80047add80
r8=fffff8a002140080 r9=fffffa80044ed000 r10=0000000000401802
r11=fffff880033b67b0 r12=fffffa80047add78 r13=fffffa80046638b0
r14=00000000c00000bb r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!ExfAcquireRundownProtection:
fffff800`02cf54a0 488b01 mov rax,qword ptr [rcx] ds:002b:ffeff8a0`0215a080=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

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 fffff80002f070e0
ffffffffffffffff

FOLLOWUP_IP:
fileinfo!FIStreamGetNext+5b
fffff880`010e52e3 408af0 mov sil,al

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff880010e52e3 to fffff80002cf54a0

STACK_TEXT:
fffff880`033b67b8 fffff880`010e52e3 : fffff880`003b0017 00000b74`00000000 fffff8a0`02140070 00000000`00000002 : nt!ExfAcquireRundownProtection
fffff880`033b67c0 fffff880`010e5459 : fffff8a0`02140070 fffffa80`0567eab0 00000000`00000002 fffffa80`047add60 : fileinfo!FIStreamGetNext+0x5b
fffff880`033b67f0 fffff880`010e2563 : fffffa80`0567eab0 fffffa80`0567eab0 fffffa80`0567ea0c fffffa80`0567eab0 : fileinfo!FIEnumerate+0x135
fffff880`033b6870 fffff880`010e260b : fffff8a0`0225e670 fffff880`033b6a00 00000000`00000000 fffff880`033b6a00 : fileinfo!FIControlDispatchSystemControl+0x73
fffff880`033b68b0 fffff800`02f6b9b4 : fffffa80`046638b0 fffffa80`0567ea0c fffffa80`0567eab0 fffffa80`0567ea0c : fileinfo!FIControlDispatch+0x4b
fffff880`033b68f0 fffff800`0309c276 : 00000000`0000000c 00000000`0000000c 00000000`00000001 fffffa80`0567eab0 : nt!WmipForwardWmiIrp+0x16c
fffff880`033b6970 fffff800`0309cf2b : fffff880`033b6ad8 fffffa80`03814501 00000000`0000000c 00000000`00000000 : nt!WmipSendWmiIrpToTraceDeviceList+0xe6
fffff880`033b69d0 fffff800`030ad444 : fffffa80`03814200 00000000`00000001 fffff8a0`0225e670 fffffa80`038142c0 : nt!WmiTraceRundownNotify+0x6b
fffff880`033b6a20 fffff800`031184dc : 00000000`00401802 fffffa80`03814568 fffffa80`038142c0 fffff800`02cde2f2 : nt!EtwpKernelTraceRundown+0xc4
fffff880`033b6a50 fffff800`031185df : fffffa80`038142c0 00000000`00000002 fffff8a0`017b7c10 fffffa80`03814200 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`033b6b50 fffff800`02f2c8a9 : 00000000`00000000 fffff8a0`017b7c10 00000000`00000000 fffff800`02cf1d06 : nt!EtwpStopLoggerInstance+0x4f
fffff880`033b6b90 fffff800`03034600 : 00000000`00000000 00000000`00000002 fffffa80`038142c0 ffffffff`88ca6c00 : nt!EtwpStopTrace+0x129
fffff880`033b6c00 fffff800`0313f8e5 : ffffffff`ffffffff 00000000`00000001 ffffffff`000000b4 fffffa80`000005b8 : nt! ?? ::NNGAKEGL::`string'+0x5940c
fffff880`033b6c70 fffff800`02cde161 : fffff800`02e74500 fffff800`0313f720 fffff800`02e745f8 fffffa80`03863040 : nt!PerfDiagpProxyWorker+0x1c5
fffff880`033b6cb0 fffff800`02f74166 : 00000000`00000000 fffffa80`03863040 00000000`00000080 fffffa80`0382e5f0 : nt!ExpWorkerThread+0x111
fffff880`033b6d40 fffff800`02caf486 : fffff880`03164180 fffffa80`03863040 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033b6d80 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`033b66a0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: fileinfo!FIStreamGetNext+5b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME: fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc481

STACK_COMMAND: .cxr 0xfffff880033b5dd0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_fileinfo!FIStreamGetNext+5b

BUCKET_ID: X64_0x7E_fileinfo!FIStreamGetNext+5b

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

 

[slimbone]

Are all of these related to driver issues?

I put my Windows 7 disc in and did that fix problems thing, and I've had 2 more BSODs, one on shut down and one on start up. I ran chkdsk /f. and now I haven't had a BSOD in a while. "Knocks on wood."

Do you think I should just do another clean install of 7 before I have to activate my copy? I still have a couple days left. If I do that, should I create a new partition, install 7 on the new partition, then delete the old partition?

 

[arges86]

if you want to reinstall the OS, there is no harm in doing it right over the old one (since the installation will wipe whatever partition its using). Just make sure to save your data. BTW, you can reinstall the OS after you've activated it. That shouldn't be a problem.

I'm by no means an expert on debugging, but i don't think its a driver issue...
my recommendation is to wait and see if it BSODs again.
Chkdsk should really 'fix' anything. Its just checking your disk (in your case the F drive). If you want it to check your current drive just don't have any parameters set.

 

[slimbone]

The BSODs won't stop ahhhhhhh! I hate this damn computer.