New
#21
I got it running again. I just did another startup recovery and this time it worked. iTunes seems to be working just fine too. Who knows what the problem was.
K, here is all that was in there
I am also getting the BSOD whenever i open PC wizard by cpuid and click on the voltage, temp, and fans button.
that minidump was caused by tifm21.sys its a file for TI and is described here tifm21.sys Windows process - What is it?.
best bet to download and re-install the driver. If you dont know what it is let me know
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\090909-22448-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02804000 PsLoadedModuleList = 0xfffff800`02a41e50
Debug session time: Wed Sep 9 21:01:28.363 2009 (GMT-4)
System Uptime: 0 days 1:03:03.844
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa80c6a6f382, 1, fffff88003a08c20, 5}
Unable to load image \SystemRoot\system32\drivers\tifm21.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tifm21.sys
*** ERROR: Module load completed but symbols could not be loaded for tifm21.sys
Could not read faulting driver name
Probably caused by : tifm21.sys ( tifm21+8c20 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa80c6a6f382, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88003a08c20, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aac0e0
fffffa80c6a6f382
FAULTING_IP:
tifm21+8c20
fffff880`03a08c20 806002f5 and byte ptr [rax+2],0F5h
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: pcwizard.dll
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800909a3c0 -- (.trap 0xfffff8800909a3c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80c6a6f380 rbx=0000000000000000 rcx=0000000000000005
rdx=fffff88003a1f230 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003a08c20 rsp=fffff8800909a550 rbp=fffffa8006139010
r8=0000000000000000 r9=fffff8800909a5d0 r10=0000000000000000
r11=fffff8800909a880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
tifm21+0x8c20:
fffff880`03a08c20 806002f5 and byte ptr [rax+2],0F5h ds:6f49:fffffa80`c6a6f382=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028f3b91 to fffff80002875f00
STACK_TEXT:
fffff880`0909a258 fffff800`028f3b91 : 00000000`00000050 fffffa80`c6a6f382 00000000`00000001 fffff880`0909a3c0 : nt!KeBugCheckEx
fffff880`0909a260 fffff800`02873fee : 00000000`00000001 fffffa80`05fc8ad0 fffff8a0`02a63c00 fffff8a0`02a63ce0 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`0909a3c0 fffff880`03a08c20 : 00000000`0000001c fffff880`03a1f230 00000000`00000000 fffff880`0909a5d0 : nt!KiPageFault+0x16e
fffff880`0909a550 00000000`0000001c : fffff880`03a1f230 00000000`00000000 fffff880`0909a5d0 00000000`00000000 : tifm21+0x8c20
fffff880`0909a558 fffff880`03a1f230 : 00000000`00000000 fffff880`0909a5d0 00000000`00000000 00000000`00000000 : 0x1c
fffff880`0909a560 00000000`00000000 : fffff880`0909a5d0 00000000`00000000 00000000`00000000 00000000`00000000 : tifm21+0x1f230
STACK_COMMAND: kb
FOLLOWUP_IP:
tifm21+8c20
fffff880`03a08c20 806002f5 and byte ptr [rax+2],0F5h
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: tifm21+8c20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tifm21
IMAGE_NAME: tifm21.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47629fce
FAILURE_BUCKET_ID: X64_0x50_tifm21+8c20
BUCKET_ID: X64_0x50_tifm21+8c20
Followup: MachineOwner
---------
Ken