Blue Screen of DEATH with SQL Server 2005

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

Blue Screen of DEATH with SQL Server 2005

Author

Topic

russray
Starting Member

27 Posts

Posted - 2008-02-28 : 16:42:32

I am hoping someone can guide me through this error. It appears SQL Server 2005 Management Studio might have a bug. What I am accomplishing deleting several rows from several tables inside SSMS. However, after about 4 or five deletions, I get the BLUE SCREEN of DEATH.

I can repeat this pattern.

Thanks for taking the time to read my post.

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-02-28 : 17:22:02

????? Blue screen of Death? Didn't get it

russray
Starting Member

27 Posts

Posted - 2008-02-28 : 17:39:28

quote:
Originally posted by sodeep

????? Blue screen of Death? Didn't get it

We are "walking" on memory locations and the O/S blows up. Micrsoft Windows shows a blue screen. One must reboot system.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-02-28 : 17:41:51

quote:
Originally posted by sodeep

????? Blue screen of Death? Didn't get it

You must be rather new to the Windows operation system if you don't know what the BSOD is.

russray,

What service pack of SQL Server 2005 do you have installed on your client machine? A lot of people don't realize that service packs and security patches aren't only for the database server/engine, but also for the client machines.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

russray
Starting Member

27 Posts

Posted - 2008-02-28 : 17:47:13

quote:
Originally posted by tkizer

quote:
Originally posted by sodeep

????? Blue screen of Death? Didn't get it

You must be rather new to the Windows operation system if you don't know what the BSOD is.

russray,

What service pack of SQL Server 2005 do you have installed on your client machine? A lot of people don't realize that service packs and security patches aren't only for the database server/engine, but also for the client machines.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

When I run SELECT @@VERSION

I am running 9.00.1406.00, Service Pack 2

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-02-28 : 18:15:10

That's not what I mean. That information is for the database server. Are you running Management Studio from the server or from your client machine?

But 1406 isn't sp2. When it says sp2, it is referring to the operation system. 1406 is actually RTM which means no service packs have been installed. You need to get yourself up to at least build 3054 which is sp2 plus a cumulative patch. I believe we are on build 3200.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

russray
Starting Member

27 Posts

Posted - 2008-02-29 : 10:27:00

First, thank you for responding to my post! Okay, here is information from the SSMS


Microsoft SQL Server Management Studio	 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC)	 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML				2.6 3.0 4.0 5.0 6.0 
Microsoft Internet Explorer		6.0.2900.2180
Microsoft .NET Framework		2.0.50727.1433
Operating System			5.1.2600

I understand I need to upgrade to sp2 and apply cummulative update pack.

jezemine
Master Smack Fu Yak Hacker

2886 Posts

Posted - 2008-02-29 : 11:12:27

quote:
Originally posted by russray

It appears SQL Server 2005 Management Studio might have a bug.

what???? impossible!

elsasoft.org

russray
Starting Member

27 Posts

Posted - 2008-02-29 : 14:29:11

okay after installing SQL Server 2005 Service Pack 2:


Microsoft SQL Server Management Studio	  9.00.3042.00
Microsoft Analysis Services Client Tools  2005.090.3042.00
Microsoft Data Access Components (MDAC)   2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML				  2.6 3.0 4.0 5.0 6.0 
Microsoft Internet Explorer		  6.0.2900.2180
Microsoft .NET Framework		  2.0.50727.1433
Operating System			  5.1.2600

russray
Starting Member

27 Posts

Posted - 2008-02-29 : 15:01:58

Okay, the Service Pack 2 fix my problem--BSD. I still need Cummlative Pack 4. This fix must be order per Microsoft's web site. Is this true?

Thank you for taking the time to read my post.

Russ

graz
Chief SQLTeam Crack Dealer

4149 Posts

Posted - 2008-02-29 : 15:07:49

It's true that you have to order it from Microsoft. You may not need it. Unless you are experiencing one of the specific problems listed in the fixes I wouldn't worry about. Personally I never install CUs unless I'm having a specific problem they fix.

=================================================
Creating tomorrow's legacy systems today. One crisis at a time.

russray
Starting Member

27 Posts

Posted - 2008-03-02 : 08:03:51

Okay, the BSOD is BACK!

It appears every time I pump data into the database, and then start "openning" up the the tables within SSMS, I get the BSOD. Sometimes I can open up several tables before I get the BSOD or I can open one with many relationships. One thing I do know, I don't receive the BSOD with any other program. It is just SQL Server 2005's SSMS! The screen dump deals with win32.sys file.

My earlier post gives you the latest version for SSMS.

I am running SQL Server 2005 on a Dell Precision laptop computer model M90. It has Intell T2500 @ 2.00GHz CPU and 2GB RAM. Windows XP, SP2 is OS.

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2008-03-02 : 08:09:16

maybe you should contact MS support if this is really annoying.
define "opening tables". do you mean for editing?

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com

russray
Starting Member

27 Posts

Posted - 2008-03-02 : 08:22:38

In SSMS you can view the table and the date inside the table through the "Open Table" command.

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2008-03-02 : 08:42:20

yeah, i know... i just wanted to make sure we mean the same thing.
do you get any errors windows before the BSOD?

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com

russray
Starting Member

27 Posts

Posted - 2008-03-02 : 08:48:05

No error what so ever! Something is not playing nice iwht SQL Server 2005. I suspect SQL Server 2005 and another applicaiton are touching the same memory location. I'll let the technical support guys figure it out.

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2008-03-02 : 08:52:44

this open table is a completly new control in ssms so i guess you're probably right about the memory stuff.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com

jezemine
Master Smack Fu Yak Hacker

2886 Posts

Posted - 2008-03-02 : 11:23:55

BSOD is usually caused by a problem in code that's running kernel mode. that means it's a driver problem. SSMS runs in user mode, so it can't cause a BSOD directly, only indirectly thru the drivers the OS invokes as a result of SSMS running.

according to this post, it may be caused by your mouse driver:
http://botsikas.blogspot.com/2007/06/ssms-and-win32ksys-blue-screen.html

elsasoft.org

russray
Starting Member

27 Posts

Posted - 2008-03-02 : 11:48:31

I am following your logic and it sounds cogent. I will need to find which driver my system is using that is causing the conflict with SSMS.

Thank you for your time for reading my post and your insight!

Russ

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2008-03-02 : 12:03:36

> SSMS runs in user mode, so it can't cause a BSOD directly

DOH! where's the icon of shooting yourself in the head??

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-03-02 : 15:22:34

Did you see any error in windows event logs and sql server log?

Next Page

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources