Windows 7 Notepad desktop.ini problem on reboot

[bweier]

Hello Everyone and thanks in advance for your help!

Blue screen when automatic updates installed last night. Now on reboot I get the following Notepad popping up (below). I also copied the blue screen crash info. Any input would be much appreciated.

1. The desktop.ini file does exist as written (below)
2. All updates are in place (Windows
3. Toshiba bios 1.70 (Insyde)
4. Windows 7 64 Bit
5. Malwarebytes and Microsoft Security Essentials protected

Thanks!11




From Desktop - Notepad

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787


Windows has recovered from an unexpected shutdown


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: 0000000000000000
BCP3: FFFFF880037AF798
BCP4: FFFFF880037AEFF0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022813-24554-01.dmp
C:\Users\Bill\AppData\Local\Temp\WER-58469-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt


This issue happens after automatic updates overnight while computer is in "sleep" mode


Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.145.727.0)
Platform Update for Windows 7 x64-Edition (KB2670838)

 

[kaos]

please upload ure minidump file

 

[bweier]

Where can I find this? I am assuming this isn't what my Yorkie leaves on the carpet...

Never mind, I just saw the C:\Windows\Minidump\022813-24554-01.dmp from above

I will upload it later tonight in a few hours when I get off work.

Thank you!

 

[bweier]

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




Loading Dump File [C:\Windows\Minidump\022813-24554-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0320e000 PsLoadedModuleList = 0xfffff800`03452670
Debug session time: Thu Feb 28 07:56:40.656 2013 (UTC - 5:00)
System Uptime: 10 days 22:22:47.070
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image \SystemRoot\system32\DRIVERS\Thpevm.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Thpevm.SYS
*** ERROR: Module load completed but symbols could not be loaded for Thpevm.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 1000007E, {ffffffffc0000005, 0, fffff880037af798, fffff880037aeff0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : Thpevm.SYS ( Thpevm+9aa )


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





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




Loading Dump File [C:\Windows\Minidump\021713-24320-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03260000 PsLoadedModuleList = 0xfffff800`034a4670
Debug session time: Sun Feb 17 09:32:56.640 2013 (UTC - 5:00)
System Uptime: 0 days 21:21:58.577
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.................
Unable to load image \SystemRoot\system32\DRIVERS\Thpevm.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Thpevm.SYS
*** ERROR: Module load completed but symbols could not be loaded for Thpevm.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 1000007E, {ffffffffc0000005, 0, fffff880037af798, fffff880037aeff0}


***** Kernel symbols are WRONG. Please fix symbols to do analysis.


*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : Thpevm.SYS ( Thpevm+9aa )


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

 

[kaos]

dont copy and paste from Windows DBG, we need the file lol, we will do our own analysis of it , and build a plan from the file.

the file is located c:/windows/minidump

we wil tell you drivers what are out of date etc

if its the Thpevm.SYS, its ure harddrive protetion software (toshiba, try, disabling this and see if it works, OR update the software

 

[bweier]

dont copy and paste from Windows DBG, we need the file lol, we will do our own analysis of it , and build a plan from the file.

the file is located c:/windows/minidump

we wil tell you drivers what are out of date etc

if its the Thpevm.SYS, its ure harddrive protetion software (toshiba, try, disabling this and see if it works, OR update the software

OK. I can see both minidump files in the location you stated, but what program do I use to open them? Notepad, Word, etc. all open gibberish so that is why I installed the Windows SDK utility last night in an effort to get something legible.

So "open with" which program? Then I will cut and paste it for you.

Thanks!!

 

[bweier]

I just downloaded BlueScreenView and maybe this is what you are looking for. ACPI.sys and Thpevm.SYS were both in pink at the top of the cut and pasted list below in both minidump files. Let me know how I can clean this up for you or if you need something else.

[h=3]Crash List[/h]
[h=4]Created by using BlueScreenView[/h]

Dump File	Crash Time	Bug Check String	Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Caused By Driver	Caused By Address	File Description	Product Name	Company	File Version	Processor	Crash Address	Stack Address 1	Stack Address 2	Stack Address 3	Computer Name	Full Path	Processors Count	Major Version	Minor Version	Dump File Size

[TD="bgcolor: #FFFFFF"]022813-24554-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]2/28/2013 7:58:15 AM[/TD]
[TD="bgcolor: #FFFFFF"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/TD]
[TD="bgcolor: #FFFFFF"]0x1000007e[/TD]
[TD="bgcolor: #FFFFFF"]ffffffff`c0000005[/TD]
[TD="bgcolor: #FFFFFF"]00000000`00000000[/TD]
[TD="bgcolor: #FFFFFF"]fffff880`037af798[/TD]
[TD="bgcolor: #FFFFFF"]fffff880`037aeff0[/TD]
[TD="bgcolor: #FFFFFF"]Thpevm.SYS[/TD]
[TD="bgcolor: #FFFFFF"]Thpevm.SYS+9aa[/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"]x64[/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"]C:\windows\Minidump\022813-24554-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]8[/TD]
[TD="bgcolor: #FFFFFF"]15[/TD]
[TD="bgcolor: #FFFFFF"]7601[/TD]
[TD="bgcolor: #FFFFFF"]292,360[/TD]

[TD="bgcolor: #FFFFFF"]021713-24320-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]2/17/2013 9:34:41 AM[/TD]
[TD="bgcolor: #FFFFFF"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/TD]
[TD="bgcolor: #FFFFFF"]0x1000007e[/TD]
[TD="bgcolor: #FFFFFF"]ffffffff`c0000005[/TD]
[TD="bgcolor: #FFFFFF"]00000000`00000000[/TD]
[TD="bgcolor: #FFFFFF"]fffff880`037af798[/TD]
[TD="bgcolor: #FFFFFF"]fffff880`037aeff0[/TD]
[TD="bgcolor: #FFFFFF"]Thpevm.SYS[/TD]
[TD="bgcolor: #FFFFFF"]Thpevm.SYS+9aa[/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"]x64[/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"] [/TD]
[TD="bgcolor: #FFFFFF"]C:\windows\Minidump\021713-24320-01.dmp[/TD]
[TD="bgcolor: #FFFFFF"]8[/TD]
[TD="bgcolor: #FFFFFF"]15[/TD]
[TD="bgcolor: #FFFFFF"]7601[/TD]
[TD="bgcolor: #FFFFFF"]291,776[/TD]

022813-24554-01.dmp 2/28/2013 7:58:15 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 00000000`00000000 fffff880`037af798 fffff880`037aeff0 Thpevm.SYS Thpevm.SYS+9aa x64 C:\windows\Minidump\022813-24554-01.dmp 8 15 7601 292,360
021713-24320-01.dmp 2/17/2013 9:34:41 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 00000000`00000000 fffff880`037af798 fffff880`037aeff0 Thpevm.SYS Thpevm.SYS+9aa x64 C:\windows\Minidump\021713-24320-01.dmp 8 15 7601 291,776




ACPI.sys ACPI.sys+16c0e fffff880`0119c000 fffff880`011f3000 0x00057000 0x4ce79294 11/20/2010 4:19:16 AM
Thpevm.SYS Thpevm.SYS+9aa fffff880`01a9c000 fffff880`01a9df80 0x00001f80 0x4a487829 6/29/2009 3:15:37 AM
ntoskrnl.exe fffff800`0320e000 fffff800`037f5000 0x005e7000 0x50e79935 1/4/2013 10:08:37 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18044 (win7sp1_gdr.130104-1431) Microsoft Corporation C:\windows\system32\ntoskrnl.exe
hal.dll fffff800`037f5000 fffff800`0383e000 0x00049000 0x4ce7c669 11/20/2010 8:00:25 AM
kdcom.dll fffff800`00b9d000 fffff800`00ba7000 0x0000a000 0x4d4d8061 2/5/2011 11:52:49 AM
mcupdate_GenuineIntel.dll fffff880`00ca0000 fffff880`00cef000 0x0004f000 0x4ce7c737 11/20/2010 8:03:51 AM
PSHED.dll fffff880`00cef000 fffff880`00d03000 0x00014000 0x4a5be027 7/13/2009 8:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\windows\system32\PSHED.dll
CLFS.SYS fffff880`00d03000 fffff880`00d61000 0x0005e000 0x4a5bc11d 7/13/2009 6:19:57 PM
CI.dll fffff880`00ebd000 fffff880`00f7d000 0x000c0000 0x4ce7c944 11/20/2010 8:12:36 AM
Wdf01000.sys fffff880`010ca000 fffff880`0118c000 0x000c2000 0x5010aa89 7/25/2012 9:25:13 PM
WDFLDR.SYS fffff880`0118c000 fffff880`0119c000 0x00010000 0x5010ab70 7/25/2012 9:29:04 PM
WMILIB.SYS fffff880`011f3000 fffff880`011fc000 0x00009000 0x4a5bc117 7/13/2009 6:19:51 PM
msisadrv.sys fffff880`01000000 fffff880`0100a000 0x0000a000 0x4a5bc0fe 7/13/2009 6:19:26 PM
pci.sys fffff880`0100a000 fffff880`0103d000 0x00033000 0x4ce7928f 11/20/2010 4:19:11 AM
vdrvroot.sys fffff880`0103d000 fffff880`0104a000 0x0000d000 0x4a5bcadb 7/13/2009 7:01:31 PM
partmgr.sys fffff880`0104a000 fffff880`0105f000 0x00015000 0x4f641bc1 3/17/2012 12:06:09 AM
compbatt.sys fffff880`0105f000 fffff880`01068000 0x00009000 0x4a5bc3b6 7/13/2009 6:31:02 PM
BATTC.SYS fffff880`01068000 fffff880`01074000 0x0000c000 0x4a5bc3b5 7/13/2009 6:31:01 PM
volmgr.sys fffff880`01074000 fffff880`01089000 0x00015000 0x4ce792a0 11/20/2010 4:19:28 AM
volmgrx.sys fffff880`00f7d000 fffff880`00fd9000 0x0005c000 0x00000000
mountmgr.sys fffff880`01089000 fffff880`010a3000 0x0001a000 0x4ce79299 11/20/2010 4:19:21 AM
pciide.sys fffff880`010a3000 fffff880`010aa000 0x00007000 0x4a5bc115 7/13/2009 6:19:49 PM
PCIIDEX.SYS fffff880`010aa000 fffff880`010ba000 0x00010000 0x4a5bc114 7/13/2009 6:19:48 PM
iaStor.sys fffff880`01241000 fffff880`01395000 0x00154000 0x4c8ece94 9/13/2010 8:23:32 PM
atapi.sys fffff880`01395000 fffff880`0139e000 0x00009000 0x4a5bc113 7/13/2009 6:19:47 PM
ataport.SYS fffff880`0139e000 fffff880`013c8000 0x0002a000 0x4ce79293 11/20/2010 4:19:15 AM
msahci.sys fffff880`013c8000 fffff880`013d3000 0x0000b000 0x4ce7a416 11/20/2010 5:33:58 AM
amdxata.sys fffff880`013d3000 fffff880`013de000 0x0000b000 0x4ba3a3ca 3/19/2010 11:18:18 AM
fltmgr.sys fffff880`00e00000 fffff880`00e4c000 0x0004c000 0x4ce7929c 11/20/2010 4:19:24 AM
fileinfo.sys fffff880`013de000 fffff880`013f2000 0x00014000 0x4a5bc481 7/13/2009 6:34:25 PM
PxHlpa64.sys fffff880`013f2000 fffff880`013fde00 0x0000be00 0x4a416253 6/23/2009 6:16:35 PM
Ntfs.sys fffff880`01449000 fffff880`015ec000 0x001a3000 0x5040d4c6 8/31/2012 10:14:14 AM
msrpc.sys fffff880`00e4c000 fffff880`00eaa000 0x0005e000 0x00000000
ksecdd.sys fffff880`01400000 fffff880`0141b000 0x0001b000 0x4fc97f6f 6/1/2012 9:50:23 PM
cng.sys fffff880`00d61000 fffff880`00dd3000 0x00072000 0x5037a204 8/24/2012 10:47:16 AM
pcw.sys fffff880`0141b000 fffff880`0142c000 0x00011000 0x4a5bc0ff 7/13/2009 6:19:27 PM
Fs_Rec.sys fffff880`0142c000 fffff880`01436000 0x0000a000 0x00000000
ndis.sys fffff880`016d1000 fffff880`017c3000 0x000f2000 0x5034f6b2 8/22/2012 10:11:46 AM
NETIO.SYS fffff880`01600000 fffff880`01660000 0x00060000 0x5034f6a0 8/22/2012 10:11:28 AM
ksecpkg.sys fffff880`01660000 fffff880`0168b000 0x0002b000 0x5037a24d 8/24/2012 10:48:29 AM
tcpip.sys fffff880`01800000 fffff880`01a00000 0x00200000 0x50e4f6f4 1/2/2013 10:11:48 PM
fwpkclnt.sys fffff880`00c00000 fffff880`00c49000 0x00049000 0x50e4f5c8 1/2/2013 10:06:48 PM
wd.sys fffff880`0168b000 fffff880`01693000 0x00008000 0x4a5bc11b 7/13/2009 6:19:55 PM
volsnap.sys fffff880`00c49000 fffff880`00c95000 0x0004c000 0x4ce792c8 11/20/2010 4:20:08 AM
TVALZ_O.SYS fffff880`01693000 fffff880`01697e00 0x00004e00 0x4a5beb2e 7/13/2009 9:19:26 PM
tos_sps64.sys fffff880`01a22000 fffff880`01a9c000 0x0007a000 0x4a41ba1d 6/24/2009 12:31:09 AM
spldr.sys fffff880`01a9e000 fffff880`01aa6000 0x00008000 0x4a0858bb 5/11/2009 11:56:27 AM
rdyboost.sys fffff880`01aa6000 fffff880`01ae0000 0x0003a000 0x4ce7982e 11/20/2010 4:43:10 AM
mup.sys fffff880`01ae0000 fffff880`01af2000 0x00012000 0x4a5bc201 7/13/2009 6:23:45 PM
hwpolicy.sys fffff880`01af2000 fffff880`01afb000 0x00009000 0x4ce7927e 11/20/2010 4:18:54 AM
fvevol.sys fffff880`01afb000 fffff880`01b35000 0x0003a000 0x4ce793b6 11/20/2010 4:24:06 AM
disk.sys fffff880`01b35000 fffff880`01b4b000 0x00016000 0x4a5bc11d 7/13/2009 6:19:57 PM
CLASSPNP.SYS fffff880`01b4b000 fffff880`01b7b000 0x00030000 0x4ce7929b 11/20/2010 4:19:23 AM
cdrom.sys fffff880`0439a000 fffff880`043c4000 0x0002a000 0x4ce79298 11/20/2010 4:19:20 AM
Null.SYS fffff880`043c4000 fffff880`043cd000 0x00009000 0x00000000
Beep.SYS fffff880`043cd000 fffff880`043d4000 0x00007000 0x4a5bca8d 7/13/2009 7:00:13 PM
vga.sys fffff880`043d4000 fffff880`043e2000 0x0000e000 0x4a5bc587 7/13/2009 6:38:47 PM
VIDEOPRT.SYS fffff880`04200000 fffff880`04225000 0x00025000 0x4a5bc58b 7/13/2009 6:38:51 PM
watchdog.sys fffff880`043e2000 fffff880`043f2000 0x00010000 0x4a5bc53f 7/13/2009 6:37:35 PM
RDPCDD.sys fffff880`043f2000 fffff880`043fb000 0x00009000 0x4a5bce62 7/13/2009 7:16:34 PM
rdpencdd.sys fffff880`04225000 fffff880`0422e000 0x00009000 0x4a5bce62 7/13/2009 7:16:34 PM
rdprefmp.sys fffff880`01b89000 fffff880`01b92000 0x00009000 0x4a5bce63 7/13/2009 7:16:35 PM
Msfs.SYS fffff880`01b92000 fffff880`01b9d000 0x0000b000 0x00000000
Npfs.SYS fffff880`01b9d000 fffff880`01bae000 0x00011000 0x4a5bc114 7/13/2009 6:19:48 PM
tdx.sys fffff880`01bae000 fffff880`01bd0000 0x00022000 0x4ce79332 11/20/2010 4:21:54 AM
TDI.SYS fffff880`01bd0000 fffff880`01bdd000 0x0000d000 0x4ce7933e 11/20/2010 4:22:06 AM
afd.sys fffff880`02eb0000 fffff880`02f39000 0x00089000 0x4efa9418 12/27/2011 10:59:20 PM
netbt.sys fffff880`02f39000 fffff880`02f7e000 0x00045000 0x4ce79386 11/20/2010 4:23:18 AM
wfplwf.sys fffff880`02f7e000 fffff880`02f87000 0x00009000 0x4a5bccb6 7/13/2009 7:09:26 PM
pacer.sys fffff880`02f87000 fffff880`02fad000 0x00026000 0x4ce7a862 11/20/2010 5:52:18 AM
vwififlt.sys fffff880`02fad000 fffff880`02fc3000 0x00016000 0x4a5bcc3a 7/13/2009 7:07:22 PM
netbios.sys fffff880`02fc3000 fffff880`02fd2000 0x0000f000 0x4a5bccb6 7/13/2009 7:09:26 PM
tosrfcom.sys fffff880`02fd2000 fffff880`02fe4b80 0x00012b80 0x4cd91f19 11/9/2010 5:14:49 AM
wanarp.sys fffff880`02fe5000 fffff880`03000000 0x0001b000 0x4ce7a874 11/20/2010 5:52:36 AM
termdd.sys fffff880`02e00000 fffff880`02e14000 0x00014000 0x4ce7ab0c 11/20/2010 6:03:40 AM
rdbss.sys fffff880`02e14000 fffff880`02e65000 0x00051000 0x4ce79497 11/20/2010 4:27:51 AM
nsiproxy.sys fffff880`02e65000 fffff880`02e71000 0x0000c000 0x4a5bc15e 7/13/2009 6:21:02 PM
mssmbios.sys fffff880`02e71000 fffff880`02e7c000 0x0000b000 0x4a5bc3be 7/13/2009 6:31:10 PM
discache.sys fffff880`02e7c000 fffff880`02e8b000 0x0000f000 0x4a5bc52e 7/13/2009 6:37:18 PM
dfsc.sys fffff880`02e8b000 fffff880`02ea9000 0x0001e000 0x4ce79447 11/20/2010 4:26:31 AM
blbdrive.sys fffff880`01bdd000 fffff880`01bee000 0x00011000 0x4a5bc4df 7/13/2009 6:35:59 PM
tunnel.sys fffff880`01698000 fffff880`016be000 0x00026000 0x4ce7a846 11/20/2010 5:51:50 AM
nvlddmkm.sys fffff880`0f23d000 fffff880`0ffff000 0x00dc2000 0x4fb20748 5/15/2012 2:35:36 AM
nvBridge.kmd fffff880`0f200000 fffff880`0f205000 0x00005000 0x4dd7385f 5/20/2011 10:58:23 PM
dxgkrnl.sys fffff880`04405000 fffff880`044f9000 0x000f4000 0x4ce799fa 11/20/2010 4:50:50 AM
dxgmms1.sys fffff880`044f9000 fffff880`0453f000 0x00046000 0x4ce799c1 11/20/2010 4:49:53 AM
HDAudBus.sys fffff880`0453f000 fffff880`04563000 0x00024000 0x4ce7a65e 11/20/2010 5:43:42 AM
HECIx64.sys fffff880`04563000 fffff880`04574000 0x00011000 0x4cbe2ad7 10/19/2010 6:33:43 PM
usbehci.sys fffff880`04574000 fffff880`04585000 0x00011000 0x4d8c0c00 3/24/2011 10:29:04 PM
USBPORT.SYS fffff880`04585000 fffff880`045db000 0x00056000 0x4d8c0c08 3/24/2011 10:29:12 PM
1394ohci.sys fffff880`04ae2000 fffff880`04b20000 0x0003e000 0x4ce7a6a8 11/20/2010 5:44:56 AM
o2sdgx64.sys fffff880`04b20000 fffff880`04b2a780 0x0000a780 0x4a8a6db4 8/18/2009 4:00:36 AM
SCSIPORT.SYS fffff880`04b2b000 fffff880`04b5a000 0x0002f000 0x4ce7a419 11/20/2010 5:34:01 AM
o2mdgx64.sys fffff880`04b5a000 fffff880`04b6b880 0x00011880 0x4ce4ea2e 11/18/2010 3:56:14 AM
athrx.sys fffff880`052f6000 fffff880`0559c000 0x002a6000 0x4ddb5d23 5/24/2011 2:24:19 AM
vwifibus.sys fffff880`0559c000 fffff880`055a9000 0x0000d000 0x4a5bcc39 7/13/2009 7:07:21 PM
L1C62x64.sys fffff880`055a9000 fffff880`055be000 0x00015000 0x4ca03b67 9/27/2010 1:36:23 AM
i8042prt.sys fffff880`055be000 fffff880`055dc000 0x0001e000 0x4a5bc11d 7/13/2009 6:19:57 PM
kbdclass.sys fffff880`055dc000 fffff880`055eb000 0x0000f000 0x4a5bc116 7/13/2009 6:19:50 PM
SynTP.sys fffff880`0582c000 fffff880`05986000 0x0015a000 0x4ca54818 9/30/2010 9:31:52 PM
USBD.SYS fffff880`05986000 fffff880`05987f00 0x00001f00 0x4d8c0bfb 3/24/2011 10:28:59 PM
mouclass.sys fffff880`05988000 fffff880`05997000 0x0000f000 0x4a5bc116 7/13/2009 6:19:50 PM
GEARAspiWDM.sys fffff880`05997000 fffff880`0599dc00 0x00006c00 0x4fa2e2e1 5/3/2012 2:56:17 PM
intelppm.sys fffff880`0599e000 fffff880`059b4000 0x00016000 0x4a5bc0fd 7/13/2009 6:19:25 PM
CmBatt.sys fffff880`059b4000 fffff880`059b8500 0x00004500 0x4a5bc3b7 7/13/2009 6:31:03 PM
tosrfec.sys fffff880`059b9000 fffff880`059c1000 0x00008000 0x4c1b2426 6/18/2010 2:45:42 AM
QIOMem.sys fffff880`059c1000 fffff880`059cb000 0x0000a000 0x4a35e318 6/15/2009 12:58:48 AM
wmiacpi.sys fffff880`059cb000 fffff880`059d4000 0x00009000 0x4a5bc3b6 7/13/2009 6:31:02 PM
btfilter.sys fffff880`059d4000 fffff880`059e2000 0x0000e000 0x4cb9246c 10/15/2010 11:05:00 PM
CompositeBus.sys fffff880`059e2000 fffff880`059f2000 0x00010000 0x4ce7a3ed 11/20/2010 5:33:17 AM
AgileVpn.sys fffff880`05800000 fffff880`05816000 0x00016000 0x4a5bccf0 7/13/2009 7:10:24 PM
rasl2tp.sys fffff880`05200000 fffff880`05224000 0x00024000 0x4ce7a872 11/20/2010 5:52:34 AM
ndistapi.sys fffff880`05816000 fffff880`05822000 0x0000c000 0x4a5bccd8 7/13/2009 7:10:00 PM
ndiswan.sys fffff880`05224000 fffff880`05253000 0x0002f000 0x4ce7a870 11/20/2010 5:52:32 AM
raspppoe.sys fffff880`05253000 fffff880`0526e000 0x0001b000 0x4a5bcce9 7/13/2009 7:10:17 PM
raspptp.sys fffff880`0526e000 fffff880`0528f000 0x00021000 0x4ce7a86f 11/20/2010 5:52:31 AM
rassstp.sys fffff880`0528f000 fffff880`052a9000 0x0001a000 0x4a5bccf1 7/13/2009 7:10:25 PM
swenum.sys fffff880`05822000 fffff880`05823480 0x00001480 0x4a5bca92 7/13/2009 7:00:18 PM
ks.sys fffff880`052a9000 fffff880`052ec000 0x00043000 0x4ce7a3f3 11/20/2010 5:33:23 AM
umbus.sys fffff880`055eb000 fffff880`055fd000 0x00012000 0x4ce7a695 11/20/2010 5:44:37 AM
usbhub.sys fffff880`04b6c000 fffff880`04bc6000 0x0005a000 0x4d8c0c15 3/24/2011 10:29:25 PM
NDProxy.SYS fffff880`04bc6000 fffff880`04bdb000 0x00015000 0x4ce7a864 11/20/2010 5:52:20 AM
nvhda64v.sys fffff880`04a00000 fffff880`04a32000 0x00032000 0x4f8ef4ea 4/18/2012 12:07:54 PM
portcls.sys fffff880`04a32000 fffff880`04a6f000 0x0003d000 0x4a5bcc03 7/13/2009 7:06:27 PM
drmk.sys fffff880`04a6f000 fffff880`04a91000 0x00022000 0x4a5bd8e5 7/13/2009 8:01:25 PM
ksthunk.sys fffff880`05824000 fffff880`05829200 0x00005200 0x4a5bca93 7/13/2009 7:00:19 PM
CHDRT64.sys fffff880`0605f000 fffff880`06118000 0x000b9000 0x4cb540fd 10/13/2010 12:17:49 AM
tosporte.sys fffff880`06118000 fffff880`06129000 0x00011000 0x4a37788f 6/16/2009 5:48:47 AM
usbccgp.sys fffff880`06129000 fffff880`06146000 0x0001d000 0x4d8c0c0a 3/24/2011 10:29:14 PM
usbvideo.sys fffff880`06146000 fffff880`06173280 0x0002d280 0x4ce7a692 11/20/2010 5:44:34 AM
tosrfusb.sys fffff880`06174000 fffff880`06183480 0x0000f480 0x4cdb726f 11/10/2010 11:34:55 PM
win32k.sys fffff960`00080000 fffff960`00396000 0x00316000 0x00000000
Dxapi.sys fffff880`06184000 fffff880`06190000 0x0000c000 0x4a5bc574 7/13/2009 6:38:28 PM
tosrfbd.sys fffff880`06190000 fffff880`061d5b80 0x00045b80 0x4cda7e35 11/10/2010 6:12:53 AM
Tosrfhid.sys fffff880`061d6000 fffff880`061ebb80 0x00015b80 0x4c7b07e4 8/29/2010 8:22:44 PM
crashdmp.sys fffff880`06000000 fffff880`0600e000 0x0000e000 0x4a5bcabd 7/13/2009 7:01:01 PM
dump_iaStor.sys fffff880`0422e000 fffff880`04382000 0x00154000 0x4c8ece94 9/13/2010 8:23:32 PM
dump_dumpfve.sys fffff880`0600e000 fffff880`06021000 0x00013000 0x4a5bc18f 7/13/2009 6:21:51 PM
TSDDD.dll fffff960`005f0000 fffff960`005fa000 0x0000a000 0x00000000
luafv.sys fffff880`06021000 fffff880`06044000 0x00023000 0x4a5bc295 7/13/2009 6:26:13 PM
mbam.sys fffff880`06044000 fffff880`0604e000 0x0000a000 0x50326aa5 8/20/2012 11:49:41 AM
WudfPf.sys fffff880`04a91000 fffff880`04aaa000 0x00019000 0x5010aae5 7/25/2012 9:26:45 PM
lltdio.sys fffff880`04aaa000 fffff880`04abf000 0x00015000 0x4a5bcc92 7/13/2009 7:08:50 PM
nwifi.sys fffff880`03e4f000 fffff880`03ea2000 0x00053000 0x4a5bcc3b 7/13/2009 7:07:23 PM
ndisuio.sys fffff880`03ea2000 fffff880`03eb5000 0x00013000 0x4ce7a7e0 11/20/2010 5:50:08 AM
rspndr.sys fffff880`03eb5000 fffff880`03ecd000 0x00018000 0x4a5bcc92 7/13/2009 7:08:50 PM
HTTP.sys fffff880`03ecd000 fffff880`03f96000 0x000c9000 0x4ce793ce 11/20/2010 4:24:30 AM
vwifimp.sys fffff880`03f96000 fffff880`03fa0000 0x0000a000 0x4a5bcc40 7/13/2009 7:07:28 PM
bowser.sys fffff880`03fa0000 fffff880`03fbe000 0x0001e000 0x4d649328 2/22/2011 11:55:04 PM
mpsdrv.sys fffff880`03fbe000 fffff880`03fd6000 0x00018000 0x4a5bcc79 7/13/2009 7:08:25 PM
mrxsmb.sys fffff880`03e00000 fffff880`03e2d000 0x0002d000 0x4db78226 4/26/2011 9:40:38 PM
mrxsmb10.sys fffff880`05621000 fffff880`0566f000 0x0004e000 0x4e17c104 7/8/2011 9:46:28 PM
mrxsmb20.sys fffff880`0566f000 fffff880`05693000 0x00024000 0x4db781e9 4/26/2011 9:39:37 PM
regi.sys fffff880`05693000 fffff880`0569b000 0x00008000 0x462393ee 4/16/2007 10:19:10 AM
ATMFD.DLL fffff960`008c0000 fffff960`00921000 0x00061000 0x00000000 Adobe Type Manager Windows NT OpenType/Type 1 Font Driver 5.1 Build 237 Adobe Systems Incorporated C:\windows\system32\ATMFD.DLL
peauth.sys fffff880`056bc000 fffff880`05762000 0x000a6000 0x4a5bd8df 7/13/2009 8:01:19 PM
secdrv.SYS fffff880`05762000 fffff880`0576d000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
srvnet.sys fffff880`0576d000 fffff880`0579e000 0x00031000 0x4dba2aff 4/28/2011 10:05:35 PM
tcpipreg.sys fffff880`0579e000 fffff880`057b0000 0x00012000 0x506c62be 10/3/2012 11:07:26 AM
srv2.sys fffff880`06ab9000 fffff880`06b22000 0x00069000 0x4dba2b0a 4/28/2011 10:05:46 PM
srv.sys fffff880`06b22000 fffff880`06bba000 0x00098000 0x4dba2b1e 4/28/2011 10:06:06 PM
MpFilter.sys fffff880`06a71000 fffff880`06aa9000 0x00038000 0x5091a97a 10/31/2012 5:43:06 PM
NisDrvWFP.sys fffff880`06bba000 fffff880`06bdb000 0x00021000 0x5091a992 10/31/2012 5:43:30 PM
asyncmac.sys fffff880`06be9000 fffff880`06bf4000 0x0000b000 0x4a5bcce5 7/13/2009 7:10:13 PM
cdd.dll fffff960`007d0000 fffff960`007f7000 0x00027000 0x00000000
cdfs.sys fffff880`06a29000 fffff880`06a46000 0x0001d000 0x4a5bc112 7/13/2009 6:19:46 PM
fastfat.SYS fffff880`057b0000 fffff880`057e6000 0x00036000 0x4a5bc1f0 7/13/2009 6:23:28 PM
monitor.sys fffff880`06a0e000 fffff880`06a1c000 0x0000e000 0x4a5bc58c 7/13/2009 6:38:52 PM
hiber_iaStor.sys fffff880`0c842000 fffff880`0c996000 0x00154000 0x4c8ece94 9/13/2010 8:23:32 PM
hiber_dumpfve.sys fffff880`0c996000 fffff880`0c9a9000 0x00013000 0x4a5bc18f 7/13/2009 6:21:51 PM

 

