3) Update your ATI video drivers to the latest version available from Global Provider of Innovative Graphics, Processors and Media Solutions | AMDDaemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):[DEL] DuplexSecure - FAQ [/DEL]Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
[FONT=lucida console]**************************Mon Nov 26 02:52:21.755 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112612-20420-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:18:05.300[/B]
BugCheck Code: [B]BugCheck 1A, {5003, fffff70001080000, 10017, 100390002006e}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45f3d )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000010017
Arg4: 000100390002006e
BUGCHECK_STR: 0x1a_5003
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: [B]cmdagent.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+45f3d[/B]
BIOS Version V1.20
BIOS Release Date 11/30/2009
Manufacturer TOSHIBA
Product Name Satellite L500D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 16:30:33.619 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-19921-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:03:16.164[/B]
BugCheck Code: [B]BugCheck 50, {fffffaa0049c3184, 0, fffff880012368d9, 5}[/B]
Probably caused by :[B]Ntfs.sys ( Ntfs!NtfsCommonRead+89 )[/B]
BugCheck Info: [B]PAGE_FAULT_IN_NONPAGED_AREA (50)[/B]
Arguments:
Arg1: fffffaa0049c3184, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880012368d9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: [B]WINWORD.EXE[/B]
FAILURE_BUCKET_ID: [B]X64_0x50_Ntfs!NtfsCommonRead+89[/B]
BIOS Version V1.20
BIOS Release Date 11/30/2009
Manufacturer TOSHIBA
Product Name Satellite L500D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 16:25:25.011 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112512-20373-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:00:59.431[/B]
BugCheck Code: [B]BugCheck 1A, {5003, fffff70001080000, 78f, 7b100000f5e}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+38906 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000078f
Arg4: 000007b100000f5e
BUGCHECK_STR: 0x1a_5003
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: [B]dw20.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+38906[/B]
BIOS Version V1.20
BIOS Release Date 11/30/2009
Manufacturer TOSHIBA
Product Name Satellite L500D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT][FONT=lucida console]**************************Mon Nov 26 02:52:21.755 2012 (UTC - 5:00)**************************
[COLOR=RED][B]AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)[/B][/COLOR]
[COLOR=RED][B]RtHDMIVX.sys Wed May 20 06:04:50 2009 (4A13D5C2)[/B][/COLOR]
[COLOR=RED][B]Rt64win7.sys Fri May 22 10:52:30 2009 (4A16BC2E)[/B][/COLOR]
[COLOR=RED][B]TVALZFL.sys Fri Jun 19 06:05:44 2009 (4A3B62F8)[/B][/COLOR]
[COLOR=RED][B]tos_sps64.sys Wed Jun 24 01:31:09 2009 (4A41BA1D)[/B][/COLOR]
[COLOR=RED][B]LPCFilter.sys Tue Jun 30 19:57:52 2009 (4A4AA680)[/B][/COLOR]
[COLOR=RED][B]TVALZ_O.SYS Mon Jul 13 22:19:26 2009 (4A5BEB2E)[/B][/COLOR]
[COLOR=RED][B]SynTP.sys Mon Jul 20 20:07:29 2009 (4A6506C1)[/B][/COLOR]
RTKVHD64.sys Tue Jul 28 09:00:05 2009 (4A6EF655)
atikmdag.sys Thu Jul 30 00:23:28 2009 (4A712040)
tdcmdpst.sys Thu Jul 30 04:39:35 2009 (4A715C47)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
rtl8192se.sys Mon Apr 26 13:23:06 2010 (4BD5CBFA)
[COLOR=RED][B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
cmderd.sys Wed Nov 7 17:06:57 2012 (509ADB81)
inspect.sys Wed Nov 7 17:07:02 2012 (509ADB86)
cmdhlp.sys Wed Nov 7 17:07:03 2012 (509ADB87)
cmdguard.sys Wed Nov 7 17:07:39 2012 (509ADBAB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 25 16:30:33.619 2012 (UTC - 5:00)**************************
[COLOR=RED][B]pgeffect.sys Mon Jun 22 05:00:11 2009 (4A3F481B)[/B][/COLOR]
[/FONT]Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes
to a DWORD 3 value and reboot. If the same bugcheck (STOP 0xDA) occurs again the stack trace will
identify the offending driver.
[font=lucida console]**************************Wed Nov 28 08:23:04.688 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112812-20592-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:21:31.233[/B]
BugCheck Code: [B]BugCheck 1A, {5005, fffff70001080000, 866, 79c}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ffe5 )[/B]
BugCheck Info: [B]MEMORY_MANAGEMENT (1a)[/B]
Arguments:
Arg1: 0000000000005005, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000000866
Arg4: 000000000000079c
BUGCHECK_STR: 0x1a_5005
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: [B]mscorsvw.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x1a_5005_nt!_??_::FNODOBFM::_string_+1ffe5[/B]
BIOS Version V1.20
BIOS Release Date 11/30/2009
Manufacturer TOSHIBA
Product Name Satellite L500D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 27 12:17:40.445 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112712-22417-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:02:07.006[/B]
BugCheck Code: [B]BugCheck DA, {504, fffff6fc40053fb8, 1, a7f7}[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b3eb )[/B]
BugCheck Info: [B]SYSTEM_PTE_MISUSE (da)[/B]
Arguments:
Arg1: 0000000000000504, Type of error.
Arg2: fffff6fc40053fb8
Arg3: 0000000000000001
Arg4: 000000000000a7f7
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xDA
PROCESS_NAME: [B]Skype.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0xDA_nt!_??_::FNODOBFM::_string_+b3eb[/B]
BIOS Version V1.20
BIOS Release Date 11/30/2009
Manufacturer TOSHIBA
Product Name Satellite L500D
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font][font=lucida console]**************************Wed Nov 28 08:23:04.688 2012 (UTC - 5:00)**************************
[COLOR=RED][B]AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)[/B][/COLOR]
[COLOR=RED][B]TVALZFL.sys Fri Jun 19 06:05:44 2009 (4A3B62F8)[/B][/COLOR]
[COLOR=RED][B]pgeffect.sys Mon Jun 22 05:00:11 2009 (4A3F481B)[/B][/COLOR]
[COLOR=RED][B]tos_sps64.sys Wed Jun 24 01:31:09 2009 (4A41BA1D)[/B][/COLOR]
[COLOR=RED][B]LPCFilter.sys Tue Jun 30 19:57:52 2009 (4A4AA680)[/B][/COLOR]
[COLOR=RED][B]TVALZ_O.SYS Mon Jul 13 22:19:26 2009 (4A5BEB2E)[/B][/COLOR]
tdcmdpst.sys Thu Jul 30 04:39:35 2009 (4A715C47)
amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
rtl8192se.sys Mon Apr 26 13:23:06 2010 (4BD5CBFA)
[COLOR=RED][B]AODDriver2.sys Tue Mar 6 04:55:00 2012 (4F55DEF4)[/B][/COLOR]
RTKVHD64.sys Tue Jun 19 04:50:56 2012 (4FE03D70)
atikmpag.sys Wed Jul 4 01:10:55 2012 (4FF3D05F)
atikmdag.sys Wed Jul 4 01:16:13 2012 (4FF3D19D)
aswrdr2.sys Mon Oct 8 04:23:43 2012 (50728D8F)
Rt64win7.sys Thu Oct 25 05:20:09 2012 (50890449)
SynTP.sys Thu Oct 25 22:16:32 2012 (5089F280)
aswFsBlk.SYS Tue Oct 30 18:43:04 2012 (509057F8)
aswMonFlt.sys Tue Oct 30 18:43:09 2012 (509057FD)
aswTdi.SYS Tue Oct 30 18:43:16 2012 (50905804)
aswSP.SYS Tue Oct 30 18:44:06 2012 (50905836)
aswSnx.SYS Tue Oct 30 18:44:08 2012 (50905838)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 27 12:17:40.445 2012 (UTC - 5:00)**************************
[COLOR=RED][B]RtHDMIVX.sys Wed May 20 06:04:50 2009 (4A13D5C2)[/B][/COLOR]
Rt64win7.sys Fri May 22 10:52:30 2009 (4A16BC2E)
SynTP.sys Mon Jul 20 20:07:29 2009 (4A6506C1)
RTKVHD64.sys Tue Jul 28 09:00:05 2009 (4A6EF655)
atikmdag.sys Thu Jul 30 00:23:28 2009 (4A712040)
[COLOR=RED][B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
[/font]Reboot for the changes to takeaffect (?effect?)effect.
Source: Microsoft Support Knowledge Base Entry No. 315222
- Restart your computer and start pressing the F8 key on your keyboard. On a computer that is configured for booting to multiple operating systems, you can press the F8 key when the Boot Menu appears.
- Select an option when the Windows Advanced Options menu appears, and then press ENTER.
- When the Boot menu appears again, and the words "Safe Mode" appear in blue at the bottom, select the installation that you want to start, and then press ENTER. Last Known Good Configuration: This option starts Windows by using the previous good configuration.
Source: Microsoft Support Knowledge Base No. 894278[h=3]Method 1: Rename the malicious driver by using Internet Explorer[/h]
[h=3]Method 2: In Safe Mode, rename the malicious driver by using My Computer[/h]
- Open Internet Explorer.
- In the Address box, type %windir%\system32\drivers, and then press ENTER.
- Locate the randomly named .sys file, right-click the file, and then select Rename.
- Type malware.old to rename the file, and then press ENTER.
- In the Address box, type \WINDOWS\system32, and then press ENTER.
- Locate and then rename the following files, if they exist:
- Msupd5.exe. Rename this file Msupd5.old.
- Msupd4.exe. Rename this file Msupd4.old.
- Msupd.exe. Rename this file Msupd.old.
- Reloadmedude.exe. Rename this file Reloadmedude.old.
- Close Internet Explorer.
- Restart the computer.
- Make sure that your antivirus or anti-spyware software is updated with the latest signatures, and then perform a complete system scan.
[h=3]Method 3: In Safe Mode, rename the malicious driver by using the command prompt[/h]
- Start the computer in Safe Mode. To do this, follow these steps:
- Restart the computer.
- As the computer starts, press the F8 key repeatedly (one time per second). This action will cause the Microsoft Windows Advanced Startup Menu options to appear.
- Use the UP ARROW and DOWN ARROW keys to highlight Safe Mode, and then press ENTER.
- Open Internet Explorer
- In the Address box, type %windir%\system32\drivers, and then press ENTER.
- Enable the viewing of hidden files. To do this, follow these steps:
- Click Start, and then click My Computer.
- On the Tools menu, click Folder Options.
- On the View tab, click to clear the Hide protected operating system files (Recommended) check box, and then click Yes when you receive a warning message that states that you have chosen to display protected operating system files.
- Under Hidden files and folders, click Show hidden files and folders.
- Click to clear the Hide extensions for known file types check box.
- In the Folder views area, click Apply to All Folders, and then click OK.
- Locate the folder named C:\%windir%\System32\Drivers.
- Locate any .sys file that has the following characteristics:
- A randomly generated file name that is made up of eight lowercase letters, such as "gbqxmhia.sys," "upzvlbvv.sys," or "jsbmefvk.sys"
- A date of January 11, 2005
- A size of 14 KB (13,824 bytes)
- A hidden attribute that is set
Note A file that has its hidden attribute set displays an "HA" in the Attributes column in Windows Explorer. For instructions on how to view the Attributes column, see steps 5a and 5b of the procedure that is described in the "More information" section.- It has no version, product name, or manufacturer information.
- For each file that you locate, right-click the file, and then select Rename.
- Type malware1.old to rename the first file, and then press ENTER.
Note Type malware2.old to rename the second file, type malware3.old to rename the third file, and so on.- Locate the %windir%\System32 folder.
- Rename the following files, if they exist:
- Msupd5.exe. Rename this file msupd5.old.
- Msupd4.exe. Rename this file Msupd4.old.
- Msupd.exe. Rename this file Msupd.old.
- Reloadmedude.exe. Rename this file Reloadmedude.old.
- Restart the computer.
- Make sure that your antivirus or anti-spyware software is updated with the latest signatures, and then perform a complete system scan.
- Start the computer in Safe Mode. To do this, follow these steps:
- Restart the computer.
- As the computer starts, press the F8 key repeatedly (one time per second). This action will cause the Microsoft Windows Advanced Startup Menu options to appear.
- Use the UP ARROW and the DOWN ARROW keys to select Safe Mode with Command Prompt, and then press ENTER.
- Click Start, click Run, type cmd in the Open box, and then click OK.
- At the command prompt, type CD %windir%\system32\drivers, and then press ENTER.
- Type Dir /ah, and then press ENTER.
- You will see text that is similar to the following text. The .sys file name will be randomly generated.
Directory of C:\WINDOWS\system32\drivers01/11/2005 09:18 AM 13,824 gbqxmhia.sys 1 File(s) 13,824 bytes 0 Dir(s) 961,425,408 bytes free
- Type Attrib –s –h RandomFilename, and then press ENTER. This action removes the system attributes and the hidden attributes from the file.
Note The placeholder RandomFilename represents the name of the .sys file that is displayed after you perform step 5. For example, for the file name that is specified in the example in step 5, you would type Attrib –s –h gbqxmhia.sys.- Type Ren RandomFilename malware.old, and then press ENTER. This action renames the randomly named file.
- Type CD, and then press ENTER. This changes the command line to the %windir%\System32 folder.
- Type the following commands one at a time, and then press ENTER after you type each command:
Ren msupd5.exe msupd5.old
Ren msupd4.exe msupd4.old
Ren msupd.exe msupd.old
Ren reloadmedude.exe reloadmedude.old
Note If you receive the following error message, you can safely ignore the message, because it indicates that the targeted file does not exist:The system cannot find the file specified.
- Type Exit, and then press ENTER.
- Restart the computer.
- Make sure that your antivirus or anti-spyware software is updated with the latest signatures, and then perform a complete system scan.
to add on to usasma's post.
A few of those dumps point to a problem with your memory. Memory can be found in your Graphics Card, RAM (obviously), CPU and Hard Disk.
Try running
Memtest86+ - Advanced Memory Diagnostic Tool ---- 7 to 8 hours (or overnight)
Free Software - GIMPS ---- up to 3 hours (or until error shows)
HD Tune website ---- run for 2 to 3 days
or use usasma's hardware diagnostics here: Hardware Diagnostics
Another way to test your RAM (RAM only):
Remove all RAM sticks (except one) (be sure to turn the computer power off before doing this) and restart your computer. If it boots, that means the current RAM stick is working ok.
Repeat with all the other RAM sticks until you find one faulty.
You can also do the above process with memtest to do a more thorough check.
PAGE_FAULT_IN_NONPAGED_AREA:
Use this link: A description of the Safe Mode Boot options in Windows XP and boot into the Last known Good Configuration. (If you can't access the link:
Source: Microsoft Support Knowledge Base Entry No. 315222
You can also try this link: The computer may automatically restart, or you may receive a "serious error" message or a Stop error message in Windows Server 2003, in Windows XP, or in Windows 2000 to solve the problem. If that link doesn't work:
Source: Microsoft Support Knowledge Base No. 894278
Not sure how to tackle the last one: SYSTEM_PTE_MISUSE
but I'm quite sure it has something to do with your memory.
the way to enter Safe Mode is the same in Windows 7.