Tech Support banner

Status
Not open for further replies.
1 - 15 of 15 Posts

·
Registered
Joined
·
8 Posts
Discussion Starter #1
I'm getting the driver_irql_not_less_or_equal BSOD for past 2 days.. before my computer was doing this every 10-14 days.. but for past 2 days its doing it very frequently.. I followed the instructions using verifier and zipped the minidumps.. attached here.. please help..!!
 

·
Registered
Joined
·
3,260 Posts
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Hello,

It appears that you have some network issue. Norton is blamed three times, so remove it according to these directions: Norton Product Support | Installation and Uninstall

Replace it with MSE: http://www.microsoft.com/security_essentials

Your Conextent modem drivers were blamed several times; please install updated ones from here: Conexant: Support

If you cannot obtain newer ones, physically remove the modem card from the PCI slot, or disable it in the BIOS.
Code:
VSTBS26.SYS             Wed Oct 15 20:54:06 2008 (48F690AE)
VSTCNXT6.SYS            Wed Oct 15 20:52:22 2008 (48F69046)
VSTDPV6.SYS             Wed Oct 15 20:57:45 2008 (48F69189)
Finally, sxuptp.sys is blamed once. I'm not entirely sure what it is, but search results show it may be a driver for a Belkin network hub? Try to update the drivers, or again, remove the device completely.

If you get more BSODs, please upload a full jcgriff2 report, according to these directions: http://www.techsupportforum.com/forums/f299/blue-screen-of-death-bsod-posting-instructions-windows-7-and-vista-452654.html

...Summary of the dumps:
Code:
[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 15 10:39:39.906 2011 (UTC - 4:00)
System Uptime: 0 days 13:50:15.060
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
Probably caused by : IDSvia64.sys ( IDSvia64+3b0d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_IDSvia64+3b0d6
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Mar 14 13:46:42.386 2011 (UTC - 4:00)
System Uptime: 0 days 0:35:58.355
*** WARNING: Unable to verify timestamp for sxuptp.sys
*** ERROR: Module load completed but symbols could not be loaded for sxuptp.sys
Probably caused by : sxuptp.sys ( sxuptp+1343d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_sxuptp+1343d
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar  3 11:32:43.922 2011 (UTC - 4:00)
System Uptime: 3 days 20:34:22.182
*** WARNING: Unable to verify timestamp for VSTBS26.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTBS26.SYS
Probably caused by : VSTBS26.SYS ( VSTBS26+16760 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VSTBS26+16760
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Feb 17 14:22:13.169 2011 (UTC - 4:00)
System Uptime: 0 days 23:55:16.154
*** WARNING: Unable to verify timestamp for VSTBS26.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTBS26.SYS
Probably caused by : VSTBS26.SYS ( VSTBS26+43677 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VSTBS26+43677
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb  9 15:59:45.115 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:19.865
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for mup.sys - 
*** WARNING: Unable to verify timestamp for SRTSP64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP64.SYS
Probably caused by : mup.sys ( mup+169d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x103
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x103_mup+169d
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb  9 15:54:22.976 2011 (UTC - 4:00)
System Uptime: 0 days 1:21:53.789
*** WARNING: Unable to verify timestamp for VSTBS26.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTBS26.SYS
Probably caused by : VSTBS26.SYS ( VSTBS26+4efcc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VSTBS26+4efcc
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Feb  9 14:20:26.599 2011 (UTC - 4:00)
System Uptime: 0 days 15:41:10.427
*** WARNING: Unable to verify timestamp for VSTBS26.SYS
*** ERROR: Module load completed but symbols could not be loaded for VSTBS26.SYS
Probably caused by : VSTBS26.SYS ( VSTBS26+4efcc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_VSTBS26+4efcc
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Feb  8 21:08:09.457 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:08.285
*** WARNING: Unable to verify timestamp for SYMTDIV.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDIV.SYS
Probably caused by : SYMTDIV.SYS ( SYMTDIV+4d31f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  ccsvchst.exe
FAILURE_BUCKET_ID:  X64_0x50_SYMTDIV+4d31f
SystemProductName = GT5636E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]
 

·
Registered
Joined
·
8 Posts
Discussion Starter #5
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Thanks will try these instructions.. by the way, the BSODs are happening mostly while watching movies on computer.. I just connected and installed new D-Link DIR-655 router couple of days ago.. could you tell me what caused the recent BSODs from past 2 days..?

Thanks a bunch
 

·
Registered
Joined
·
3,260 Posts
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

The Match 15th dump points to IDSvia64.sys, a component of Norton. The March 14th dump points to sxuptp.sys.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #7
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Hi Jonathan,

I again got the VSTBS26.SYS BSOD.. I searched on the Conexant site for driver update but there is none for Windows 7..

so now if I physically remove the modem card from the PCI slot, or disable it in the BIOS, then how would it effect my computer?? What would stop working??
 

·
Registered
Joined
·
2,210 Posts
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Are you or will you be planning to use a dialup connection on your PC? If not, you can uninstall and get rid of the Conexant modem drivers altogether. All it is is a 56k modem.

This is the not the first time I saw Conexant modem drivers mess up with other drivers.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #9
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Thanks VirGnarus,

That helps. I won't be using the dial-up service so good to know that i can get rid of it. So the best way is to disable it in the BIOS?? What should I look for in the BIOS?
 

·
Registered
Joined
·
3,260 Posts
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

If you have a physical modem card installed, you won't be able to disable it in the BIOS; just remove it from the computer.

If your modem is a chip on the motherboard, check around in the Advanced tab; you'll know what the option is when you see it.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #11
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Great.. Thanks Jonathan.. I will try this out..!!
 

·
Registered
Joined
·
8 Posts
Discussion Starter #12
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Hi Jonthan & VirGnarus,

Didn't see the drivers in the BIOS (advanced), so removed the physical modem card from the computer.. well now will have to wait and see if I still get the BSODs.. only difference I have seen so far is that the network icon in the taskbar has X on it, meaning not connected to the internet.. but internet is connected and works fine..

Hopefully no more BSODs..

Thanks for all your help..!!! :3-thumbup
 

·
Registered
Joined
·
3,260 Posts
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

Sounds good so far! Let us know how it works out.
 

·
Registered
Joined
·
8 Posts
Discussion Starter #14
Re: Getting Continuous BSODs For Past 2 Days.. Help!!

hey guys.. I think the problem is solved.. no BSODs for 5 days now..!!!!!

Thanks a lot.. you guys are great...!!!! :grin: :grin:
 
1 - 15 of 15 Posts
Status
Not open for further replies.
Top