[kaos]

no u dont need to open anything with anything, reply to this thread. click upload and select the minidump files,

we do the analysis with the files,

 

[bweier]

Link RemovedLink Removed

These are the 2 minidump files I have.

Thanks!!

 

[bweier]

Good morning and thanks to kaos if you have time to look at the minidump files in my last post.

 

[kaos]

okidokie, ive looked into this for you,

couple of things,
the driver - thpvem.sys is out of date, ( 2009 ) and will need updating, you do have a lot of toshiba drivers out of date too.

the FIRST thing we need to do is ensure you have updated all of ure drivers, such as graphics, bios, etc etc.
if u hve toshiba harddrive protection update this too,

its basically going through all of ure programs and updating them

 

[bweier]

OK. Installed most current BIOS 1.90 and thank God it went ok. Last time I flashed the BIOS my laptop ended up back at Toshiba as it failed and screwed up everything. After I got it back in early 2012 I deleted all Toshiba utilities as I didn't trust them. Re-installed the Toshiba utilities including the Harddrive protection and Service Station utility. Went through device manager and tried to update all drivers and all were "up to date". Went to the Toshiba website and downloaded/updated quite a few drivers. Not sure if many were actually out of date, but everything installed OK.

To get rid of the annoying desktop.ini error message on startup on note pad, I deleted all (29) desktop.ini files from computer. They are in the Recycle Bin right now just in case. On restart, the error message went away.

Is there an "update" file I can upload so you can check the progress?

 

[kaos]

unfortunately, i believe its a waiting game now to determine if this has been resolved by updating the software and drivers.

why have u deleted the desktop.ini files??... these files are normally hidden automatically. Desktop.ini files are just to remember data of attributes of folders etc. i wouldnt worry bout them to be quite frank. IF it happens again. DISABLE the harddrive protection since i believe the error was caused by this in the first place. if u get any more blue screens upload them. and we can check each one. we can then see if its the same driver or software that is causing this...

if ure worried about loss of data then do backups . Harddrive protection is only for like Surges/shock etc. but if u back up ure important data somewhere else then ure fine ( were here to solve these issues for u if u come across them )