file here
A abdallah Member Joined Jun 25, 2013 Posts 6 Jun 25, 2013 #2 minidump here Attachments Minidump.zip 34.2 KB · Views: 2
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,446 Location New Jersey Shore Jun 25, 2013 #3 Hi - The last 2 dumps had bugcheck 0x50 = invalid memory referenced and named NVIDIA video drivers as the probable cause. The driver lists show you recently updated NVIDIA - Code: nvlddmkm.sys Sun May 12 15:09:45 2013 (518FE8F9) nvlddmkm.sys Sat Dec 29 01:47:52 2012 (50DE9218) http://sysnative.com/drivers/driver.php?id=nvlddmkm.sys Daemon Tools/ Alcohol 120 are known to cause BSODs in Windows 7. Remove all virtual devices for now and see if BSODs subside. If so, reinstall - Code: sptd.sys Tue Nov 23 06:47:37 2010 (4CEBA9D9) - Daemon/ Alcohol http://sysnative.com/drivers/driver.php?id=sptd.sys RAM failure is another possibility. If BSODs continue, run memtest86+ one stick at a time, alternate the slots - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html Regards. . . jcgriff2 BSOD SUMMARY Code: Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\062513-76346-01.dmp] Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Debug session time: Tue Jun 25 16:09:41.367 2013 (UTC - 4:00) System Uptime: 0 days 0:04:45.428 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+8bf08a ) DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: nvstwiz.exe FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+8bf08a Bugcheck code 00000050 Arguments fffff9cf`b902c40c 00000000`00000001 fffff880`062d408a 00000000`00000005 BiosVersion = 2.30 BiosReleaseDate = 11/24/11 SystemManufacturer = TOSHIBA SystemProductName = Satellite A660 MaxSpeed: 1730 CurrentSpeed: 1729 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\062313-79342-01.dmp] Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Debug session time: Sun Jun 23 08:15:46.779 2013 (UTC - 4:00) System Uptime: 3 days 19:08:49.841 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+90089a ) DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: nvstwiz.exe FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+90089a Bugcheck code 00000050 Arguments fffff9c2`8bd376ec 00000000`00000001 fffff880`0633e89a 00000000`00000005 BiosVersion = 2.30 BiosReleaseDate = 11/24/11 SystemManufacturer = TOSHIBA SystemProductName = Satellite A660 MaxSpeed: 1730 CurrentSpeed: 1729 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Hi - The last 2 dumps had bugcheck 0x50 = invalid memory referenced and named NVIDIA video drivers as the probable cause. The driver lists show you recently updated NVIDIA - Code: nvlddmkm.sys Sun May 12 15:09:45 2013 (518FE8F9) nvlddmkm.sys Sat Dec 29 01:47:52 2012 (50DE9218) http://sysnative.com/drivers/driver.php?id=nvlddmkm.sys Daemon Tools/ Alcohol 120 are known to cause BSODs in Windows 7. Remove all virtual devices for now and see if BSODs subside. If so, reinstall - Code: sptd.sys Tue Nov 23 06:47:37 2010 (4CEBA9D9) - Daemon/ Alcohol http://sysnative.com/drivers/driver.php?id=sptd.sys RAM failure is another possibility. If BSODs continue, run memtest86+ one stick at a time, alternate the slots - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html Regards. . . jcgriff2 BSOD SUMMARY Code: Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\062513-76346-01.dmp] Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Debug session time: Tue Jun 25 16:09:41.367 2013 (UTC - 4:00) System Uptime: 0 days 0:04:45.428 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+8bf08a ) DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: nvstwiz.exe FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+8bf08a Bugcheck code 00000050 Arguments fffff9cf`b902c40c 00000000`00000001 fffff880`062d408a 00000000`00000005 BiosVersion = 2.30 BiosReleaseDate = 11/24/11 SystemManufacturer = TOSHIBA SystemProductName = Satellite A660 MaxSpeed: 1730 CurrentSpeed: 1729 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\062313-79342-01.dmp] Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Debug session time: Sun Jun 23 08:15:46.779 2013 (UTC - 4:00) System Uptime: 3 days 19:08:49.841 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+90089a ) DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: nvstwiz.exe FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+90089a Bugcheck code 00000050 Arguments fffff9c2`8bd376ec 00000000`00000001 fffff880`0633e89a 00000000`00000005 BiosVersion = 2.30 BiosReleaseDate = 11/24/11 SystemManufacturer = TOSHIBA SystemProductName = Satellite A660 MaxSpeed: 1730 CurrentSpeed: 1729 ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
A abdallah Member Joined Jun 25, 2013 Posts 6 Jun 27, 2013 #4 I have removed magdisc and deamon tools from my pc, and started memtest86+, but no errors in red appeared i have downloaded the latest NVidia driver updates, and before installing them I did a registry clean up for my pc, than I performed I clean installation for the new drivers, and restarted my computer afterwards. after the restart I tried to launch the 3d vision and, suddenly BSOD appears again....
I have removed magdisc and deamon tools from my pc, and started memtest86+, but no errors in red appeared i have downloaded the latest NVidia driver updates, and before installing them I did a registry clean up for my pc, than I performed I clean installation for the new drivers, and restarted my computer afterwards. after the restart I tried to launch the 3d vision and, suddenly BSOD appears again....
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,446 Location New Jersey Shore Jun 27, 2013 #5 Hi - See if Driver Verifier flags any 3rd party drivers - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html Let it run for at least 24 hours. Upon BSOD, please re-run - https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html Regards. . . jcgriff2
Hi - See if Driver Verifier flags any 3rd party drivers - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html Let it run for at least 24 hours. Upon BSOD, please re-run - https://www.sysnative.com/forums/bs...g-instructions-windows-8-7-windows-vista.html Regards. . . jcgriff2
A abdallah Member Joined Jun 25, 2013 Posts 6 Jun 28, 2013 #6 hello Jcgriff2 I have run verifier.exe as you've recommended and I have chosen all the drivers except the ones that belong to Microsoft, and as windows logo starts, it gives me a bsod so I did a system restore. but sir, as I was choosing the drivers from "verifier" I saw that sptd.sys is still in the list and the publisher is <unknown>, although I did uninstall deamon tools as you've suggested, justed wanted you to know.... Thanks in advance !!
hello Jcgriff2 I have run verifier.exe as you've recommended and I have chosen all the drivers except the ones that belong to Microsoft, and as windows logo starts, it gives me a bsod so I did a system restore. but sir, as I was choosing the drivers from "verifier" I saw that sptd.sys is still in the list and the publisher is <unknown>, although I did uninstall deamon tools as you've suggested, justed wanted you to know.... Thanks in advance !!
jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,446 Location New Jersey Shore Jun 28, 2013 #7 Hi - Was there a driver name on the BSOD? Driver Verifier apparently flagged a boot driver. The system restore likely wiped the dump out. Disable sptd.sys via the Registry - 1. Create system restore point START | type create | "Create a system restore point" 2. Go in to regedit - START | type regedit Code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sptd Type REG_DWORD 0x1 Start REG_DWORD 0x0 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\Drivers\sptd.sys DisplayName REG_SZ sptd Group REG_SZ Boot Bus Extender Tag REG_DWORD 0x3 - go to the SPTD key in red - 2x-click on sptd "folder" - locate "Start" - 2x-click on blue icon next to "Start" - change the DWORD 0 to 4 (disable) REF: [SOLVED] BSOD from ntoskrnl.exe and others - Tech Support Forum Apologies for detailed instructions as you seem to know your way around Windows very well. Regards. . . jcgriff2 `
Hi - Was there a driver name on the BSOD? Driver Verifier apparently flagged a boot driver. The system restore likely wiped the dump out. Disable sptd.sys via the Registry - 1. Create system restore point START | type create | "Create a system restore point" 2. Go in to regedit - START | type regedit Code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sptd Type REG_DWORD 0x1 Start REG_DWORD 0x0 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\Drivers\sptd.sys DisplayName REG_SZ sptd Group REG_SZ Boot Bus Extender Tag REG_DWORD 0x3 - go to the SPTD key in red - 2x-click on sptd "folder" - locate "Start" - 2x-click on blue icon next to "Start" - change the DWORD 0 to 4 (disable) REF: [SOLVED] BSOD from ntoskrnl.exe and others - Tech Support Forum Apologies for detailed instructions as you seem to know your way around Windows very well. Regards. . . jcgriff2 `
A abdallah Member Joined Jun 25, 2013 Posts 6 Jun 29, 2013 #8 well thank goodness sptd.sys was removed now we have some progress, my verifier.exe did not give a bsod at windows startup, but after the restart I thought that verifier will launch but i don't see nothing goin on. how can i know if its working right now or. although I wrote in cmd verifier/query it showed me the entire list and details of the drivers chosen. but when does it stop working or when does it finish that's the question. Thank you again jcgriff2
well thank goodness sptd.sys was removed now we have some progress, my verifier.exe did not give a bsod at windows startup, but after the restart I thought that verifier will launch but i don't see nothing goin on. how can i know if its working right now or. although I wrote in cmd verifier/query it showed me the entire list and details of the drivers chosen. but when does it stop working or when does it finish that's the question. Thank you again jcgriff2
A abdallah Member Joined Jun 25, 2013 Posts 6 Jun 29, 2013 #9 well thank goodness the sptd.sys disappeared now my verifier doesn't give me a bsod on startup, but when windows start, I don't see any verifier.exe running. how can I make sure its running, and when do I know its finished thanks again jcgriff2
well thank goodness the sptd.sys disappeared now my verifier doesn't give me a bsod on startup, but when windows start, I don't see any verifier.exe running. how can I make sure its running, and when do I know its finished thanks again jcgriff2
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jun 29, 2013 #10 Hi, You can go into the GUI for verifier.exe and select 'display existing settings'. Regards, Patrick
Hi, You can go into the GUI for verifier.exe and select 'display existing settings'. Regards, Patrick
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 9,910 Location %systemroot% Jun 30, 2013 #11 Alternatively, open a elevated command prompt, and then type the following command: Code: verifier /query
Alternatively, open a elevated command prompt, and then type the following command: Code: verifier /query