|
|
|
|
|||||
|
|
|
|
|
|
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
 |
|
|
LinkBack | Thread Tools |
11-03-2009, 04:50 PM
|
#1 (permalink) |
|
Registered User
Join Date: Nov 2009
Posts: 10
OS: windows 7 RTM 1
|
Windows 7 = death >0
after upgrading to windows 7 RTM from vista, this is what has happened
1. random shutdowns. not like where it would say "please save your work" it would physically reset my computer to bios testing 2. i received this bsod error "0X0000009F: POWER_DEVICE_MANAGEMENT_FAILURE" 3. system lock up when loading desktop 4. system lock up while on desktop 5. invalid application extensions (.vbs and .C++) that would crash explorer.exe and just recently something weird BSOD CODE "0x00000000" i watch as the physical dump occurred and it when from 64% to 5% and my screen got glitchy also there was no explanation for it there was just a blank space. i have ran memtest, virusheck and found nothing  please help me |
|
     
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
11-03-2009, 06:07 PM
|
#2 (permalink) |
|
TSF Enthusiast
Join Date: Apr 2009
Location: Los Angeles
Posts: 2,676
OS: XP SP3, Vista SP2, Windows7
|
Re: Windows 7 = death >0
Go into the Bios and see if there is a section for SATA or Hard Drive. change the Hard Drive from AHCI mode to Compatibility mode or Legacy.
Or look here: Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state. Possible Resolutions: • Stop 0x9F messages can occur after installing faulty applications or drivers or system services. If a file is listed by name and you can associate it with an application, uninstall the application. For drivers, disable, remove, or roll back that driver to to determine if this resolves the error. If it does, contact the hardware manufacturer for a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, and CD mastering tools. • For information about troubleshooting standby and hibernate mode issues, see KB article Q266169, "How to Troubleshoot Problems with Standby Mode, Hibernate Mode, and Shutting Down Your Computer in Windows 2000."
__________________
Spike Baron A Plus, MCSE, MCAS (office 2007) MOUS, CNA |
|
|
|
|
11-03-2009, 08:19 PM
|
#3 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
 |
Re: Windows 7 = death >0
That last BSOD that you described looks very interesting... And that's quite the miscellaneous slew of problems.
Please follow the instructions here: http://www.techsupportforum.com/1871981-post2.html |
|
|
|
|
11-04-2009, 06:27 PM
|
#4 (permalink) |
|
Registered User
Join Date: Nov 2009
Posts: 10
OS: windows 7 RTM 1
|
Re: Windows 7 = death >0
here some files for you to look at i noticed something about an unknown driver in the report.html file
anyways i received another bsod containing this file: NVLDDMKM.SYS i think the first address code was 0X803F i am suspecting its my ram especially since when i was running vista i got bsod error 0X7F "MEMORY_MANAGEMENT" also bsod error "NTFS_FILESYSTEM" and a couple of "UNKNOWN_ HARD_ERROR" and "UNHANDED_KERNEL_EXCEPTION" plz. help. |
|
|
|
|
11-04-2009, 06:38 PM
|
#5 (permalink) |
|
Registered User
Join Date: Nov 2009
Posts: 10
OS: windows 7 RTM 1
|
Re: Windows 7 = death >0
sorry there is an upload error. please refer to this website:
http://sites.google.com/site/thesupercomputerproject/home/files |
|
|
|
|
11-04-2009, 06:49 PM
|
#6 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
|
Re: Windows 7 = death >0
...Is this a legitimate copy of Windows?
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Devin\AppData\Local\Temp\Rar$DI35.139\110309-37112-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0x82e13000 PsLoadedModuleList = 0x82f5b810
Debug session time: Tue Nov 3 15:41:17.483 2009 (GMT-5)
System Uptime: 0 days 0:00:51.512
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: c0000005
Arg2: 82ea21d9
Arg3: 9b11384c
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
ERROR: Could Not Find Target OS Version. Please Update GetFunctionForOSVer to include target OS Version
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: 82e13000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8b4e
FAULTING_IP:
nt+dbf28
82eeef28 cc int 3
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 82eeef28 (nt+0x000dbf28)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000001
NumberParameters: 0
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x0
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82ea207c to 82eeef28
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9b1133b4 82ea207c 0000008e c0000005 82ea21d9 nt+0xdbf28
9b1137dc 82e4bfe6 9b1137f8 00000000 9b11384c nt+0x8f07c
9b11384c 82ea21d9 badb0d00 00000018 bf7ed568 nt+0x38fe6
9b113cc4 82e4bfe6 9b113ce0 00000000 9b113d34 nt+0x8f1d9
9b113d34 775c512f badb0d00 00000057 00000000 nt+0x38fe6
9b113d38 badb0d00 00000057 00000000 00000000 0x775c512f
9b113d3c 00000000 00000000 00000000 00000000 0xbadb0d00
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+dbf28
82eeef28 cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+dbf28
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
|
|
|
|
|
11-05-2009, 02:36 PM
|
#9 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
|
Re: Windows 7 = death >0
Please upload those last two dumps. Go to C:\Windows\Minidump, zip them up and attach them to your next post.
|
|
|
|
|
11-05-2009, 04:39 PM
|
#11 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
|
Re: Windows 7 = death >0
The only thing that I can see from this is that you have many very outdated drivers...
Code:
91138000 91155000 dump_nvstor32 dump_nvstor32.sys Fri Oct 26 14:50:16 2007 (472236E8) 90932000 90932c80 lmimirr lmimirr.sys Tue Apr 10 18:32:11 2007 (461C106B) 9a574000 9a575cc0 MCSTRM MCSTRM.SYS Tue Dec 16 17:24:32 2003 (3FDF8620) 88c84000 88ca1000 nvstor32 nvstor32.sys Fri Oct 26 14:50:16 2007 (472236E8) 8fd41000 8fd95c80 nvm62x32 nvm62x32.sys Fri Oct 17 17:00:39 2008 (48F8FCF7) 8efe8000 8efeca80 PS2 PS2.sys Mon Dec 12 20:26:59 2005 (439E2363) 88d36000 88d3ede0 PxHelp20 PxHelp20.sys Wed Jun 20 18:26:00 2007 (4679A978) 9117f000 911b7b00 rt73 rt73.sys Tue Aug 02 11:00:35 2005 (42EF8A93) 88ade000 88b19000 vmm vmm.sys Sun Feb 18 03:10:42 2007 (45D80A02) 88ade000 88b19000 vmm vmm.sys Sun Feb 18 03:10:42 2007 (45D80A02) Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Devin\AppData\Local\Temp\Rar$DI00.511\110509-33072-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7100 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0x82e55000 PsLoadedModuleList = 0x82f9d810
Debug session time: Thu Nov 5 00:51:39.426 2009 (GMT-5)
System Uptime: 0 days 6:40:40.439
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
............
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 0, {18, 5, 0, 90108865}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
ERROR: Could Not Find Target OS Version. Please Update GetFunctionForOSVer to include target OS Version
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+eb865 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000018
Arg2: 00000005
Arg3: 00000000
Arg4: 90108865
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
ERROR: Could Not Find Target OS Version. Please Update GetFunctionForOSVer to include target OS Version
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: 82e55000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49d509f6
FAULTING_IP:
nt+3b7bb
82e907bb 833dc48afb8200 cmp dword ptr [nt+0x163ac4 (82fb8ac4)],0
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 82e907bb (nt+0x0003b7bb)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000001
NumberParameters: 0
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x0
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 90108865 to 82e907bb
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
807e2ac4 90108865 badb0d00 00000007 86c95808 nt+0x3b7bb
807e2b78 901031a2 86c95808 864e542c 00000000 nvlddmkm+0xeb865
807e2b90 9009d78a 8639ac98 864e542c 8647b000 nvlddmkm+0xe61a2
807e2ba8 9006d626 00000200 86525784 90028ad5 nvlddmkm+0x8078a
807e2bc8 908370d6 8647b000 00000000 807e2bec nvlddmkm+0x50626
807e2bd8 90847d25 8626ac80 86195920 00000000 dxgkrnl+0x20d6
807e2bec 82e894ec 8626ac80 86195920 8647b000 dxgkrnl+0x12d25
00000000 00000000 00000000 00000000 00000000 nt+0x344ec
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+eb865
90108865 ff5018 call dword ptr [eax+18h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nvlddmkm+eb865
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> r
eax=82f8c17c ebx=807e2b05 ecx=00000014 edx=00000000 esi=807c6120 edi=00000000
eip=82e907bb esp=807e2aac ebp=807e2ac4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
nt+0x3b7bb:
82e907bb 833dc48afb8200 cmp dword ptr [nt+0x163ac4 (82fb8ac4)],0 ds:0023:82fb8ac4=????????
1: kd> lmntsm
start end module name
8fcf6000 8fd22000 1394ohci 1394ohci.sys Tue Apr 21 23:50:20 2009 (49EE93FC)
889b8000 88a00000 ACPI ACPI.sys Tue Apr 21 23:08:37 2009 (49EE8A35)
8effa000 8effb300 AeKbd AeKbd.sys Thu May 14 08:18:46 2009 (4A0C0C26)
8efe6000 8efe7280 AeMouse AeMouse.sys Thu May 14 08:18:48 2009 (4A0C0C28)
88a66000 88ac0000 afd afd.sys Tue Apr 21 23:09:58 2009 (49EE8A86)
90933000 90945000 AgileVpn AgileVpn.sys Tue Apr 21 23:53:30 2009 (49EE94BA)
8efaf000 8efc1000 amdk8 amdk8.sys Tue Apr 21 23:08:27 2009 (49EE8A2B)
88ce8000 88cf1000 amdxata amdxata.sys Tue Mar 10 19:22:16 2009 (49B6F628)
9c1cf000 9c1d8000 asyncmac asyncmac.sys Tue Apr 21 23:53:14 2009 (49EE94AA)
88c58000 88c61000 atapi atapi.sys Tue Apr 21 23:08:39 2009 (49EE8A37)
88c61000 88c84000 ataport ataport.SYS Tue Apr 21 23:08:42 2009 (49EE8A3A)
8ef3f000 8ef8f380 avgldx86 avgldx86.sys Thu Jul 09 20:17:49 2009 (4A5688AD)
8ef39000 8ef3e280 avgmfx86 avgmfx86.sys Wed Jul 01 16:37:21 2009 (4A4BC901)
88d9c000 88db4e00 avgtdix avgtdix.sys Mon Apr 06 09:42:27 2009 (49DA06C3)
891f2000 891f9000 Beep Beep.SYS Tue Apr 21 23:43:27 2009 (49EE925F)
8ef2b000 8ef39000 blbdrive blbdrive.sys Tue Apr 21 23:20:31 2009 (49EE8CFF)
88844000 8884c000 BOOTVID BOOTVID.dll Wed Apr 22 01:01:42 2009 (49EEA4B6)
9a4ac000 9a4c5000 bowser bowser.sys Tue Apr 21 23:11:38 2009 (49EE8AEA)
97990000 979ae000 cdd cdd.dll unavailable (00000000)
891cc000 891eb000 cdrom cdrom.sys Tue Apr 21 23:08:48 2009 (49EE8A40)
8888e000 88939000 CI CI.dll Wed Apr 22 01:08:59 2009 (49EEA66B)
88c33000 88c58000 CLASSPNP CLASSPNP.SYS Tue Apr 21 23:08:43 2009 (49EE8A3B)
8884c000 8888e000 CLFS CLFS.SYS Tue Apr 21 23:08:36 2009 (49EE8A34)
88d3f000 88d9c000 cng cng.sys Tue Apr 21 23:31:04 2009 (49EE8F78)
90925000 90932000 CompositeBus CompositeBus.sys Tue Apr 21 23:43:54 2009 (49EE927A)
91121000 9112e000 crashdmp crashdmp.sys Tue Apr 21 23:44:19 2009 (49EE9293)
8eeaf000 8ef13000 csc csc.sys Tue Apr 21 23:12:21 2009 (49EE8B15)
8ef13000 8ef2b000 dfsc dfsc.sys Tue Apr 21 23:11:34 2009 (49EE8AE6)
8eea3000 8eeaf000 discache discache.sys Tue Apr 21 23:21:34 2009 (49EE8D3E)
89176000 89187000 disk disk.sys Tue Apr 21 23:08:52 2009 (49EE8A44)
91108000 91121000 drmk drmk.sys Wed Apr 22 00:40:17 2009 (49EE9FB1)
9112e000 91138000 dump_diskdump dump_diskdump.sys Tue Apr 21 23:44:19 2009 (49EE9293)
91155000 91166000 dump_dumpfve dump_dumpfve.sys Tue Apr 21 23:10:11 2009 (49EE8A93)
91138000 91155000 dump_nvstor32 dump_nvstor32.sys Fri Oct 26 14:50:16 2007 (472236E8)
911b8000 911c2000 Dxapi Dxapi.sys Tue Apr 21 23:22:56 2009 (49EE8D90)
90835000 908ec000 dxgkrnl dxgkrnl.sys Tue Apr 21 23:23:48 2009 (49EE8DC4)
908ec000 90925000 dxgmms1 dxgmms1.sys Tue Apr 21 23:22:57 2009 (49EE8D91)
88d25000 88d36000 fileinfo fileinfo.sys Tue Apr 21 23:19:22 2009 (49EE8CBA)
88cf1000 88d25000 fltmgr fltmgr.sys Tue Apr 21 23:08:39 2009 (49EE8A37)
88fb6000 88fbf000 Fs_Rec Fs_Rec.sys Tue Apr 21 23:08:38 2009 (49EE8A36)
89144000 89176000 fvevol fvevol.sys Tue Apr 21 23:10:25 2009 (49EE8AA1)
8937a000 893ab000 fwpkclnt fwpkclnt.sys Tue Apr 21 23:09:26 2009 (49EE8A66)
82e1e000 82e55000 hal halmacpi.dll Tue Apr 21 23:08:30 2009 (49EE8A2E)
8fd22000 8fd41000 HDAudBus HDAudBus.sys Tue Apr 21 23:49:20 2009 (49EE93C0)
9a427000 9a4ac000 HTTP HTTP.sys Tue Apr 21 23:10:08 2009 (49EE8A90)
8922d000 89235000 hwpolicy hwpolicy.sys Tue Apr 21 23:08:27 2009 (49EE8A2B)
8efc1000 8efd9000 i8042prt i8042prt.sys Tue Apr 21 23:08:47 2009 (49EE8A3F)
9c188000 9c1ae000 ipnat ipnat.sys Tue Apr 21 23:53:01 2009 (49EE949D)
8ee8c000 8eea3000 ISODrive ISODrive.sys Tue Feb 10 04:22:07 2009 (4991473F)
8efed000 8effa000 kbdclass kbdclass.sys Tue Apr 21 23:08:39 2009 (49EE8A37)
80ba9000 80bb1000 kdcom kdcom.dll Wed Apr 22 01:07:23 2009 (49EEA60B)
8faa5000 8fad9000 ks ks.sys Tue Apr 21 23:43:43 2009 (49EE926F)
88f95000 88fa8000 ksecdd ksecdd.sys Tue Apr 21 23:09:16 2009 (49EE8A5C)
8910f000 89134000 ksecpkg ksecpkg.sys Tue Apr 21 23:32:15 2009 (49EE8FBF)
90e1a000 90e2a000 lltdio lltdio.sys Tue Apr 21 23:51:49 2009 (49EE9455)
90932000 90932c80 lmimirr lmimirr.sys Tue Apr 10 18:32:11 2007 (461C106B)
9a56a000 9a574000 LMIRfsDriver LMIRfsDriver.sys Mon Jul 14 12:26:22 2008 (487B7E2E)
911cd000 911e8000 luafv luafv.sys Tue Apr 21 23:13:02 2009 (49EE8B3E)
9a574000 9a575cc0 MCSTRM MCSTRM.SYS Tue Dec 16 17:24:32 2003 (3FDF8620)
88828000 88833000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Apr 21 23:10:35 2009 (49EE8AAB)
8fce9000 8fcf6000 modem modem.sys Tue Apr 21 23:53:57 2009 (49EE94D5)
911c2000 911cd000 monitor monitor.sys Tue Apr 21 23:23:20 2009 (49EE8DA8)
8efd9000 8efe6000 mouclass mouclass.sys Tue Apr 21 23:08:39 2009 (49EE8A37)
88a00000 88a16000 mountmgr mountmgr.sys Tue Apr 21 23:08:51 2009 (49EE8A43)
9a4c5000 9a4d7000 mpsdrv mpsdrv.sys Tue Apr 21 23:51:21 2009 (49EE9439)
9a4d7000 9a4fa000 mrxsmb mrxsmb.sys Tue Apr 21 23:11:40 2009 (49EE8AEC)
9a4fa000 9a535000 mrxsmb10 mrxsmb10.sys Tue Apr 21 23:11:55 2009 (49EE8AFB)
9a535000 9a550000 mrxsmb20 mrxsmb20.sys Tue Apr 21 23:11:48 2009 (49EE8AF4)
88e00000 88e0b000 Msfs Msfs.SYS Tue Apr 21 23:08:46 2009 (49EE8A3E)
88809000 88811000 msisadrv msisadrv.sys Tue Apr 21 23:08:33 2009 (49EE8A31)
88f6a000 88f95000 msrpc msrpc.sys Tue Apr 21 23:09:19 2009 (49EE8A5F)
8ee82000 8ee8c000 mssmbios mssmbios.sys Tue Apr 21 23:16:49 2009 (49EE8C21)
89134000 89144000 mup mup.sys Tue Apr 21 23:11:32 2009 (49EE8AE4)
8901a000 890d1000 ndis ndis.sys Tue Apr 21 23:09:42 2009 (49EE8A76)
9095d000 90968000 ndistapi ndistapi.sys Tue Apr 21 23:52:58 2009 (49EE949A)
90e2a000 90e3a000 ndisuio ndisuio.sys Tue Apr 21 23:52:24 2009 (49EE9478)
90968000 9098b000 ndiswan ndiswan.sys Tue Apr 21 23:53:08 2009 (49EE94A4)
909eb000 909fc000 NDProxy NDProxy.SYS Tue Apr 21 23:53:01 2009 (49EE949D)
88de7000 88df5000 netbios netbios.sys Tue Apr 21 23:52:28 2009 (49EE947C)
88db5000 88de7000 netbt netbt.sys Tue Apr 21 23:09:39 2009 (49EE8A73)
890d1000 8910f000 NETIO NETIO.SYS Tue Apr 21 23:10:05 2009 (49EE8A8D)
88e0b000 88e19000 Npfs Npfs.SYS Tue Apr 21 23:08:49 2009 (49EE8A41)
8ee78000 8ee82000 nsiproxy nsiproxy.sys Tue Apr 21 23:09:25 2009 (49EE8A65)
82e55000 83264000 nt ntkrnlpa.exe Tue Apr 21 23:13:18 2009 (49EE8B4E)
88e3b000 88f6a000 Ntfs Ntfs.sys Tue Apr 21 23:09:31 2009 (49EE8A6B)
891eb000 891f2000 Null Null.SYS Tue Apr 21 23:08:37 2009 (49EE8A35)
9001d000 9076f9c0 nvlddmkm nvlddmkm.sys Thu Apr 02 14:54:46 2009 (49D509F6)
8fd41000 8fd95c80 nvm62x32 nvm62x32.sys Fri Oct 17 17:00:39 2008 (48F8FCF7)
88c14000 88c33000 nvraid nvraid.sys Tue Apr 14 20:25:36 2009 (49E52980)
88c84000 88ca1000 nvstor32 nvstor32.sys Fri Oct 26 14:50:16 2007 (472236E8)
907b4000 907fa000 nwifi nwifi.sys Tue Apr 21 23:50:26 2009 (49EE9402)
88ac0000 88ade000 pacer pacer.sys Tue Apr 21 23:52:32 2009 (49EE9480)
88a55000 88a66000 partmgr partmgr.sys Tue Apr 21 23:08:57 2009 (49EE8A49)
88a2b000 88a55000 pci pci.sys Tue Apr 21 23:08:40 2009 (49EE8A38)
88be8000 88bef000 pciide pciide.sys Tue Apr 21 23:08:44 2009 (49EE8A3C)
88bef000 88bfd000 PCIIDEX PCIIDEX.SYS Tue Apr 21 23:08:40 2009 (49EE8A38)
88fa8000 88fb6000 pcw pcw.sys Tue Apr 21 23:08:34 2009 (49EE8A32)
9c019000 9c0b0000 peauth peauth.sys Wed Apr 22 00:40:09 2009 (49EE9FA9)
910d9000 91108000 portcls portcls.sys Tue Apr 21 23:49:26 2009 (49EE93C6)
8efe8000 8efeca80 PS2 PS2.sys Mon Dec 12 20:26:59 2005 (439E2363)
88833000 88844000 PSHED PSHED.dll Wed Apr 22 01:09:07 2009 (49EEA673)
88d36000 88d3ede0 PxHelp20 PxHelp20.sys Wed Jun 20 18:26:00 2007 (4679A978)
9a568000 9a569800 RaInfo RaInfo.sys Fri Jan 04 13:57:12 2008 (477E8188)
90945000 9095d000 rasl2tp rasl2tp.sys Tue Apr 21 23:53:07 2009 (49EE94A3)
9098b000 909a3000 raspppoe raspppoe.sys Tue Apr 21 23:53:24 2009 (49EE94B4)
909a3000 909ba000 raspptp raspptp.sys Tue Apr 21 23:53:17 2009 (49EE94AD)
909ba000 909d1000 rassstp rassstp.sys Tue Apr 21 23:53:30 2009 (49EE94BA)
8ee37000 8ee78000 rdbss rdbss.sys Tue Apr 21 23:11:43 2009 (49EE8AEF)
909d1000 909db000 rdpbus rdpbus.sys Wed Apr 22 00:01:12 2009 (49EE9688)
88fe0000 88fe8000 RDPCDD RDPCDD.sys Wed Apr 22 00:00:11 2009 (49EE964B)
88fe8000 88ff0000 rdpencdd rdpencdd.sys Wed Apr 22 00:00:11 2009 (49EE964B)
88ff0000 88ff8000 rdprefmp rdprefmp.sys Wed Apr 22 00:00:11 2009 (49EE964B)
89200000 8922d000 rdyboost rdyboost.sys Tue Apr 21 23:19:32 2009 (49EE8CC4)
911e8000 911fb000 rspndr rspndr.sys Tue Apr 21 23:51:50 2009 (49EE9456)
9117f000 911b7b00 rt73 rt73.sys Tue Aug 02 11:00:35 2005 (42EF8A93)
90e3a000 910d8540 RTKVHDA RTKVHDA.sys Tue Aug 18 05:30:35 2009 (4A8A74BB)
88b67000 88b8d000 SCSIPORT SCSIPORT.SYS Tue Apr 21 23:44:24 2009 (49EE9298)
9c0b0000 9c0ba000 secdrv secdrv.SYS Wed Sep 13 09:18:32 2006 (45080528)
893f2000 893fa000 spldr spldr.sys Wed Mar 25 15:16:08 2009 (49CA82F8)
9c137000 9c188000 srv srv.sys Tue Apr 21 23:12:29 2009 (49EE8B1D)
9c0e8000 9c137000 srv2 srv2.sys Wed Sep 09 23:10:12 2009 (4AA86E14)
9c0ba000 9c0db000 srvnet srvnet.sys Tue Apr 21 23:12:06 2009 (49EE8B06)
88ca1000 88ce8000 storport storport.sys Tue Apr 21 23:44:26 2009 (49EE929A)
909db000 909dc380 swenum swenum.sys Tue Apr 21 23:43:34 2009 (49EE9266)
89235000 8937a000 tcpip tcpip.sys Tue Apr 21 23:10:47 2009 (49EE8AB7)
9c0db000 9c0e8000 tcpipreg tcpipreg.sys Tue Apr 21 23:52:46 2009 (49EE948E)
88e30000 88e3b000 TDI TDI.SYS Tue Apr 21 23:09:31 2009 (49EE8A6B)
88e19000 88e30000 tdx tdx.sys Tue Apr 21 23:09:29 2009 (49EE8A69)
88b19000 88b29000 termdd termdd.sys Wed Apr 22 00:00:07 2009 (49EE9647)
97960000 97969000 TSDDD TSDDD.dll unavailable (00000000)
8ef90000 8efaf000 tunnel tunnel.sys Tue Apr 21 23:52:38 2009 (49EE9486)
909dd000 909eb000 umbus umbus.sys Tue Apr 21 23:50:03 2009 (49EE93EB)
9117d000 9117e700 USBD USBD.SYS Tue Apr 21 23:49:30 2009 (49EE93CA)
8fa4a000 8fa59000 usbehci usbehci.sys Tue Apr 21 23:49:40 2009 (49EE93D4)
90770000 907b4000 usbhub usbhub.sys Tue Apr 21 23:50:25 2009 (49EE9401)
8ee00000 8ee0a000 usbohci usbohci.sys Tue Apr 21 23:49:39 2009 (49EE93D3)
8fa00000 8fa4a000 USBPORT USBPORT.SYS Tue Apr 21 23:49:38 2009 (49EE93D2)
91166000 9117d000 USBSTOR USBSTOR.SYS Tue Apr 21 23:49:42 2009 (49EE93D6)
88811000 8881c000 vdrvroot vdrvroot.sys Tue Apr 21 23:44:49 2009 (49EE92B1)
89000000 8900c000 vga vga.sys Tue Apr 21 23:23:17 2009 (49EE8DA5)
88fbf000 88fe0000 VIDEOPRT VIDEOPRT.SYS Tue Apr 21 23:23:20 2009 (49EE8DA8)
88ade000 88b19000 vmm vmm.sys Sun Feb 18 03:10:42 2007 (45D80A02)
893ab000 893b3380 vmstorfl vmstorfl.sys Tue Apr 21 23:26:29 2009 (49EE8E65)
88b8d000 88b9d000 volmgr volmgr.sys Tue Apr 21 23:08:47 2009 (49EE8A3F)
88b9d000 88be8000 volmgrx volmgrx.sys Tue Apr 21 23:09:06 2009 (49EE8A52)
893b4000 893f2000 volsnap volsnap.sys Tue Apr 21 23:08:58 2009 (49EE8A4A)
8fa59000 8faa5000 VSTBS23 VSTBS23.SYS Wed Oct 15 20:30:15 2008 (48F68B17)
8fc34000 8fce9000 VSTCNXT3 VSTCNXT3.SYS Wed Oct 15 20:29:13 2008 (48F68AD9)
8fad9000 8fbdb000 VSTDPV3 VSTDPV3.SYS Wed Oct 15 20:32:04 2008 (48F68B84)
88c00000 88c13000 wanarp wanarp.sys Tue Apr 21 23:53:29 2009 (49EE94B9)
8900c000 89019000 watchdog watchdog.sys Tue Apr 21 23:21:46 2009 (49EE8D4A)
88939000 889aa000 Wdf01000 Wdf01000.sys Tue Apr 21 23:09:01 2009 (49EE8A4D)
889aa000 889b8000 WDFLDR WDFLDR.SYS Tue Apr 21 23:08:47 2009 (49EE8A3F)
891f9000 89200000 wfplwf wfplwf.sys Tue Apr 21 23:52:24 2009 (49EE9478)
97700000 9794a000 win32k win32k.sys unavailable (00000000)
88800000 88809000 WMILIB WMILIB.SYS Tue Apr 21 23:08:46 2009 (49EE8A3E)
90e00000 90e1a000 WudfPf WudfPf.sys Tue Apr 21 23:48:41 2009 (49EE9399)
9c1ae000 9c1ce480 WUDFRd WUDFRd.sys Tue Apr 21 23:49:10 2009 (49EE93B6)
Unloaded modules:
9c1dd000 9c1e7000 hiber_storpo
Timestamp: unavailable (00000000)
Checksum: 00000000
9a5e0000 9a5fd000 hiber_nvstor
Timestamp: unavailable (00000000)
Checksum: 00000000
9c1e7000 9c1f8000 hiber_dumpfv
Timestamp: unavailable (00000000)
Checksum: 00000000
9c1d8000 9c1da000 MSTEE.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
9c1da000 9c1dd000 MSKSSRV.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
9a576000 9a5e0000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
9a550000 9a568000 parport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
89187000 89194000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
89194000 8919e000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
8919e000 891bb000 dump_nvstor3
Timestamp: unavailable (00000000)
Checksum: 00000000
891bb000 891cc000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
88a66000 88b67000 sptd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
|
|
|
|
|
11-05-2009, 04:57 PM
|
#12 (permalink) |
|
Registered User
Join Date: Nov 2009
Posts: 10
OS: windows 7 RTM 1
|
Re: Windows 7 = death >0
yes.
i did not have windows vista servise pack 2 or 3 installed before i upgraded to windows 7 due to errors. any ways my realtek sound drivers would not update in windows update. same is with Belkin 3g wireless adapter. i do not, however have windows update to set for automatic updates. i like to see what is being installed. anways i think i figured out the 0x00000000 in system properties i found this I/O Port 0x00000000-0x000003AF PCI bus I/O Port 0x00000000-0x000003AF Direct memory access controller I also noticed that i have some shared IRQ's and memory allocations(at least i think their shared) IRQ 20 NVIDIA GeForce 6150SE nForce 430 (Prerelease - WDDM 1.0) IRQ 20 Standard Enhanced PCI to USB Host Controller IRQ 22 High Definition Audio Controller IRQ 22 Standard OpenHCD USB Host Controller IRQ 23 NVIDIA nForce Serial ATA Controller IRQ 23 NVIDIA nForce Serial ATA Controller Memory Address 0xFEFF0000-0xFEFF00FF System board Memory Address 0xFEFF0000-0xFEFF00FF High precision event timer I/O Port 0x00001C00-0x00001C80 PCI bus I/O Port 0x00001C00-0x00001C80 NVIDIA nForce PCI System Management Memory Address 0xA0000-0xBFFFF PCI bus Memory Address 0xA0000-0xBFFFF NVIDIA GeForce 6150SE nForce 430 (Prerelease - WDDM 1.0) I/O Port 0x000003B0-0x000003DF PCI bus I/O Port 0x000003B0-0x000003DF NVIDIA GeForce 6150SE nForce 430 (Prerelease - WDDM 1.0) I/O Port 0x00008000-0x0000FFFF PCI bus I/O Port 0x00008000-0x0000FFFF PCI standard PCI-to-PCI bridge |
|
|
|
|
11-05-2009, 05:20 PM
|
#13 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
|
Re: Windows 7 = death >0
If the wireless USB adapter wouldn't update, you should definitely either look on the manufacturer's website or uninstall the driver and invest in a new one. 2003 is WAY too old for Windows 7.
|
|
|
|
|
11-05-2009, 06:03 PM
|
#15 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
|
Re: Windows 7 = death >0
I don't even know what you're talking about, to be completely honest. What do you mean, your SPTD?
EDIT: I was mistaken. Your USB wireless device is from 2005 (still very old), it is your RealNetworks software that's from 2003. I recommend that you uninstall it until we figure this out. Last edited by DT Roberts; 11-05-2009 at 06:05 PM. |
|
|
|
|
11-05-2009, 06:14 PM
|
#16 (permalink) |
|
Windows Tech Team
Join Date: Jun 2009
Location: Massachusetts
Posts: 1,194
OS: Windows 7 RTM (x64), Vista SP2, XP Pro, Windows 7, Ubuntu 9.04
|
Re: Windows 7 = death >0
Note to self: always look at the unloaded modules.
sptd.sys is the cause of much grief in Windows Vista/7. Uninstall Daemon Tools and see if the problem persists. |
|
|
|
|
| Thread Tools | |
|
|
Re: Windows 7 = death >0
