Urgent problem | Microsoft Connect

Posted by Microsoft on 2/20/2007 at 12:26 AM

Hi MironBramson,

Thanks for reporting this bug. I would like to know more input on this bug. Are you connecting to a db on your machine itself or to a remote machine? When you download ssms express, which DB are you making the connection with? Could you please update us with this info. Feel free to contact us and probably we can have a call as well.

Posted by Mironabramson on 2/21/2007 at 1:49 AM

Yes, I'm connecting DB that on my local machine.
I downloaded the ssms express in the last month (version: 9.00.2047.00).
The DB I'm connecting to is my DB. I created it.
Need Some more info ?
I know I'm not the only one who have this problem. a fast checking over the net found
some others that having the problem, but none of them found the solution.
Waiting for fast solution...
Regards,
Miron Abramson

Posted by Microsoft on 2/21/2007 at 9:15 PM

Hi MironBramson,

We shall target this issue in our next release. Also we want to reproduce this problem at our end so that we can find a solution. Please let us know what is the table size and what are the data types in it when it happens.

Thanks,
Alok

Posted by Mironabramson on 2/22/2007 at 12:40 AM

Hi,
the size of the table is not meter. it's happen on empty or full table.
also, it can happen almost with every table. the table witch is most commonly happen include the data type:
int, datetime, bigint, varchar(128), varchar(MAX), varchar(255), varchar(MAX).
I remind you again that it's not happen every time I open that table.
I happen maybe one to ten times I open it.
I also attached that table.

Posted by Mironabramson on 2/22/2007 at 12:41 AM

Posted by vpa on 3/5/2007 at 11:22 PM

I have same problems and I found on google that other people too. Common sign is using on notebooks with multi core processor. I have for example Acer notebook and problems I have from end of January. Before that I have no problems. I've been tried SP1 and SP2 of SQL 2005, Developer and Express versions and BSOD's are the same. It not depends on table's properties. It can be small table with two int columns like I tried yesterday. When I want add new row BSOD is thrown, for example. I have no problems with SQL 2000 Enterprise Manager, so I using it now again.

Posted by Mironabramson on 3/21/2007 at 6:28 AM

Hi,
There is something new with the subject ?
My windows still crashing all time. Waiting (as some more windows users) for
an urgent solution.
Regards,
Miron Abramson

Posted by Mironabramson on 3/21/2007 at 6:31 AM

Hi,
There is something new with the subject ?
My windows still crashing all time. Waiting (as some more windows users) for
an urgent solution.
Regards,
Miron Abramson

Posted by AaronBertrand on 3/21/2007 at 12:55 PM

Is it possibly a video driver related bug, or something Dell specific? I don't use Open Table but I have a Dell machine with core 2 duo processors and a high-end video card, and I get blue screens all the time on that machine (but none seem related to Management Studio at all). I have a few other Dell machines (two desktops and a laptop), both desktops have dual core, and none of these three machines has ever had a blue screen. So it can't be Management Studio in isolation, else I would be seeing this on all Dells (or all Dells with multi core processors, or all Dells with nvidia video cards, etc). The symptom definitely sounds video driver related to me.

Posted by vpa on 3/22/2007 at 7:11 AM

I have Acer, not Dell.
Problems are from January, I've been installed new MSDN, SP1 for SQL and security patches from MS and from next day BSOD are fired.

Posted by Mironabramson on 3/23/2007 at 1:48 PM

Hi all,
I'm tired from waiting for an answer.
I need to work, and I just can't !!!
Somebody can help me by give me a link to another editor\management software to manage sql server?
Thank you all

Posted by vpa on 5/8/2007 at 11:13 PM

Are you using Microsoft IntelliMouse Driver? I found in https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262721 solution that removing of new 6.x version of Intellimouse Driver resolves our common problem.

Posted by Mironabramson on 5/13/2007 at 10:43 AM

I'm not using Microsoft IntelliMouse Driver.
The only common pattern I found for all that having the problem is :
Processor Core Due 2 with 2G of RAM.
Until MS will provide a solution, I left the Management Studio for Aqua Data Studio 4.7

Posted by Mironabramson on 5/13/2007 at 10:48 AM

Posted by AndyAlmq on 6/5/2007 at 9:34 PM

Hi,

I also have the same problem on a Sony VAIO VGN-BX670P. All of the instances of this that I have found have been with Intel dual core systems - possibly all Core 2 duo. A temporary workaround that appears to work for me is to go into the advanced display settings and turn off hardware acceleration. My video card is an ATI Mobility Radeon X1600, and it has the most recent drivers available.

As far as reproducing this problem, it happens nearly every time I leave hardware accelleration at full (I havn't tried settings in between). It generally happens when selecting a field to edit, or editing a value, but the timing seem rather random. Some times it will happen the first time I try to edit something, other times I'll be working for 15-20 minutes before it happens.

Posted by tOMPSON on 6/19/2007 at 2:40 PM

Hi,

I got the same problem here: Dell Precision M65 Notebook with 2GB RAM, Core Duo 2, Windows XP

After a random amount of time working with SQL Server Management Studio Express I get the BSOD with

*** STOP: 0x0000008E ( .... )
*** win32k.sys - Address ....

It does not depend on which table I open ... I already upgraded my video driver to the newest version - problem still exists.

Will there be a solution/patch soon?

Posted by DoButton on 6/28/2007 at 3:18 AM

Intel Releases Core 2 BIOS Chip Fix:
http://www.theregister.co.uk/2007/06/27/intel_core2_duo_bios_fix/

Causes system instability - blue screens etc.
Prehaps its a Hardware issue after all, somebody to test and report back ?

Posted by Microsoft on 12/3/2007 at 1:33 AM

Hello Miron Abramson,

Have you looked at the Eventvwr logs for any anomalies post the Blue Screen?

The STOP error message you have posted :

*** STOP: 0x0000008E (0xc0000005,0xbf8E270C,0A8E11868,0x00000000)

suggests that the problem at the hardware level.

SQL Server or SSMS bein user level processes can never cause a Blue Screen.

Thanks,
Karthik

SQL Server Team

Posted by Microsoft on 12/20/2007 at 8:10 AM

Hi Mironabramson,

With the next release of SQL Express, the open table operation will be restrictive with a fixed no. of rows. This issue has been around based on so many hardware issues as well. We are closing this at this point. If you find the problem still persisting, feel free to reopen this issue.

Regards
Vinod

Posted by Microsoft on 1/22/2009 at 3:57 AM

Dear customer,
This is no more an issue in the SQL Server 2008 SSMS express version. Please let us know if you see this issue again.

Thanks
Satish

Posted by vos on 2/21/2007 at 5:56 AM

Turn off multiple CPU core's in BIOS fix it for me (Dell Optiplex GX620)

Posted by cflogan on 5/29/2007 at 10:05 AM

See workarounds listed in Problem 262721. All 4 (or 5) speak of disabling or uninstalling IntelliPoint 6.1 Software. When I did this as well. I was fine. No more BSODs related to opening tables in SSMS.

Posted by AndyAlmq on 6/5/2007 at 9:36 PM

Disabling hardware acceleration in the advanced display properties works for me.

Posted by tOMPSON on 6/23/2007 at 3:44 AM

for me the problem was solved with uninstalling the IntelliPoint 6.1 driver

Posted by JLopez_MVP on 7/25/2007 at 1:08 PM

for me too.
Problem was solved with uninstalling the IntelliPoint 6.1 driver.

Posted by fanningmsf on 2/10/2008 at 6:24 AM

The hardware acceleration tip may be one clue. Once I set it down to the 3rd notch (with left-most being the first notch) where all DirectX and Direct3D accelerations are disabled, the problem went away. I have no doubt that an alternative method would be to leave it at full acceleration, and then set the Core2 Duo processor to single processor in the BIOS, but I have not tried that as of yet.

It seems to be inconsistent in our office, where we have a large number of HP/Compaq nw8440 laptops using an onboard ATI Mobility FireGL V5200 (using the latest ATI driver and BIOS version from HP). I switched my hard drive to another brand new machine that had not been handed out to the user yet, and it still exhibited this problem. The developer on my left however had not seen this issue yet. I've only had my laptop for 3 months now. Prior to this I had a Dell Latitude (which did not have the Core 2 Duo and used an Intel based graphics adapter) and never saw this problem.

My guess is it's an issue relating to the Core 2 Duo and Direct X/3D hardware acceleration. It would be interesting to know if any of the AMD-based laptops are exhibiting this issue. Or if anyone using the NVidia display adapters in conjunction with the Core 2 Duo encounter this problem or not.

Posted by fanningmsf on 2/10/2008 at 7:50 AM

Additional info (found this from another site: http://botsikas.blogspot.com/2007/06/ssms-and-win32ksys-blue-screen.html). I went ahead and uninstalled MS Intellipoint 6.2 from the laptop and the problem no longer occurs. I'm guessing here that it is a problem in how it uses DirectX in conjunction with the Core 2 Duo processor - some incompatibility.

Posted by RJ Anderson on 3/30/2008 at 8:47 PM

Seems to have been fixed by removing Microsoft Intellipoint 6.01.

Posted by CAFM on 7/6/2008 at 8:34 AM

same as tOMPSON: for me the problem was solved with uninstalling the IntelliPoint 6.1 driver

Posted by Mironabramson on 7/26/2008 at 9:42 PM

After long time of quietness, the problem start happening again.
Without any logical reason.
I open again the 'case'.

Urgent problem by Mironabramson