My Computer actually was running fine. I went to Shut it down and it sometimes just restarts instead of fully shutting down. I installed it from a bootable flash drive and have had no other problems with the operating system so far. How can i fix this ? Its really annoying.
Try making a shortcut to c:/windows/system32/shutdown.exe and pin it to the taskbar. Use it and see if that helps...
ok. But i also get this blue screen with this description.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 91B2B23E
BCP3: 807CFB4C
BCP4: 807CF730
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\122209-27003-01.dmp
C:\Users\Ramon\AppData\Local\Temp\WER-41324-0.sysdata.xml
I believe something is wrong with my dsl adapters or technology. It sent me a message telling me to a dress a problem with 2wire which is my internet modem but i have no clue what it could be. It was working fine yesterday before i got windows 7.
Address a problem with xDSL
xDSL has stopped working properly.
This product is no longer supported by the manufacturer.
no.. zip the file up as usual, then open the quick reply and click on the paperclip ... this will open up a file browser from which you select the zipped .dmp file.. then click on the upload file, close the window and post your reply.. your .dmp file will then appear as an attachment that we can open....
ok thank you. I added it as an attachment.
Your .dmp file points to a bad driver (2WirePCP.sys) Go to their website and download/reinstall the driver...
Attachment 43103
Don Welcome
This one was caused by your 2wirePCP. It is from 2002. I cannot believe it hasnt given you more problems
I would
update all the older drivers listed
run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>fsc /scannow
Code:2WirePCP.sys 2WirePCP.sys+223e 0x91b29000 0x91b38580 0x0000f580 0x3d8f9a28 9/23/2002 5:48:08 PM secdrv.SYS 0x949f4000 0x949fe000 0x0000a000 0x45080528 9/13/2006 8:18:32 AM VSTCNXT3.SYS 0x91a1f000 0x91ad4000 0x000b5000 0x48f68ad9 10/15/2008 7:29:13 PM VSTAZL3.SYS 0x8ee77000 0x8eeb4000 0x0003d000 0x48f68b0b 10/15/2008 7:30:03 PM VSTDPV3.SYS 0x8eeb4000 0x8efb6000 0x00102000 0x48f68b84 10/15/2008 7:32:04 PM Rt86win7.sys 0x8d6cd000 0x8d6f2000 0x00025000 0x49a65b16 2/26/2009 4:04:22 AM igdkmd32.sys 0x8da1e000 0x8df1b000 0x004fd000 0x4a01d354 5/6/2009 1:13:40 PM spldr.sys 0x889f4000 0x889fc000 0x00008000 0x4a084ebb 5/11/2009 11:13:47 AM amdxata.sys 0x8820e000 0x88217000 0x00009000 0x4a12f30f 5/19/2009 12:57:35 PM athr.sys 0x8c423000 0x8c533000 0x00110000 0x4a2ea444 6/9/2009 1:04:52 PM hwpolicy.sys 0x8882d000 0x88835000 0x00008000 0x4a5bbf05 7/13/2009 6:11:01 PMGood luckCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\122209-27003-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82808000 PsLoadedModuleList = 0x82950810 Debug session time: Tue Dec 22 09:50:02.917 2009 (GMT-5) System Uptime: 0 days 0:07:53.758 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ...... Unable to load image \SystemRoot\system32\DRIVERS\2WirePCP.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for 2WirePCP.sys *** ERROR: Module load completed but symbols could not be loaded for 2WirePCP.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 91b2b23e, 807cfb4c, 807cf730} Probably caused by : 2WirePCP.sys ( 2WirePCP+223e ) Followup: MachineOwner --------- 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: c0000005, The exception code that was not handled Arg2: 91b2b23e, The address that the exception occurred at Arg3: 807cfb4c, Exception Record Address Arg4: 807cf730, 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: 2WirePCP+223e 91b2b23e f3a5 rep movs dword ptr es:[edi],dword ptr [esi] EXCEPTION_RECORD: 807cfb4c -- (.exr 0xffffffff807cfb4c) ExceptionAddress: 91b2b23e (2WirePCP+0x0000223e) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000001 Attempt to read from address 00000001 CONTEXT: 807cf730 -- (.cxr 0xffffffff807cf730) eax=00000042 ebx=85580f4c ecx=00000010 edx=00000042 esi=00000001 edi=864bf108 eip=91b2b23e esp=807cfc14 ebp=807cfc2c iopl=0 nv up ei pl nz na po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203 2WirePCP+0x223e: 91b2b23e f3a5 rep movs dword ptr es:[edi],dword ptr [esi] Resetting default scope CUSTOMER_CRASH_COUNT: 1 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: 00000000 EXCEPTION_PARAMETER2: 00000001 READ_ADDRESS: GetPointerFromAddress: unable to read from 82970718 Unable to read MiSystemVaType memory at 82950160 00000001 FOLLOWUP_IP: 2WirePCP+223e 91b2b23e f3a5 rep movs dword ptr es:[edi],dword ptr [esi] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from 91b2c97b to 91b2b23e STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 807cfc2c 91b2c97b 004c0001 864bf108 807cfc6c 2WirePCP+0x223e 807cfc94 91b33b34 85580e64 00000042 00000000 2WirePCP+0x397b 807cfcb8 91b357b3 00000000 86442004 8493dbfc 2WirePCP+0xab34 807cfd00 82875f2b 8493dbec 00000000 848485e8 2WirePCP+0xc7b3 807cfd50 82a1666d 00000000 a1274ec1 00000000 nt!ExpWorkerThread+0x10d 807cfd90 828c80d9 82875e1e 00000000 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: 2WirePCP+223e FOLLOWUP_NAME: MachineOwner MODULE_NAME: 2WirePCP IMAGE_NAME: 2WirePCP.sys DEBUG_FLR_IMAGE_TIMESTAMP: 3d8f9a28 STACK_COMMAND: .cxr 0xffffffff807cf730 ; kb FAILURE_BUCKET_ID: 0x7E_2WirePCP+223e BUCKET_ID: OLD_IMAGE_2WirePCP.sys Followup: MachineOwner ---------
Ken J+
Thank you Both Very Much ! I Noticed it actually shuts down correctly when i unplug the 2wire USb for my DSL so you yea its definitely the 2wire. How do i locate that file and uninstall it ? Or do i just go to the site and download new ones ? when i search for the files i cant find them. do i just delete the minidump files ?
Quote