July 2, 2007 at 11:16 pm
I have SQL server 2005 development edition installed on my laptop and when viewing the contents of the tables it will reboot the machine with no warning, this only happens in sql server and only when viewing the tables (ie not running stored proc's or other management of database). I had the same issue happening on my older laptop but it is happening more frequently on this one. Which leads me to rule out the most obvious cause, hardware, this new machine is a dual processor, 1.5gb etc (ie good enough not to be doing this).
The only clues to the cause are the very cryptic messages in the event log:
An error message:
Error code 1000008e, parameter1 c0000005, parameter2 bf8e5f91, parameter3 9c064868, parameter4 00000000.
And an information message:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf8e5f91, 0x9c064868, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini070307-05.dmp.
I have tried scripting the database and importing the data into a new db but the problem still occurs.
I have uninstalled and reinstalled SQL server and applied SP2.
The machine in question is fully patched and all most recent drivers (win XP pro)
Any help or ideas as to the cause would be greatly appreciated.
July 2, 2007 at 11:40 pm
I hope the machine is hitting a memory dump. check for the sql server error log files and the eventvwr to get more clue on what is exactly happening at that time anc can you post those.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 3, 2007 at 12:20 am
I would add: exclude your online database files from your antivirus (Norton is doing this sometimes); define min and max (sql) server memory that way your os would get enough memory any time.
Hope this helps.
July 3, 2007 at 12:27 am
There is nothing in the SQL server logs around the time of the reboots, there are 4 few during the init of the server relating to (I assume) the performance counters not being able to start..
SQL Error1:
Error: 8313, Severity: 16, State: 1.
SQL Error 2:
Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
SQL Error 3:
Error: 3409, Severity: 16, State: 1.
SQL Error 4:
Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
Information relating to these errors that I have found through google etc suggest (to me anyways) that these errors are not related to my problem.
Other than those errors the SQL server logs are pretty clean.
As for the event viewer, There are A LOT (about 600 in the space of 5 minutes) of events in the Application log just before the reboot, most of them from .Net Runtime Optimization Service for example
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: C:\Program Files\Microsoft SQL Server\90\DTS\Binn\dtsinstall.exe
OR
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Succesfully compiled: Microsoft.SqlServer.PipelineHost, Version=9.0.242.0, Culture=neutral, PublicKeyToken=xx
OR
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Began compiling: Microsoft.SqlServer.DtsMsg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=xx
There are some errors.
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.SqlServer.SQLTaskConnectionsWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=xx. Error code = 0x80070002
The System log is fairly clean apart from the errors I posted origionally. I hope this info helps a little,
July 3, 2007 at 6:05 am
C:\WINDOWS\Minidump\Mini070307-05.dmp. did you checked this dump file?
Minaz
"More Green More Oxygen !! Plant a tree today"
July 3, 2007 at 5:12 pm
Here are the results of running the dump file through dumpchk.exe, none of this means much to me, any help would be appreciated.
C:\PROGRA~1\Support Tools>dumpchk c:\windows\minidump\mini070307-05.dmp
Loading dump file c:\windows\minidump\mini070307-05.dmp
----- 32 bit Kernel Mini Dump Analysis
DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0a240680
PfnDataBase 810a6000
PsLoadedModuleList 8055c700
PsActiveProcessHead 80562818
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 bf8e5f91
BugCheckParameter3 9c064868
BugCheckParameter4 00000000
PaeEnabled 00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields 00000dff
TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00000788
DriverListOffset 00003398
DriverCount 00000092
StringPoolOffset 00005ef0
StringPoolSize 00001438
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 9c064878
DebuggerDataOffset 00003108
DebuggerDataSize 00000290
DataBlocksOffset 00007328
DataBlocksCount 00000004
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Jul 03 13:15:57 2007
System Uptime: 0 days 1:15:46
start end module name
804d7000 806e2000 nt Checksum: 001FB950 Timestamp: Wed Feb 28 20:
15:54 2007 (45E5484A)
Unloaded modules:
9bebf000 9beea000 kmixer.sys Timestamp: unavailable (00000000)
9c02a000 9c055000 kmixer.sys Timestamp: unavailable (00000000)
9c02a000 9c055000 kmixer.sys Timestamp: unavailable (00000000)
9ca7a000 9caa5000 kmixer.sys Timestamp: unavailable (00000000)
f7b73000 f7b74000 drmkaud.sys Timestamp: unavailable (00000000)
9e1ca000 9e1d7000 DMusic.sys Timestamp: unavailable (00000000)
9caa5000 9cac8000 aec.sys Timestamp: unavailable (00000000)
f67f7000 f6805000 swmidi.sys Timestamp: unavailable (00000000)
f7a09000 f7a0b000 splitter.sys Timestamp: unavailable (00000000)
a597d000 a5982000 Cdaudio.SYS Timestamp: unavailable (00000000)
a5975000 a5978000 Sfloppy.SYS Timestamp: unavailable (00000000)
Finished dump check
July 6, 2007 at 5:52 am
From that dump looks to me like you have might have the /PAE enabled in boot.ini? If so try removing that and see if that fixes it.
July 10, 2007 at 3:01 pm
I just encountered this problem today, and can reproduce it every time when connected to a networked database.
1) Open SQL Server Manager and connect to a networked database (in this case, it happens to be a server with 50+ databases on it).
2) Scroll through the list of tables, find one with lots of columns and 200ish rows.
3) Right click on table and choose Open Table.
4) Drag the elevator box all the way to the bottom.
5) BSOD. Stop 0x0000008E (0xC0000005, 0xBF8E5F91, 0xB3891868, 0x00000000) Win32k.sys at location 0xBF8E5F91, base 0xBF800000, datestamp 45F013F6.
Haven't seen it yet with my own local database. On my machine, I'm running SQL Server 9.0.3045, and on the network machine it is 9.0.3042. XP Service pack 2.
July 11, 2007 at 11:30 am
Getting the exact same thing. And I can make it happen on a local database as well.
July 11, 2007 at 6:51 pm
Glad to see Im not the only one with this problem (well not glad for the people with the problem), I have not fixed it per se but I have managed to avoid the issue for now by using queries rather than viewing the tables directly, but this is far from ideal. I checked the boot.ini and found nothing refering to /PAE, just your standard boot.ini as it is a new laptop with a fresh install of xp pro.
July 12, 2007 at 6:14 am
A BLUE SCREEN (popularly called bugcheck ) is a fault occouring in Windows Kernel mode.
Any user mode process such as SQL (or a notepad or any) CAN NOT cause bugcheck.
to resolve this:
consider updating all system drivers/firmware.
if issue persists, call up microsoft Windows support team and ask for diagnostics.
July 12, 2007 at 7:17 am
Hi Josh,
Yes, my work-around technique is the same as yours, simply do a query instead of doing an "Open Table" from the context menu.
Less than ideal, but it works. But occasionally, I forget and do an Open Table, and thus shortly after I see the BSOD.
July 12, 2007 at 7:00 pm
I am getting a slightly different error message, but essentially the same thing.
Error code 1000008e, parameter1 c0000005, parameter2 bf8e5f91, parameter3 b1021868, parameter4 00000000.
My error occurs when opening the table from server explorer in visual web developer express. I am using sql server express edition.
I hope someone figures this out.
July 13, 2007 at 7:40 am
I'm getting the exact same problem.
On sql server all day and it crashes out about 4 times a day, got all the win updates and no difference.
Can any please advise, its doing my head in.
Cheers
Dan
July 13, 2007 at 10:32 am
I have the same error
Error code 1000008e, parameter1 c0000005, parameter2 bf8e5f91, parameter3 b952f868, parameter4 00000000.
this happens when i open tables in SQL Server, if anyone have an idea whats going on that will be great.
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply