hi everyone. I really need help with this because i have an exam coming up and i need to get my computer back to normal. Im a complete newb at all computer terminology and my attempts to fix it myself have failed because of that. My problem is that whenever i boot up my netbook, it goes to the bsod and ive already tried restoring and all that but it still hasnt worked. I can only start up my computer through safe mode and safe mode with networking but i cant start it up normally. I attached some files that i hope will help and please help me out asap. thanks. also, in case you guys need it im pretty sure im running a 32 bit windows 7 os. i bought my computer a couple of months ago and havent installed or reinstalled any other os s.
Easy your trend micro AV. It caused them all. Remove and replace with Microsoft security essentials.
http://www.microsoft.com/security_essentials/
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\092810-19983-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x81a42000 PsLoadedModuleList = 0x81b8a810
Debug session time: Tue Sep 28 19:55:07.582 2010 (GMT-5)
System Uptime: 9 days 11:59:57.467
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 1, a702bac8, 0}
Unable to load image \SystemRoot\system32\DRIVERS\tmwfp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tmwfp.sys
*** ERROR: Module load completed but symbols could not be loaded for tmwfp.sys
Probably caused by : tmwfp.sys ( tmwfp+20798 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 00000001, The address that the exception occurred at
Arg3: a702bac8, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+12a
00000001 ?? ???
TRAP_FRAME: a702bac8 -- (.trap 0xffffffffa702bac8)
ErrCode = 00000010
eax=837f74dc ebx=b1bd5000 ecx=00000001 edx=000000e6 esi=837f74b0 edi=00000003
eip=00000001 esp=a702bb3c ebp=a702bba4 iopl=0 nv up ei pl zr ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010257
00000001 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: TmPfw.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 866c63c6 to 00000001
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
a702bb38 866c63c6 837f74b0 00000000 b1bd5440 0x1
a702bba4 a9c33798 837f74b0 00000000 b1bd5440 tcpip!WfpAleCompleteOperation+0x146
a702bbb8 a9c34738 b1bd5440 84076244 00000000 tmwfp+0x20798
a702bbdc a9c2f3c8 834095e8 8331bb50 00000000 tmwfp+0x21738
a702bbfc 81a7e4bc 8331bb50 b3f71008 b3f71008 tmwfp+0x1c3c8
a702bc14 81c7ff6e 834095e8 b3f71008 b3f71078 nt!IofCallDriver+0x63
a702bc34 81c9cd5f 8331bb50 834095e8 00000000 nt!IopSynchronousServiceTail+0x1f8
a702bcd0 81c9f53a 8331bb50 b3f71008 00000000 nt!IopXxxControlFile+0x6aa
a702bd04 81a8544a 0000013c 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
a702bd04 77bf64f4 0000013c 00000000 00000000 nt!KiFastCallEntry+0x12a
00b5fdfc 00000000 00000000 00000000 00000000 0x77bf64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
tmwfp+20798
a9c33798 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: tmwfp+20798
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tmwfp
IMAGE_NAME: tmwfp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a794c6d
FAILURE_BUCKET_ID: 0x8E_tmwfp+20798
BUCKET_ID: 0x8E_tmwfp+20798
Followup: MachineOwner
---------
0: kd> lmvm tmwfp
start end module name
a9c13000 a9dbd000 tmwfp T (no symbols)
Loaded symbol image file: tmwfp.sys
Image path: \SystemRoot\system32\DRIVERS\tmwfp.sys
Image name: tmwfp.sys
Timestamp: Wed Aug 05 05:10:05 2009 (4A794C6D)
CheckSum: 00047515
ImageSize: 001AA000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Quote