Quote: Originally Posted by tjw015
I have had a big problem with BSoDs. It usually happens when I am working in Microsoft Word, which is rather unavoidable. I have had an 0xe, an 0xa and an 0xea come up. I have attached the files you requested. I have only installed one piece of software in the past month, and I have not been using it at any time when the problems have arisen.
Windows 7 . . .
- 64 bit ?
- the original installed OS on the system? Yes
- an OEM or full retail version? Received it free as an update from Microsoft
- What is the age of system (hardware)? Two years
- What is the age of OS installation (have you re-installed the OS?) Two years
Hi Tom and welcome
Most of these were Related to Thpevm.sys
HDD Protection - Shock Sensor Driver
from TOSHIBA Corporation. Yours is 3 years old. I would update it to the most current one you can find.
Also there are many old drivers
that need updating
tosrfec.sys 10/23/2006 3:33:06 AM fffff880`02df6000 fffff880`02e00000 0x0000a000 0x453c7032
FwLnk.sys 11/19/2006 10:11:04 AM fffff880`02ce9000 fffff880`02cf1000 0x00008000 0x456065f8
rimspx64.sys 7/26/2007 7:33:52 AM fffff880`051bb000 fffff880`051d2000 0x00017000 0x46a886a0
rixdpx64.sys 7/27/2007 6:45:50 AM fffff880`04928000 fffff880`0497f000 0x00057000 0x46a9ccde
OpenLibSysX64.sys 10/19/2007 1:03:47 AM fffff880`02671000 fffff880`02678000 0x00007000 0x47183ab3
TVALZ_O.SYS 11/8/2007 11:08:41 PM fffff880`015b7000 fffff880`015bbe80 0x00004e80 0x4733cf39
tdcmdpst.sys 12/10/2007 10:29:00 PM fffff880`049c5000 fffff880`049cf000 0x0000a000 0x475df5ec
rimmpx64.sys 2/20/2008 9:24:19 PM fffff880`051a6000 fffff880`051bb000 0x00015000 0x47bcd2c3
UVCFTR_S.SYS 6/26/2008 4:25:22 AM fffff880`053dd000 fffff880`053e5000 0x00008000 0x48635272
IntcHdmi.sys 6/30/2008 8:52:42 AM fffff880`0539c000 fffff880`053c0000 0x00024000 0x4868d71a
SynTP.sys 8/14/2008 10:03:12 PM fffff880`0497f000 fffff880`049c5000 0x00046000 0x48a4e3e0
spldr.sys 5/11/2009 12:56:27 PM fffff880`015bc000 fffff880`015c4000 0x00008000 0x4a0858bb
GEARAspiWDM.sys 5/18/2009 8:17:04 AM fffff880`049cf000 fffff880`049dc000 0x0000d000 0x4a1151c0
amdxata.sys 5/19/2009 1:56:59 PM fffff880`00c00000 fffff880`00c0b000 0x0000b000 0x4a12f2eb
Thpevm.SYS 6/29/2009 4:15:37 AM fffff880`01600000 fffff880`01601f80 0x00001f80 0x4a487829
ATSwpWDF.sys 7/2/2009 3:10:38 PM fffff880`082f3000 fffff880`083ac000 0x000b9000 0x4a4d062e
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.