Tech Support Forum banner

BSOD a few minutes after startup - vista

2352 Views 8 Replies 3 Participants Last post by  alfie
I am having multiple BSOD crashes which happen a few minutes after startup, then I have to repair startup a few times. It happens with almost anything, IE or even windows explorer. In normal setting, none of the diagnostics tools or autoruns work. After BSOD minidum is not created. Safe mode seems to be working fine. I have performed the required tests in safe mode.
Some information as much as I could gather:
- HP Pavilion desktop model m9450f
- Vista Home Premium edition SP2
- x64
- System came with windsows installed
- about 2 years old
- CPU: Intel Core 2 Quad CPU Q9300 @2.50GHz
- Video: NVIDIA GEforce 9800GT

System health report (perfmon /report) gave the error, path not found.

Verifier doesn't work in normal mode and in safe mode can't be enabled, even after rebooting, it is still disabled.

Thank you so much in advance.

Attachments

Status
Not open for further replies.
1 - 9 of 9 Posts
Several errors in MSINFO32 revolving around your Norton/Symantec protection software.
Please do the following:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: http://www.carrona.org/freeav.html
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
More to follow after the dump files finish running.

BTW - Driver Verifier does work in Safe Mode, but errors with using it may indicate a malware infection. Have you scanned for malware with something other than Norton (because it seems to be having issues)? If not, try these free, online malware scans: http://www.carrona.org/malware.html
3 out of 9 errors blame Norton - I'd suspect that it's to blame.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers (You can look them up here: http://www.carrona.org/dvrref.html ).
Please pay particular attention to any dated 2008 or earlier:
Code:
PS2.sys      Thu Sep 07 18:49:03 2006 - HP Multimedia Keyboard Driver - http://www.carrona.org/dvrref.html#PS2.sys
PdiPorts.sys Thu Nov 16 19:31:16 2006 - PdiPorts Device Driver - http://www.carrona.org/dvrref.html#PdiPorts.sys
livecamv.sys Mon Feb 05 04:36:46 2007 - Creative Livecam driver system driver - http://www.carrona.org/dvrref.html#livecamv.sys
iastor.sys   Thu Dec 04 15:47:09 2008 - Intel Storage drivers - http://www.carrona.org/dvrref.html#iastor.sys
V0540Vid.sys Mon Apr 28 05:12:54 2008 - Creative Camera VF0540 Driver - http://www.carrona.org/dvrref.html#V0540Vid.sys
CtClsFlt.sys Tue May 06 23:20:29 2008 - Creative Camera Class Upper Filter Driver - http://www.carrona.org/dvrref.html#CtClsFlt.sys
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul 16 16:26:29.191 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:58.306
BugCheck 50, {fffffa600ac81001, 0, fffff9600004f14b, 0}
Probably caused by : win32k.sys ( win32k!draw_clrt_nf_ntb_o_to_temp_start+7b )
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Mon Jul 12 11:47:29.284 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.971
BugCheck 1A, {782, fffffa6007ba7740, fffff980038c0000, fffff8800009b690}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1895f )
BUGCHECK_STR:  0x1a_782
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul 11 21:15:39.802 2010 (UTC - 4:00)
System Uptime: 0 days 5:45:57.172
BugCheck 50, {fffff880bfaece60, 0, fffffa6009e85199, 5}
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : SRTSP64.SYS ( SRTSP64+4e199 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  SearchProtocolH
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul 11 15:00:32.279 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:31.363
BugCheck A, {38, 2, 0, fffff80002455070}
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : SRTSP64.SYS ( SRTSP64+36fcc )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchProtocolH
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Sun Jul 11 14:53:55.684 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:30.762
BugCheck 1A, {41790, fffffa80062308b0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1c42e )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  9 20:23:09.903 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:03.713
BugCheck 1A, {41790, fffffa800623bd70, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1c42e )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SearchIndexer.e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  9 19:54:53.281 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:39.013
BugCheck BE, {fffff68000aa1a00, 37000020d4db025, fffffa600899d9b0, b}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d00d )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  SLsvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  9 15:54:29.639 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:31.745
BugCheck 50, {fffffa80239e61c8, 0, fffff800026c89b8, 2}
Probably caused by : ntkrnlmp.exe ( nt!ObpIncrementHandleCount+198 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 6002.18209.amd64fre.vistasp2_gdr.100218-0019
Debug session time: Fri Jul  9 15:52:49.710 2010 (UTC - 4:00)
System Uptime: 7 days 2:27:14.029
BugCheck 50, {fffff90000003388, 0, fffff80002594972, 7}
*** WARNING: Unable to verify timestamp for SYMEFA64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMEFA64.SYS ( SYMEFA64+3b0e )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]
See less See more
thank you usasma for the help and instructions. But I'm still having the same problems.

