BSOD is still there...

[Razo]

Ok, my system is much more better now since I've found the right drivers for things. However, I'm still getting BSOD's. I get them at least twice a day. It used to be about 6 everyday.

Here is my latest dmp file:
View attachment 76642
View attachment 76648

 

[Tews]

Your .dmp file shows USBPORT.sys as the cause of your crash ... Go to your manufacturers website and download the latest USB driver and test...

View attachment 76647

 

[Razo]

Your .dmp file shows USBPORT.sys as the cause of your crash ... Go to your manufacturers website and download the latest driver and test...

View attachment 76647

Yep. That's the message that always appears, usbport.sys. The culprit is most probably my wireless LAN adapter. I have all the latest drivers for the lan adapter that I got from the site that were built for windows 7.

Also, this is a custom made computer. Would I need to go to the motherboard's site and get some sort of update from there?

 

[Tews]

Yes... Your motherboards site should have the driver that you need..

 

[Razo]

Yes... Your motherboards site should have the driver that you need..

Hmm, I can't seem to find anything.

My Motherboard is an MSI SiS 645DX and well, there seems to be nothing about usb and/or anything related.

 

[zigzag3143]

Ok, my system is much more better now since I've found the right drivers for things. However, I'm still getting BSOD's. I get them at least twice a day. It used to be about 6 everyday.

Here is my latest dmp file:
View attachment 76642
View attachment 76648

This DMP was probably caused by your zone alarm (sptd.sys). You should replace it with microsoft security essentials. There is a known problem with ZAP.

Also if you are overclocking stop
if you are running daemon tools or Alcohol 120 they should be remoeved.


Let us know if you need help

Ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 16:34:34.905 2010 (GMT-4)
System Uptime: 0 days 0:12:51.202
BugCheck D1, {daa5e314, 2, 1, 8f6fdee2}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+13882 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe

 

[Razo]

Ok, my system is much more better now since I've found the right drivers for things. However, I'm still getting BSOD's. I get them at least twice a day. It used to be about 6 everyday.

Here is my latest dmp file:
View attachment 76642
View attachment 76648

This DMP was probably caused by your zone alarm (sptd.sys). You should replace it with microsoft security essentials. There is a known problem with ZAP.

Also if you are overclocking stop
if you are running daemon tools or Alcohol 120 they should be remoeved.


Let us know if you need help

Ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 16:34:34.905 2010 (GMT-4)
System Uptime: 0 days 0:12:51.202
BugCheck D1, {daa5e314, 2, 1, 8f6fdee2}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+13882 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe

Okay got rid of daemon tools. Only needed it once, don't know why I didn't completely remove it.

I don't have zone-alarm.

 

[zigzag3143]

Ok, my system is much more better now since I've found the right drivers for things. However, I'm still getting BSOD's. I get them at least twice a day. It used to be about 6 everyday.

Here is my latest dmp file:
View attachment 76642
View attachment 76648

This DMP was probably caused by your zone alarm (sptd.sys). You should replace it with microsoft security essentials. There is a known problem with ZAP.

Also if you are overclocking stop
if you are running daemon tools or Alcohol 120 they should be removed.


Let us know if you need help

Ken

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 16:34:34.905 2010 (GMT-4)
System Uptime: 0 days 0:12:51.202
BugCheck D1, {daa5e314, 2, 1, 8f6fdee2}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+13882 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe

Okay got rid of daemon tools. Only needed it once, don't know why I didn't completely remove it.

I don't have zone-alarm.

Great Now its a wait and see. If you get more BSOD''s up load the DMP files. If this goes on much longer we should consider running driver verifier. It will make you system crash but will probably tell you which driver caused it.

If you havent already you should run a system file check to verify and repair your system files.
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results as it will narrow the search

Ken

EDIT: spdt.sys is NOT from zone alarm. It is used by virtual dvd drive applications like alcohol 120 and daemon tools. My apologies for the error

 

[Razo]

Great Now its a wait and see. If you get more BSOD''s up load the DMP files. If this goes on much longer we should consider running driver verifier. It will make you system crash but will probably tell you which driver caused it.

If you havent already you should run a system file check to verify and repair your system files.
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results as it will narrow the search

Ken

Okay Ken. I have started the scan and it's running smoothly, for now.
I suspect the problem will be with usbport.sys and most probably will be caused by my adapter. The blue screen usually/always happens on the internet and always comes up with driver_irql_not_equal and says usbport.sys.

Thanks in advance Ken.

Razo

 

[Razo]

UPDATE KEN.

Okay, BSOD again, no dmp file though for some reason, have no clue why not. However of course it was a usbport.sys problem.

 

[Razo]

The problem only seems to be caused by usbport.sys. Also can you tell me why there was no .dmp file created?

EDIT: I am re-doing the sfc /scannow command in cmd with run as administrator. Hopefully it can detect and fix the issue.

 

[Razo]

UPDATE 3.

Okay, no BSOD for about half an hour. The sfc /scannow did detect some problems and fixed them. Hopefully no more BSOD.