- First of all, I still can't do anything in normal mode without going to BSOD, so everything in this post is done in safe mode.

- I removed Norton 360 and all its remnants as instructed.

- I updated (or attempted to update) the drivers. I think PS2.sys didn't install, after running the exe file I got from HP, it needs to restart and after restart, it's the same old driver again. I think it might need to be done in normal mode which is not possible for me.

- (by the way what is the safest way to unistall a driver before installing the new one? will running the exe file be enough?)

- I installed and ran Microsoft security essential, no malware found.

- When BSOD happens, it is a different error every time and at the bottom of screen it says:
"collecting data for crash dump...
initializing disk for flash dump...."
and it stays there, I've waited but nothing else happens, so I have to just power off manually.

Anyways I ran new diagnostics (in safe mode!) and the file is attached.

Any help will be greatly appreciated.

Attachments

See less See more
So, are all the BSOD's from running in Safe Mode?
If so, that rules out most of the 3rd party drivers.

But, first you've got to get rid of the Symantec stuff that's loading on your system.
If you didn't run the Norton Removal tool - then do so now.
If you did run it, please open Windows Explorer as an Administrator (go to Start...All Programs...Accessories...Windows Explorer and right click on it. Then select "Run as administrator")
Then go to C:\Windows\System32\drivers and rename:
SYMDS64.SYS to SYMDS64.BAK
SYMEFA64.SYS to SYMEFA64.BAK

Then reboot to ensure that the drivers aren't loaded.

The second BSOD blames this component:
Probably caused by : ø?ÿø?ÿ?ÿ?ÿ`?ÿ
I don't have any idea of what it is - do you?
See less See more
No, I think I didn't word my post right. The crash only happens in normal mode, there is no crash in safe mode.
I ran the Norton removal tool and those 2 drivers (SYMDS64 and SYMEFA64) don't exist in the drivers directory anymore.


As for that strange jumble of characters, I have no idea either, any way I can figure out what it is?

Any idea would help, I'm getting frustrated, thinking about using my recovery disks which I have never done before, but if I do use it, will it delete all my installed programs and documents?

Thanks again for the support.
Since you can run OK in SAFEMODE, use MSCONFIG to disable start-up apps 1-by-1 to determine which, if any, is the culprit.

http://support.microsoft.com/kb/331796

Regards. . .

jcgriff2

.
I agree w/jcgriff2

If you use your restore disks it will reset your computer to the way it was the day that it left the factory. It will delete your installed programs and documents.

If you want to do that, please post back for instructions on backing up your data. Unfortunately, there's no easy way to save the installed programs - so you'll either have to use the CD's that they came on, or download fresh copies from their website(s).
Performed a clean startup as instructed in the Microsoft support site. Still get BSOD, so I can only conclude that one of the Windsows services is corrupt not a third party service.
Trying to run a system scan for malware, hoping that is the case, tried a few scanners mentioned in your replies, they crash the system half way through even in safe mode.

Still working on it, will update if anything changes. I don't know what else I should do since it seems that it's not the fault of a third party application.
1 - 9 of 9 Posts
Status
Not open for further replies.
Top