BugCheck Dump
please review if this stack dump is a concern or if it's a one time non-critical event.
If it's a concern, please provide any recommendations.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.50.2550.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU E5630 @ 2.53GHz.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 1.3.9
16 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.
Memory
MemoryLoad = 96%
Total Physical = 16374 MB
Available Physical = 560 MB
Total Page File = 32746 MB
Available Page File = 15132 MB
Total Virtual = 8388607 MB
Available Virtual = 8371381 MB
**Dump thread - spid = 0, EC = 0x0000000000000000
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0005.tx
t
* BEGIN STACK DUMP:
* 07/11/14 01:38:00 spid 2060
* Non-yielding Resource Monitor
* Short Stack Dump
Thank you!
please review if this stack dump is a concern or if it's a one time non-critical event.
If it's a concern, please provide any recommendations.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.50.2550.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU E5630 @ 2.53GHz.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 1.3.9
16 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.
Memory
MemoryLoad = 96%
Total Physical = 16374 MB
Available Physical = 560 MB
Total Page File = 32746 MB
Available Page File = 15132 MB
Total Virtual = 8388607 MB
Available Virtual = 8371381 MB
**Dump thread - spid = 0, EC = 0x0000000000000000
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0005.tx
t
* BEGIN STACK DUMP:
* 07/11/14 01:38:00 spid 2060
* Non-yielding Resource Monitor
* Short Stack Dump
Thank you!
Similar Messages
-
Hi,
I have a bugcheck dump file. I don't know how to use it for troubleshooting. Can someone please guide me?
Its SQL server 2012 3128 build. I was troubleshooting a performance issue when SQL server rebooted itself. Later I found this dump file. I do have more error log files etc. Please advise where should I begin from.
Thanks,
Current time is 14:48:07 01/07/14.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 11.0.3128.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AMD Opteron(TM) Processor 6276 .
Bios Version is INTEL - 6040000
VMW71.00V.0.B64.1206220901
2 X64 level 8664, 14 Mhz processor (s).
Windows NT 6.2 Build 9200 CSD .
Memory
MemoryLoad = 84%
Total Physical = 8191 MB
Available Physical = 1299 MB
Total Page File = 12479 MB
Available Page File = 3989 MB
Total Virtual = 8388607 MB
Available Virtual = 8372937 MB
***Unable to get thread context for spid 0
* BEGIN STACK DUMP:
* 01/07/14 14:48:08 spid 3916
* Non-yielding SchedulerHello Mudit,
Follow the steps in
http://mssqlwiki.com/2012/08/21/non-yielding-iocp-listener-non-yielding-scheduler-and-non-yielding-resource-monitor-known-issues-and-fixes/ and check if the stack matches any of the existing issues.If you don't find the matching stack post the stack here,
we will let you know the cause. Remember most of the Non-yield dumps are because of external conditions and SQL Server becomes victim.
If you want to understand what is Non-yielding condition please
http://mssqlwiki.com/2012/08/17/how-to-analyze-non-yielding-scheduler-dumps/
Thank you,
Karthick P.K |My blogs|My Scribbles|Twitter|My Facebook
Group|
www.Mssqlwiki.com
Please click the Mark as answer button and vote as helpful if this reply solves your problem -
Hi All,
Please help me in resolving this issue.
====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5057.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is INTEL - 6040000
PhoenixBIOS 4.0 Release 6.0
Current time is 06:04:58 09/21/14.
2 Intel x86 level 6, 2600 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 95%
Total Physical = 4095 MB
Available Physical = 165 MB
Total Page File = 9029 MB
Available Page File = 4848 MB
Total Virtual = 2047 MB
Available Virtual = 256 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0010.txt
* BEGIN STACK DUMP:
* 09/21/14 06:04:58 spid 0
* Non-yielding Resource Monitor
* Short Stack Dump
select @@ version:
Microsoft SQL Server 2005 - 9.00.5057.00 (Intel X86) Mar 25 2011 13:50:04 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Thanks in advance.Hello,
These types of errors are related to memory pressure or working set trimming on the SQL Server instance. Please try to set the max server
memory option and leave 2 or 4 GB of RAM to the operating system.
sp_configure
'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure
'max server memory', 4096;
GO
RECONFIGURE;
GO
The above code limits SQL Server Memory Manager to 4 GB.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Current time is 11:15:26 08/25/14.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 11.0.3000.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz.
Bios Version is INTEL - 6040000
PhoenixBIOS 4.0 Release 6.0
12 X64 level 8664, 14 Mhz processor (s).
Windows NT 6.2 Build 9200 CSD .
Memory
MemoryLoad = 54%
Total Physical = 129023 MB
Available Physical = 58720 MB
Total Page File = 147455 MB
Available Page File = 76622 MB
Total Virtual = 134217727 MB
Available Virtual = 134032858 MB
DBCC RESULTS
<Dbcc ID="265"
<Dbcc ID="479" Error="2593" Severity="10" State="1">There are 445 rows in 111 pages for object "Temp_CalcFields_P
laysDFD5C6F819E84D1EBA43D30C37AABB47".</Dbcc>
<Dbcc ID="480" Error="2593" Severity="10" State="1">There are 154 rows in 4 pages for object "ReplicationInfo_tra
cking".</Dbcc>
<Dbcc ID="481" Error="2593" Severity="10" State="1">There are 7022 rows in 177 pages for object "UserSettings_tra
</DbccResults>
**Dump thread - spid = 0, EC = 0x00000010A909E730
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0003.txt
* BEGIN STACK DUMP:
* 08/25/14 11:15:26 spid 158
* DBCC database corruption
* Input Buffer 90 bytes -
* use [TC_Baylor_FB] dbcc checkdb
* Short Stack Dump
CSession @0x0000001177F2C450
m_sessionId = 158 m_cRef = 14 m_rgcRefType[0] = 1
m_rgcRefType[1] = 1 m_rgcRefType[2] = 11 m_rgcRefType[3] = 1
m_rgcRefType[4] = 0 m_rgcRefType[5] = 0 m_pmo = 0x0000001177F2C040
m_pstackBhfPool = 0x0000000000000000 m_dwLoginFlags = 0x83e0 m_fBackground = 0
m_eConnResetOption = 0 m_fUserProc = 1 m_fConnReset = 0
m_fIsConnReset = 0 m_fInLogin = 0 m_fAuditLoginSent = 1
m_fAuditLoginFailedSent = 0 m_fReplRelease = 0 m_fKill = 0
m_ulLoginStamp = 6700445 m_eclClient = 7 m_protType = 5
m_hHttpToken = FFFFFFFFFFFFFFFF
m_pV7LoginRec
0000000000000000: 5c010000 04000074 00100000 00000006 400d0000 \......t........@...
0000000000000014: 00000000 e0830000 00000000 00000000 5e000e00 ....à?..........^...
0000000000000028: 00000000 00000000 7a002e00 d6000e00 f2000400 ........z...Ö...ò...
000000000000003C: f6001c00 2e010000 2e010000 e3418e99 00e02e01 ö...........ãA?..à..
0000000000000050: 28005601 00005601 00000000 0000 (.V...V.......
CPhysicalConnection @0x0000001177F2C230
m_pPhyConn->m_pmo = 0x0000001177F2C040
m_pPhyConn->m_pNetConn = 0x0000001177F2CBF0
m_pPhyConn->m_pConnList = 0x0000001177F2C420
m_pPhyConn->m_pSess = 0x0000001177F2C4A8 m_pPhyConn->m_fTracked = -1
m_pPhyConn->m_cbPacketsize = 4096 m_pPhyConn->m_fMars = 0 m_pPhyConn->m_fKill = 0
CBatch @0x0000001177F2D140
m_pSess = 0x0000001177F2C450 m_pConn = 0x0000001177F2D020 m_cRef = 3
m_rgcRefType[0] = 1 m_rgcRefType[1] = 1 m_rgcRefType[2] = 1
m_rgcRefType[3] = 0 m_rgcRefType[4] = 0 m_pTask = 0x00000018199A2928
EXCEPT (null) @0x0000000064754EF0
exc_number = 0 exc_severity = 0 exc_func = 0x00007FFF4730EE50
Task @0x00000018199A2928
CPU Ticks used (ms) = 88442 Task State = 2
WAITINFO_INTERNAL: WaitResource = 0x0000000000000000 WAITINFO_INTERNAL: WaitType = 0x0
WAITINFO_INTERNAL: WaitSpinlock = 0x0000000000000000 SchedulerId = 0x3
ThreadId = 0x205c m_state = 0 m_eAbortSev = 0
EC @0x00000010A909E730
spid = 0 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x0 ec_atomic = 0x0 ecType = 0
__pSETLS = 0x0000001177F2D090 __pSEParams = 0x0000001177F2D520
SEInternalTLS @0x0000001177F2D090
m_flags = 0
m_TLSstatus = 3
m_owningTask = 0x00000018199A2928
m_activeHeapDatasetList = 0x0000001177F2D090
m_activeIndexDatasetList = 0x0000001177F2D0A0
m_pDbccContext = 0x00000011DA40CED0
m_pAllocFileLimit = 0x0000000000000000
m_dekInstanceIndex = 0x-1
m_pImbiContext = 0x0000000000000000
SEParams @0x0000001177F2D520
m_lockTimeout = -1
m_isoLevel = 4096
m_logDontReplicate = 0
m_neverReplicate = 0
m_XactWorkspace = 0x00000012508E3050
m_execStats = 0x00000015636D5CC8Based on the dump contents, your SQL Server MDF database file is corrupt, the possible solutions are based on the situation:
1. If the corruption is not severe, then you can use the SQL Server build-in command DBCC CheckDB to correct the errors. See
http://technet.microsoft.com/en-us/library/ms176064.aspx
2. If the corruption is severe, then you may try some third party tools. The one I have tried successfully in the past is DataNumen SQL Recovery at
http://www.datanumen.com/sql-recovery/ . You can use it to scan and recover the data from your corrupted MDF and NDF database files.
Good luck!
And what about restoring from backup ? That tool is of no use seriously have tried it.
Restoring from valid backup is best option here dont go for tool its useless.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5000.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 2.2.6
Current time is 06:28:49 08/28/14.
8 Intel x86 level 6, 2660 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 82%
Total Physical = 32762 MB
Available Physical = 5805 MB
Total Page File = 82821 MB
Available Page File = 56349 MB
Total Virtual = 2047 MB
Available Virtual = 282 MB
**Dump thread - spid = 18, PSS = 0x7657A7D8, EC = 0x7657A7E0
***Stack Dump being sent to xxxxxx
* BEGIN STACK DUMP:
* 08/28/14 06:28:49 spid 18
* Latch timeout
* Short Stack DumpHello,
A fix was issued on CU 6 for SQL Server 2005 (Oct 2009) and your SQL Server instance has SP4 applied which was released November 2009.
Please apply CU1 for SP4 to make sure the hot fix has been applied to the SQL Server instance.
http://support.microsoft.com/kb/2464079
The following article may help you troubleshoot this issue:
http://mssqlwiki.com/tag/latch-timeout-stack-dump/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Recently We've migrated SQL 2005 x86 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3. We migrate users (with standard approach by Microsoft) and application databases
to new server. Everything is looking ok, applications working. But we've got some SQL exceptions like below.
Is there any known bug related to that? Could someone help us.
Memory
MemoryLoad = 15%
Total Physical = 32733 MB
Available Physical = 27752 MB
Total Page File = 64782 MB
Available Page File = 60344 MB
Total Virtual = 8388607 MB
Available Virtual = 8355366 MB
**Dump thread - spid = 84, PSS = 0x00000000D1A43ED0, EC = 0x00000000D1A43EE0
***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0005.txt
* BEGIN STACK DUMP:
* 04/25/14 12:54:30 spid 84
* ex_handle_except encountered exception C0000264 - Server terminating
* Input Buffer 255 bytes -
There is also some output from debugger:
0:000> .ecxr
rax=0000000077207080 rbx=0000000000000000 rcx=0000000016a37d50
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000440
rip=00000000772070bd rsp=0000000016a38240 rbp=000000000000003f
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000287 r12=00000000032fdab0 r13=0000000000000000
r14=00000000000019e4 r15=0000000049b8d00c
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
kernel32!RaiseException+0x3d:
00000000`772070bd 4881c4c8000000 add rsp,0C8h
0:000> kC 1000
Call Site
kernel32!RaiseException
sqlservr!DmpGetClientExport
sqlservr!_____SQL______Process______Available
sqlservr!_____SQL______Process______Available
sqlservr!_____SQL______Process______Available
sqlservr!SQLExit
kernel32!UnhandledExceptionFilter
ntdll!RtlpNotOwnerCriticalSection
ntdll!_C_specific_handler
ntdll!RtlIntegerToChar
ntdll!_C_specific_handler
ntdll!RtlRaiseStatus
ntdll!RtlpNotOwnerCriticalSection
ntdll!LdrGetProcedureAddress
sqlshield
sqlservr
0x0
0x0
0x0
0x0
0x0
Hi,
In last days we "close" our SQL to some scanning security applications which could also do some things on our SQL. But it's only a guess. About sqlshield we do the unregister and register DLL's again. Now at last two exception is not the same situation.
Can you see something from there with "Non-yielding Scheduler". Is it also possible that it something wrong with the hardware. We're using new Cisco rack 1U server for that SQL server. I've also read someting about upgrading the BIOS, related to errors
"Non-yielding Scheduler". At the end i can also tell, that the server is alive for a couple of days, if there is no a lot activity on the server, i mean on national holidays, through weekend, etc.
Any new idea?
Thanks,
Matjaž
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5266.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is Cisco0 - 0
BIOS Date: 08/20/13 06:01:31 Ver: 04.06.05
Current time is 11:17:16 04/30/14.
12 Unknown CPU 9., 14 Mhz processor (s).
Windows NT 6.0 Build 6002 CSD Service Pack 2.
Memory
MemoryLoad = 17%
Total Physical = 32733 MB
Available Physical = 26900 MB
Total Page File = 64782 MB
Available Page File = 59543 MB
Total Virtual = 8388607 MB
Available Virtual = 8355342 MB
***Unable to get thread context - no pss
* BEGIN STACK DUMP:
* 04/30/14 11:17:16 spid 0
* Non-yielding Scheduler
Stack Signature for the dump is 0x00000000000003AD -
A severe error occurred on the current command. The results, if any, should be discarded.
I have a strange situation on a database, which are on SQL Server 2008 R2 Express SP2. The database size is something around 90 MB.
When a user try to insert a record inside one table, he receive an error message, and the program is disconnected from the database. I tried to investigate this issue, and I discovered that when user try to insert one row the trigger for
insert invoke also the trigger for update and sql server crushes with "A severe error occurred on the current command. The results, if any, should be discarded."
I have checked from SQL Server Management Studio to run a direct Update on the specific table. The same error occurred.
I have run DBCC CheckTable and no errors have been found. I also have run DBCC CHECKDB and no errors.
Because I also have 3 other different databases, with the same functionality, on the same server which are going well with more than 100 000 records in that specific table, and the triggers are going well for more than 5 years, I have assumed that some
problems occurs inside the database. That is why I have copied all the records from the "damage" database to a new one. This means that inside the new databases the indexes are regenerated and a new space will be allocated.
The same strange things are happening. The same table can not be updated with a very basic Update statement.
I am looking for a patch or KB to solve this issues.
Any ideas are will be appreciated.
Thank youthere is a file as response to one of my tests to investigate which command is responsible for this error.
Current time is 21:18:39 08/18/13.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.50.4000.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz.
Bios Version is INTEL - 1072009
BIOS Date: 09/23/09 11:58:43 Ver: 08.00.10
8 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.1 Build 7601 CSD Service Pack 1.
Memory
MemoryLoad = 16%
Total Physical = 8125 MB
Available Physical = 6755 MB
Total Page File = 16248 MB
Available Page File = 14719 MB
Total Virtual = 8388607 MB
Available Virtual = 8380163 MB
***Stack Dump being sent to d:\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0084.txt
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
* BEGIN STACK DUMP:
* 08/18/13 21:18:39 spid 52
* Exception Address = 0000000000886B00 Module(sqlservr+00000000001F6B00)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 0000000000000000
* Input Buffer 214 bytes -
* begin transaction insert into DocContabile select * f
* rom gunoiDocContabile rollback
* MODULE BASE END SIZE
* sqlservr 0000000000690000 00000000042A1FFF 03c12000
* ntdll 0000000077730000 00000000778D8FFF 001a9000
* kernel32 0000000077510000 000000007762EFFF 0011f000
* KERNELBASE 000007FEFD6E0000 000007FEFD74AFFF 0006b000
* ADVAPI32 000007FEFE090000 000007FEFE16AFFF 000db000
* msvcrt 000007FEFE300000 000007FEFE39EFFF 0009f000
* sechost 000007FEFF590000 000007FEFF5AEFFF 0001f000
* RPCRT4 000007FEFF5B0000 000007FEFF6DCFFF 0012d000
* MSVCR80 0000000071710000 00000000717D8FFF 000c9000
* MSVCP80 0000000071600000 0000000071708FFF 00109000
* sqlos 00000000715F0000 00000000715F6FFF 00007000
* Secur32 000007FEFD1E0000 000007FEFD1EAFFF 0000b000
* SSPICLI 000007FEFD3B0000 000007FEFD3D4FFF 00025000
* pdh 000007FEF90C0000 000007FEF910DFFF 0004e000
* SHLWAPI 000007FEFDE50000 000007FEFDEC0FFF 00071000
* GDI32 000007FEFE3A0000 000007FEFE406FFF 00067000
* USER32 0000000077630000 0000000077729FFF 000fa000
* LPK 000007FEFDE40000 000007FEFDE4DFFF 0000e000
* USP10 000007FEFF970000 000007FEFFA38FFF 000c9000
* USERENV 000007FEFC850000 000007FEFC86DFFF 0001e000
* profapi 000007FEFD510000 000007FEFD51EFFF 0000f000
* WINMM 000007FEFB320000 000007FEFB35AFFF 0003b000
* IPHLPAPI 000007FEFAD70000 000007FEFAD96FFF 00027000
* NSI 000007FEFDFB0000 000007FEFDFB7FFF 00008000
* WINNSI 000007FEFAD60000 000007FEFAD6AFFF 0000b000
* opends60 0000000071590000 0000000071597FFF 00008000
* NETAPI32 000007FEFAEB0000 000007FEFAEC5FFF 00016000
* netutils 000007FEFAEA0000 000007FEFAEABFFF 0000c000
* srvcli 000007FEFD060000 000007FEFD082FFF 00023000
* wkscli 000007FEFAE80000 000007FEFAE94FFF 00015000
* LOGONCLI 000007FEFCB90000 000007FEFCBBFFFF 00030000
* SAMCLI 000007FEFAE60000 000007FEFAE73FFF 00014000
* BatchParser 0000000071560000 000000007158CFFF 0002d000
* IMM32 000007FEFE060000 000007FEFE08DFFF 0002e000
* MSCTF 000007FEFE1F0000 000007FEFE2F8FFF 00109000
* psapi 00000000778F0000 00000000778F6FFF 00007000
* instapi10 0000000071320000 000000007132CFFF 0000d000
* cscapi 000007FEF7FA0000 000007FEF7FAEFFF 0000f000
* sqlevn70 0000000071100000 0000000071303FFF 00204000
* CRYPTSP 000007FEFCE50000 000007FEFCE66FFF 00017000
* rsaenh 000007FEFCA70000 000007FEFCAB6FFF 00047000
* CRYPTBASE 000007FEFD440000 000007FEFD44EFFF 0000f000
* BROWCLI 000007FEF8B80000 000007FEF8B91FFF 00012000
* AUTHZ 000007FEFCF70000 000007FEFCF9EFFF 0002f000
* MSCOREE 000007FEF8980000 000007FEF89EEFFF 0006f000
* ole32 000007FEFDC30000 000007FEFDE32FFF 00203000
* credssp 000007FEFC960000 000007FEFC969FFF 0000a000
* msv1_0 000007FEFCD90000 000007FEFCDE0FFF 00051000
* cryptdll 000007FEFD090000 000007FEFD0A3FFF 00014000
* kerberos 000007FEFCCD0000 000007FEFCD83FFF 000b4000
* MSASN1 000007FEFD5B0000 000007FEFD5BEFFF 0000f000
* schannel 000007FEFCB00000 000007FEFCB55FFF 00056000
* CRYPT32 000007FEFD7D0000 000007FEFD939FFF 0016a000
* security 0000000071390000 0000000071392FFF 00003000
* WS2_32 000007FEFF360000 000007FEFF3ACFFF 0004d000
* SHELL32 000007FEFE5D0000 000007FEFF357FFF 00d88000
* OLEAUT32 000007FEFDED0000 000007FEFDFA6FFF 000d7000
* ncrypt 000007FEFCF20000 000007FEFCF6CFFF 0004d000
* bcrypt 000007FEFCEF0000 000007FEFCF11FFF 00022000
* mswsock 000007FEFCDF0000 000007FEFCE44FFF 00055000
* wship6 000007FEFCFB0000 000007FEFCFB6FFF 00007000
* wshtcpip 000007FEFC720000 000007FEFC726FFF 00007000
* ntmarta 000007FEFC620000 000007FEFC64CFFF 0002d000
* WLDAP32 000007FEFE410000 000007FEFE461FFF 00052000
* ntdsapi 000007FEF7AF0000 000007FEF7B16FFF 00027000
* bcryptprimitives 000007FEFC9D0000 000007FEFCA1BFFF 0004c000
* SAMLIB 000007FEFBE10000 000007FEFBE2CFFF 0001d000
* CLBCatQ 000007FEFD960000 000007FEFD9F8FFF 00099000
* sqlncli10 0000000063720000 00000000639DCFFF 002bd000
* VERSION 000007FEFC650000 000007FEFC65BFFF 0000c000
* COMCTL32 000007FEFA110000 000007FEFA1AFFFF 000a0000
* COMDLG32 000007FEFDFC0000 000007FEFE056FFF 00097000
* SQLNCLIR10 00000000636E0000 0000000063716FFF 00037000
* netbios 000007FEF4340000 000007FEF4349FFF 0000a000
* xpstar 0000000063650000 00000000636D7FFF 00088000
* SQLSCM 0000000063640000 000000006364DFFF 0000e000
* ODBC32 000007FEF0AC0000 000007FEF0B70FFF 000b1000
* ATL80 0000000063620000 000000006363FFFF 00020000
* odbcint 00000000635E0000 0000000063617FFF 00038000
* clusapi 000007FEF91B0000 000007FEF91FFFFF 00050000
* resutils 000007FEF9190000 000007FEF91A8FFF 00019000
* xpstar 00000000635B0000 00000000635D4FFF 00025000
* dbghelp 0000000063330000 000000006348DFFF 0015e000
* P1Home: 000000000BB6A950: 00000000C0000005 0000000000000000 0000000000886B00 0000000000000002 00000000
What else should I have to do?
Thank you,
Horia -
Can anyone review please and recommend for this
Current time is 00:51:59 07/29/14.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.0.2531.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU E5530 @ 2.40GHz.
Bios Version is HP - 2
8 X64 level 8664, 14 Mhz processor (s).
Windows NT 6.0 Build 6002 CSD Service Pack 2.
Memory
MemoryLoad = 49%
Total Physical = 36852 MB
Available Physical = 18786 MB
Total Page File = 70733 MB
Available Page File = 53469 MB
Total Virtual = 8388607 MB
Available Virtual = 8350654 MB
***Unable to get thread context for spid 0
* BEGIN STACK DUMP:
* 07/29/14 00:51:59 spid 7332
* Non-yielding Scheduler
Hi Shanky,
This forum is one of my best teacher,but to clear confusion about this thread, earlier I posted for Non-yielding resource monitor bugcheck dump and this is for Non-yielding scheduler.
Thanks a lot.
All are almost same IMO in sense they point to bug in SQL Server. As you said you got three different SQL dumps in your 3 different environement but 2 of them were not updated to latest SP. One you confirmed as even after updating service pack
you still got error. If issue subsides after applying SP its good if it does not I strongly recommend you to open case with Microsoft. I agree it would require shedding some bucks but atleast you would get solution and have a relax mind. IMO only a Microsoft
engineer can analyze dumps in most accurate way. I am saying this with experience. So take your shot and ask MS guys to analyze it.
If you want to give it a shot refer link posted by Ashwin.
You are most welcome to post questions on forum.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Non-yielding Resource Monitor - Issue on PROD server
Hi
My PROD server frequently restarting after generating below dump.
Pls help me to resolve the issues
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5000.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current time is 11:33:40 01/23/12.
8 Unknown CPU 9., 3 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 99%
Total Physical = 65533 MB
Available Physical = 505 MB
Total Page File = 121256 MB
Available Page File = 46 MB
Total Virtual = 8388607 MB
Available Virtual = 8321060 MB
**Dump thread - spid = 0, PSS = 0x0000000000000000, EC = 0x0000000000000000
***Stack Dump being sent to E:\MSSQL2K5\MSSQL.1\MSSQL\LOG\SQLDump0111.txt
* BEGIN STACK DUMP:
* 01/23/12 11:33:40 spid 0
* Non-yielding Resource Monitor
* Short Stack DumpHi, everyone.
Do you have a solution for the mentioned problem? My dump looks like the dump in the first message. Server that runs ms sql server instance stops responding to any input, and I should reboot it. And yes I have MAX memory for the sql server set to 49152
My dump:
This file is generated by Microsoft SQL Server
version 11.0.3128.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is Intel(R) Xeon(R) CPU X5650 @ 2.67GHz.
Bios Version is INTEL - 0
BIOS Date: 09/30/09 12:52:30 Ver: 08.00.10
24 X64 level 8664, 2 Mhz processor (s).
Windows NT 6.2 Build 9200 CSD .
Memory
MemoryLoad = 99%
Total Physical = 73663 MB
Available Physical = 63 MB
Total Page File = 137151 MB
Available Page File = 61709 MB
Total Virtual = 8388607 MB
Available Virtual = 8302677 MB
**Dump thread - spid = 0, EC = 0x0000000000000000
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0023.txt
* BEGIN STACK DUMP:
* 03/16/15 00:05:40 spid 844
* Non-yielding Resource Monitor
* Short Stack Dump
Thanks! -
Hello Guys,
I hope someone can help me with this error. I have been searching from forums but typically, causes and resolutions are generalized. This is the first time it happened on our Win 2008 Server and we have not installed any (hardware/Software/Drivers)
for the past 3 years.
We do install monthly security patches and that is it... This server of ours is running on VM (VMWARE).
I hope you can shed light as I do not understand crash dumps..
Thank you
===============================
Opened log file 'c:\debuglogrlo.txt'
3: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
3: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e3045048, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 819c02bf, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
READ_ADDRESS: e3045048
FAULTING_IP:
nt!CmpCheckKey+61b
819c02bf 394724 cmp dword ptr [edi+24h],eax
MM_INTERNAL_CODE: 0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
TRAP_FRAME: 8d9bf9ec -- (.trap 0xffffffff8d9bf9ec)
.trap 0xffffffff8d9bf9ec
ErrCode = 00000000
eax=00000000 ebx=cecec024 ecx=3162f75f edx=00000035 esi=b52b1940 edi=e3045024
eip=819c02bf esp=8d9bfa60 ebp=8d9bfa8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!CmpCheckKey+0x61b:
819c02bf 394724 cmp dword ptr [edi+24h],eax ds:0023:e3045048=????????
.trap
Resetting default scope
LAST_CONTROL_TRANSFER: from 81891de4 to 818dc292
STACK_TEXT:
8d9bf9d4 81891de4 00000000 e3045048 00000000 nt!MmAccessFault+0x10b
8d9bf9d4 819c02bf 00000000 e3045048 00000000 nt!KiTrap0E+0xdc
8d9bfa8c 819c681a 01000001 009c4020 009c3f70 nt!CmpCheckKey+0x61b
8d9bfabc 819c6e48 b52b1940 01000001 00000006 nt!CmpCheckRegistry2+0x8c
8d9bfb04 819c186e 01000001 8d9bfc60 80002f38 nt!CmCheckRegistry+0xf5
8d9bfb60 819c3fdd 8d9bfbb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
8d9bfbd8 819c627d 8d9bfc60 00000000 8d9bfc4c nt!CmpInitHiveFromFile+0x19e
8d9bfc18 819bc4c5 8d9bfc60 00000000 8d9bfc7b nt!CmpCmdHiveOpen+0x36
8d9bfd14 819bc6fa 00000002 8193c5a0 00000002 nt!CmpFlushBackupHive+0x2fd
8d9bfd38 81a9bcbd 8194613c 84da3020 818e9d4a nt!CmpSyncBackupHives+0x90
8d9bfd44 818e9d4a 00000000 00000000 84da3020 nt!CmpPeriodicBackupFlushWorker+0x32
8d9bfd7c 81a1a01c 00000000 bcf90a9f 00000000 nt!ExpWorkerThread+0xfd
8d9bfdc0 81882eee 818e9c4d 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CmpCheckKey+61b
819c02bf 394724 cmp dword ptr [edi+24h],eax
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!CmpCheckKey+61b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51da1840
IMAGE_VERSION: 6.0.6002.18881
FAILURE_BUCKET_ID: 0x50_nt!CmpCheckKey+61b
BUCKET_ID: 0x50_nt!CmpCheckKey+61b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x50_nt!cmpcheckkey+61b
FAILURE_ID_HASH: {b0c48432-dfba-c9e0-33fc-874f17d1f0e6}
Followup: MachineOwner
eax=8d948120 ebx=00000000 ecx=81944200 edx=000003f0 esi=8d94813c edi=00000000
eip=818dc292 esp=8d9bf960 ebp=8d9bf9d4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
nt!MmAccessFault+0x10b:
818dc292 8b03 mov eax,dword ptr [ebx] ds:0023:00000000=????????
ChildEBP RetAddr Args to Child
8d9bf9d4 81891de4 00000000 e3045048 00000000 nt!MmAccessFault+0x10b
8d9bf9d4 819c02bf 00000000 e3045048 00000000 nt!KiTrap0E+0xdc (FPO: [0,0] TrapFrame @ 8d9bf9ec)
8d9bfa8c 819c681a 01000001 009c4020 009c3f70 nt!CmpCheckKey+0x61b
8d9bfabc 819c6e48 b52b1940 01000001 00000006 nt!CmpCheckRegistry2+0x8c
8d9bfb04 819c186e 01000001 8d9bfc60 80002f38 nt!CmCheckRegistry+0xf5
8d9bfb60 819c3fdd 8d9bfbb4 00000005 00000000 nt!CmpInitializeHive+0x4c1
8d9bfbd8 819c627d 8d9bfc60 00000000 8d9bfc4c nt!CmpInitHiveFromFile+0x19e
8d9bfc18 819bc4c5 8d9bfc60 00000000 8d9bfc7b nt!CmpCmdHiveOpen+0x36
8d9bfd14 819bc6fa 00000002 8193c5a0 00000002 nt!CmpFlushBackupHive+0x2fd
8d9bfd38 81a9bcbd 8194613c 84da3020 818e9d4a nt!CmpSyncBackupHives+0x90
8d9bfd44 818e9d4a 00000000 00000000 84da3020 nt!CmpPeriodicBackupFlushWorker+0x32 (FPO: [1,0,2])
8d9bfd7c 81a1a01c 00000000 bcf90a9f 00000000 nt!ExpWorkerThread+0xfd
8d9bfdc0 81882eee 818e9c4d 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name
8060e000 80615000 kdcom kdcom.dll Sat Apr 11 14:25:29 2009 (49E037D9)
80615000 80685000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Apr 11 14:23:19 2009 (49E03757)
80685000 80696000 PSHED PSHED.dll Sat Apr 11 14:25:32 2009 (49E037DC)
80696000 8069e000 BOOTVID BOOTVID.dll Sat Jan 19 15:27:15 2008 (4791A653)
8069e000 806df000 CLFS CLFS.SYS Sat Apr 11 12:13:51 2009 (49E018FF)
806df000 807bf000 CI CI.dll Sat Apr 11 14:25:22 2009 (49E037D2)
807d7000 807e5000 WDFLDR WDFLDR.SYS Thu Jul 26 10:36:38 2012 (5010AD36)
807e5000 807fc000 dfsc dfsc.sys Thu Apr 14 22:59:03 2011 (4DA70BB7)
81811000 81844000 hal halmacpi.dll Sat Apr 11 12:13:13 2009 (49E018D9)
81844000 81bfe000 nt ntkrpamp.exe Mon Jul 08 09:39:12 2013 (51DA1840)
81e01000 81f0c000 NDIS NDIS.SYS Sat Apr 11 12:45:52 2009 (49E02080)
81f0c000 81f37000 msrpc msrpc.sys Sat Apr 11 12:37:32 2009 (49E01E8C)
81f37000 81f72000 NETIO NETIO.SYS Sat Apr 11 12:46:21 2009 (49E0209D)
81f72000 81ff3000 Wdf01000 Wdf01000.sys Sat Jun 22 10:29:37 2013 (51C50C11)
8c805000 8c84b000 acpi acpi.sys Sat Apr 11 12:19:03 2009 (49E01A37)
8c84b000 8c854000 WMILIB WMILIB.SYS Sat Jan 19 13:53:08 2008 (47919044)
8c854000 8c85c000 msisadrv msisadrv.sys Sat Jan 19 13:32:51 2008 (47918B83)
8c85c000 8c883000 pci pci.sys Sat Apr 11 12:19:16 2009 (49E01A44)
8c883000 8c892000 partmgr partmgr.sys Sat Apr 11 12:39:19 2009 (49E01EF7)
8c892000 8c894900 compbatt compbatt.sys Sat Jan 19 13:32:47 2008 (47918B7F)
8c895000 8c89f000 BATTC BATTC.SYS Sat Jan 19 13:32:45 2008 (47918B7D)
8c89f000 8c8ae000 volmgr volmgr.sys Sat Jan 19 13:49:51 2008 (47918F7F)
8c8ae000 8c8f8000 volmgrx volmgrx.sys Sat Apr 11 12:39:25 2009 (49E01EFD)
8c8f8000 8c8ff000 intelide intelide.sys Sat Jan 19 13:49:42 2008 (47918F76)
8c8ff000 8c90d000 PCIIDEX PCIIDEX.SYS Sat Apr 11 12:39:09 2009 (49E01EED)
8c90d000 8c91cb80 vmci vmci.sys Tue May 01 09:12:40 2012 (4F9F3888)
8c91d000 8c92d000 mountmgr mountmgr.sys Sat Jan 19 13:49:13 2008 (47918F59)
8c92d000 8c93a580 vsock vsock.sys Sat Sep 29 12:59:03 2012 (50668017)
8c93b000 8c943000 atapi atapi.sys Sat Apr 11 12:39:09 2009 (49E01EED)
8c943000 8c961000 ataport ataport.SYS Sat Apr 11 12:39:10 2009 (49E01EEE)
8c961000 8c979000 lsi_sas lsi_sas.sys Sat Jun 30 09:01:01 2007 (4685AB4D)
8c979000 8c9ba000 storport storport.sys Sat Apr 11 12:39:19 2009 (49E01EF7)
8c9ba000 8c9ec000 fltmgr fltmgr.sys Sat Apr 11 12:13:59 2009 (49E01907)
8ca0d000 8ca6c000 SYMDS SYMDS.SYS Tue Jul 24 06:57:53 2012 (500DD6F1)
8ca6c000 8ca95000 vsepflt vsepflt.sys Tue Oct 30 18:37:14 2012 (508FADDA)
8ca95000 8cb7d000 SYMEFA SYMEFA.SYS Thu Oct 04 02:59:21 2012 (506C8B09)
8cb7d000 8cbef000 ksecdd ksecdd.sys Sat Jun 02 05:56:07 2012 (4FC93A77)
8cc0a000 8ccf4000 tcpip tcpip.sys Fri Jul 05 10:08:19 2013 (51D62A93)
8ccf4000 8cd0f000 fwpkclnt fwpkclnt.sys Sat Apr 11 12:45:42 2009 (49E02076)
8cd0f000 8cd16e00 storflt storflt.sys Sun Nov 18 10:29:44 2007 (473FA398)
8cd17000 8cd2a000 i8042prt i8042prt.sys Sat Jan 19 13:49:17 2008 (47918F5D)
8cd2a000 8cd35000 mouclass mouclass.sys Sat Jan 19 13:49:14 2008 (47918F5A)
8cd35000 8cd4d000 parport parport.sys Sat Jan 19 13:49:32 2008 (47918F6C)
8cd4d000 8cd67000 serial serial.sys Sat Jan 19 13:49:34 2008 (47918F6E)
8cd67000 8cd71000 serenum serenum.sys Sat Jan 19 13:49:29 2008 (47918F69)
8cd71000 8cd7c000 fdc fdc.sys Sat Jan 19 13:49:37 2008 (47918F71)
8cd7c000 8cd94000 cdrom cdrom.sys Sat Apr 11 12:39:17 2009 (49E01EF5)
8cd94000 8cdc2000 vm3dmp vm3dmp.sys Fri Oct 19 02:55:17 2012 (50805095)
8cdc2000 8cdd8000 tdx tdx.sys Sat Apr 11 12:45:56 2009 (49E02084)
8cdd8000 8cdf6000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Thu Oct 10 04:46:53 2013 (5255C0BD)
8ce09000 8cf19000 Ntfs Ntfs.sys Sun Mar 03 05:02:58 2013 (51326902)
8cf19000 8cf52000 volsnap volsnap.sys Thu Aug 16 21:53:34 2012 (502CFB5E)
8cf52000 8cf5a000 spldr spldr.sys Fri Jun 22 08:29:17 2007 (467B17DD)
8cf5a000 8cf69000 mup mup.sys Sat Apr 11 12:14:12 2009 (49E01914)
8cf69000 8cf7a000 disk disk.sys Sat Apr 11 12:39:14 2009 (49E01EF2)
8cf7a000 8cf9b000 CLASSPNP CLASSPNP.SYS Sat Apr 11 12:39:05 2009 (49E01EE9)
8cf9b000 8cfab000 agp440 agp440.sys Sat Jan 19 13:32:49 2008 (47918B81)
8cfab000 8cfb4000 crcdisk crcdisk.sys Sat Jan 19 13:50:29 2008 (47918FA5)
8cfe3000 8cfee000 tunnel tunnel.sys Sat Jan 19 13:55:50 2008 (479190E6)
8cfee000 8cff9000 kbdclass kbdclass.sys Sat Jan 19 13:49:14 2008 (47918F5A)
8cff9000 8cffa380 vmmouse vmmouse.sys Mon Jun 04 17:15:28 2012 (4FCC7CB0)
92404000 924a4000 dxgkrnl dxgkrnl.sys Thu Aug 01 09:31:36 2013 (51F9BA78)
924a4000 924b0000 watchdog watchdog.sys Sat Apr 11 12:22:43 2009 (49E01B13)
924b0000 924cd000 E1G60I32 E1G60I32.sys Wed Aug 08 00:14:13 2007 (46B89A55)
924cd000 924d0780 CmBatt CmBatt.sys Sat Jan 19 13:32:47 2008 (47918B7F)
924d1000 924e0000 intelppm intelppm.sys Sat Jan 19 13:27:20 2008 (47918A38)
924e0000 924e0c80 lmimirr lmimirr.sys Wed Apr 11 06:32:11 2007 (461C106B)
924e1000 92502000 VIDEOPRT VIDEOPRT.SYS Sat Jan 19 13:52:10 2008 (4791900A)
92502000 92531000 msiscsi msiscsi.sys Sat Apr 11 12:40:07 2009 (49E01F27)
92531000 9253c000 TDI TDI.SYS Sat Jan 19 13:57:10 2008 (47919136)
9253c000 92553000 rasl2tp rasl2tp.sys Sat Jan 19 13:56:33 2008 (47919111)
92553000 9255e000 ndistapi ndistapi.sys Sat Jan 19 13:56:24 2008 (47919108)
9255e000 92581000 ndiswan ndiswan.sys Sat Apr 11 12:46:31 2009 (49E020A7)
92581000 92590000 raspppoe raspppoe.sys Sat Apr 11 12:46:30 2009 (49E020A6)
92590000 925a4000 raspptp raspptp.sys Sat Jan 19 13:56:34 2008 (47919112)
925a4000 925b9000 rassstp rassstp.sys Sat Apr 11 12:46:40 2009 (49E020B0)
925b9000 925e3000 SYMEVENT SYMEVENT.SYS Wed Aug 22 13:32:47 2012 (50346EFF)
925e3000 925f1000 Npfs Npfs.SYS Sat Apr 11 12:14:01 2009 (49E01909)
92a0a000 92a93000 rdpdr rdpdr.sys Sat Apr 11 12:52:32 2009 (49E02210)
92a93000 92aa3000 termdd termdd.sys Sat Apr 11 12:51:14 2009 (49E021C2)
92aa3000 92aa4380 swenum swenum.sys Sat Jan 19 13:49:20 2008 (47918F60)
92aa5000 92acf000 ks ks.sys Sat Apr 11 12:38:47 2009 (49E01ED7)
92acf000 92ad9000 mssmbios mssmbios.sys Sat Jan 19 13:32:55 2008 (47918B87)
92ad9000 92ae6000 umbus umbus.sys Sat Jan 19 13:53:40 2008 (47919064)
92ae6000 92af0000 flpydisk flpydisk.sys Sat Jan 19 13:49:37 2008 (47918F71)
92af0000 92b01000 NDProxy NDProxy.SYS Sat Jan 19 13:56:28 2008 (4791910C)
92b01000 92b25000 ccSetx86 ccSetx86.sys Fri Aug 17 05:15:38 2012 (502D62FA)
92b25000 92bb8000 SRTSP SRTSP.SYS Fri Nov 02 04:14:38 2012 (5092D82E)
92bb8000 92bc8000 SRTSPX SRTSPX.SYS Wed Nov 16 06:27:18 2011 (4EC2E746)
92bc8000 92bf5000 Ironx86 Ironx86.SYS Tue Jul 24 08:34:17 2012 (500DED89)
93600000 93609000 rasacd rasacd.sys Sat Jan 19 13:56:31 2008 (4791910F)
93609000 93790e00 NAVEX15 NAVEX15.SYS Fri Aug 23 03:57:57 2013 (52166D45)
937a9000 937b7000 SymEPSecFlt SymEPSecFlt.sys Wed Mar 14 22:36:50 2012 (4F60AD02)
937b7000 937c0000 Fs_Rec Fs_Rec.SYS Wed Feb 29 21:32:36 2012 (4F4E28F4)
937c0000 937c7000 Null Null.SYS Sat Jan 19 13:49:12 2008 (47918F58)
937c7000 937ce000 Beep Beep.SYS Sat Jan 19 13:49:10 2008 (47918F56)
937ce000 937d5980 vmrawdsk vmrawdsk.sys Sat Mar 23 22:24:00 2013 (514DBB00)
937d6000 937e2000 vga vga.sys Sat Jan 19 13:52:06 2008 (47919006)
937e2000 937ea000 RDPCDD RDPCDD.sys Sat Jan 19 14:01:08 2008 (47919224)
937ea000 937f2000 rdpencdd rdpencdd.sys Sat Jan 19 14:01:09 2008 (47919225)
937f2000 937fd000 Msfs Msfs.SYS Sat Jan 19 13:28:08 2008 (47918A68)
97c0d000 97c69000 SYMTDIV SYMTDIV.SYS Sat Jul 21 10:01:00 2012 (500A0D5C)
97c69000 97c7d000 smb smb.sys Sat Apr 11 12:45:22 2009 (49E02062)
97c7d000 97cc5000 afd afd.sys Thu Apr 21 21:58:25 2011 (4DB03801)
97cc5000 97cf7000 netbt netbt.sys Sat Apr 11 12:45:35 2009 (49E0206F)
97cf7000 97d00000 ws2ifsl ws2ifsl.sys Sat Jan 19 13:56:49 2008 (47919121)
97d00000 97d16000 pacer pacer.sys Sat Apr 11 12:45:51 2009 (49E0207F)
97d16000 97d24000 netbios netbios.sys Sat Jan 19 13:55:45 2008 (479190E1)
97d24000 97d46700 vmhgfs vmhgfs.sys Sat Mar 23 22:17:43 2013 (514DB987)
97d47000 97d5a000 wanarp wanarp.sys Sat Jan 19 13:56:31 2008 (4791910F)
97d5a000 97d96000 rdbss rdbss.sys Sat Apr 11 12:14:26 2009 (49E01922)
97d96000 97da0000 nsiproxy nsiproxy.sys Sat Jan 19 13:55:50 2008 (479190E6)
97da0000 97dff000 eeCtrl eeCtrl.sys Thu Oct 10 04:46:53 2013 (5255C0BD)
9800e000 9811d000 BHDrvx86 BHDrvx86.sys Fri Mar 14 10:34:18 2014 (53226AAA)
9811d000 9812a000 crashdmp crashdmp.sys Sat Apr 11 12:39:12 2009 (49E01EF0)
9812a000 98134000 dump_diskdump dump_diskdump.sys Sat Apr 11 12:39:11 2009 (49E01EEF)
98134000 9814c000 dump_LSI_SAS dump_LSI_SAS.sys Sat Jun 30 09:01:01 2007 (4685AB4D)
9814c000 98156000 Dxapi Dxapi.sys Sat Jan 19 13:36:12 2008 (47918C4C)
98156000 98165000 monitor monitor.sys Sat Jan 19 13:52:19 2008 (47919013)
98165000 98180000 luafv luafv.sys Sat Jan 19 13:30:35 2008 (47918AFB)
98180000 981ab000 ofant ofant.sys Tue Nov 22 03:55:32 2011 (4ECAACB4)
981ab000 981b5000 LMIRfsDriver LMIRfsDriver.sys Tue Jul 15 00:26:22 2008 (487B7E2E)
9d440000 9d646000 win32k win32k.sys Fri Feb 07 18:38:29 2014 (52F4B7A5)
9d660000 9d669000 TSDDD TSDDD.dll Sat Jan 19 14:01:09 2008 (47919225)
9d680000 9d68e000 cdd cdd.dll Thu Aug 01 10:49:32 2013 (51F9CCBC)
a0606000 a06b6000 spsys spsys.sys Wed Mar 11 01:10:28 2009 (49B69F04)
a06b6000 a06c6000 lltdio lltdio.sys Sat Jan 19 13:55:03 2008 (479190B7)
a06c6000 a06d9000 rspndr rspndr.sys Sat Jan 19 13:55:03 2008 (479190B7)
a06d9000 a06f2000 bowser bowser.sys Tue Feb 22 21:23:54 2011 (4D63B8EA)
a06f2000 a0713000 mrxdav mrxdav.sys Sat Apr 11 12:14:39 2009 (49E0192F)
a0713000 a0732000 mrxsmb mrxsmb.sys Fri Apr 29 21:24:39 2011 (4DBABC17)
a0732000 a076b000 mrxsmb10 mrxsmb10.sys Wed Jul 06 23:31:46 2011 (4E147FE2)
a076b000 a0783000 mrxsmb20 mrxsmb20.sys Fri Apr 29 21:24:41 2011 (4DBABC19)
a0783000 a07f0000 HTTP HTTP.sys Sun Feb 21 04:53:31 2010 (4B804BCB)
a07f0000 a07f7000 parvdm parvdm.sys Sat Jan 19 13:49:28 2008 (47918F68)
a07f7000 a07f9080 vmmemctl vmmemctl.sys Sat Mar 23 22:23:46 2013 (514DBAF2)
a07fa000 a07fb800 RaInfo RaInfo.sys Sat Jan 05 02:57:12 2008 (477E8188)
a4808000 a48e6000 peauth peauth.sys Mon Oct 23 16:55:32 2006 (453C8384)
a48e6000 a48f0000 secdrv secdrv.SYS Wed Sep 13 21:18:32 2006 (45080528)
a48f0000 a490d000 srvnet srvnet.sys Fri Apr 29 21:25:08 2011 (4DBABC34)
a490d000 a4919000 tcpipreg tcpipreg.sys Wed Dec 09 01:26:18 2009 (4B1E8C3A)
a4919000 a491ce80 vstor2_mntapi10_shared vstor2-mntapi10-shared.sys Fri Nov 05 02:33:35 2010 (4CD2FC7F)
a491d000 a4945000 srv2 srv2.sys Fri Apr 29 21:25:09 2011 (4DBABC35)
a4945000 a4994000 srv srv.sys Fri Feb 18 22:03:28 2011 (4D5E7C30)
a4994000 a49aa000 cdfs cdfs.sys Sat Jan 19 13:28:02 2008 (47918A62)
a49aa000 a49b3000 asyncmac asyncmac.sys Sat Jan 19 13:56:29 2008 (4791910D)
a49b3000 a49c3000 fileinfo fileinfo.sys Sat Jan 19 13:34:27 2008 (47918BE3)
a49dd000 a49f2000 NAVENG NAVENG.SYS Fri Aug 23 03:59:23 2013 (52166D9B)
Unloaded modules:
a49c8000 a49dd000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49b3000 a49c8000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49dd000 a49f2000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49c8000 a49dd000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49b3000 a49c8000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49dd000 a49f2000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49c8000 a49dd000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
a49b3000 a49c8000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
93609000 93791000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
93794000 937a9000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00015000
9360c000 93794000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00188000
8cfb4000 8cfc1000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000D000
8cfc1000 8cfcb000 dump_storport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000A000
8cfcb000 8cfe3000 dump_LSI_SAS.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00018000
807bf000 807d7000 sacdrv.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00018000
Closing open log file c:\debuglogrlo.txtHi,
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM
cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.
Try the solution provided in this article:
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx
And this one:
Stop error message in Windows 7 or Windows Server 2008 R2: "Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)" or "Stop error code 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA)"
http://support.microsoft.com/kb/979538
Hope this helps. -
I had the following issue on Windows Server 2008 R2 Enterprise. I want to know if it's relarted with a specific driver in orider to avoid this happend again.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffff80000003, 0xfffff80001a8d016, 0xfffff880029eb788, 0xfffff880029eafe0). A dump was saved
in: C:WindowsMEMORY.DMP. Report Id: .
The dump is uploaded to the following skydrive link:
https://skydrive.live.com/?cid=FE2E04A1A3CB9D1D&id=FE2E04A1A3CB9D1D%21150
Please Could someone help me to know to witch is related?
Regards.
Juan.thanks a lot for the answer!
the expeption code of the bugcheck is the following:
0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference was encountered
I'm checking the drivers...maybe is related with some drivers installed in the system.
Is there any way to check the dump and confirm to witch driver is related?
Regards.
Juan. -
BSOD with BugCheck Error 1001 Memory Dump Help
Hello, I need a bit of help. My computer just crashed with a blue screen of death suddenly while I was doing some audio editing (I do this frequently, never had an issue before). I have no idea what to do with this memory dump I got, so I was
hoping someone could help me.
https://onedrive.live.com/redir?resid=3BE2487D830FFF04!107&authkey=!ANb7Ny6ZZXtBfL8&ithint=file%2c.dmp
That's the link to the memory dump file. Let me know if you need any other data from me. Thanks!Thompa2
This was Related to
lvrs64.sys Kernel Audio Improvement Filter Driver from Logitech Inc. I would install the newest driver available. Yours is ~ 2years old.
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364a6d0
Debug session time: Thu Feb 27 00:37:31.119 2014 (UTC - 5:00)
System Uptime: 0 days 15:35:44.212
BugCheck 1000007E, {ffffffffc0000005, fffff88002ec1fc6, fffff88007de3758, fffff88007de2fb0}
Probably caused by : lvrs64.sys ( lvrs64+2fc6 )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002ec1fc6, The address that the exception occurred at
Arg3: fffff88007de3758, Exception Record Address
Arg4: fffff88007de2fb0, Context Record Address
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
lvrs64+2fc6
fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d
EXCEPTION_RECORD: fffff88007de3758 -- (.exr 0xfffff88007de3758)
ExceptionAddress: fffff88002ec1fc6 (lvrs64+0x0000000000002fc6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000003cd464
Attempt to read from address 00000000003cd464
CONTEXT: fffff88007de2fb0 -- (.cxr 0xfffff88007de2fb0;r)
rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
r8=0000000000000000 r9=00000000003cd440 r10=0000000000000002
r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
r14=00000000003cd440 r15=00000000003cd440
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
lvrs64+0x2fc6:
fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
Last set context:
rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
r8=0000000000000000 r9=00000000003cd440 r10=0000000000000002
r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
r14=00000000003cd440 r15=00000000003cd440
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
lvrs64+0x2fc6:
fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000003cd464
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100
GetUlongFromAddress: unable to read from fffff800036b41c0
00000000003cd464 Nonpaged pool
FOLLOWUP_IP:
lvrs64+2fc6
fffff880`02ec1fc6 45396924 cmp dword ptr [r9+24h],r13d
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff88002ec1fc6
STACK_TEXT:
fffff880`07de3990 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`12f495f0 : lvrs64+0x2fc6
fffff880`07de3998 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`12f495f0 00000000`00000000 : 0x1
fffff880`07de39a0 00000000`00000000 : 00000000`00000000 fffffa80`12f495f0 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: lvrs64+2fc6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lvrs64
IMAGE_NAME: lvrs64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 505cb9b9
STACK_COMMAND: .cxr 0xfffff88007de2fb0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_lvrs64+2fc6
BUCKET_ID: X64_0x7E_lvrs64+2fc6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_lvrs64+2fc6
FAILURE_ID_HASH: {4d85bbe7-3359-5d02-03c0-19e8d54c8fdc}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag -
Multiple operating system crashes- the computer has rebooted from a bugcheck
For last couple of months I have been facing multiple crashes every day. Looking for help diagnose it. The memory dump file is 797 MB. Is there an option wherein I can make any sense out of it under guidance from community here- or should i simply try
a clean install of win 8.1Hi grensmoothie,
Any update here?
You may follow the guide posted by Team Zigzag (http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/warning-disabling-the-new-windows-update-ui-may/dc846517-eca0-4960-b0ff-1eb7227223f5),
For BSOD related issue, we do need the dump file to give a proper suggestion.
Besides, if you would like to debug the dump file by yourself, you may follow the WIKI article below:
Windows Bugcheck Analysis
Best regards
Michael Shao
TechNet Community Support -
Re-Occurring Blue Screen~Dump files included~Please Help~Unable to verify timestamp for ntkrnlpa.exe
Hello,
Starting yesterday I started getting the BSOD. I have uploaded my dump files to this dropbox account:
www.dropbox.com/sh/w3ryago8pfcw2y2/AAAR5i6Crx5q-p--xdESJjnMa
There are lots of them as my PC crashed many times.
I attempted to analyze them with windbg but all I can see is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Also I ran sfc /scannow and it found no integrity violations.
After the first BSOD I was barely able to get Windows to load without another immediate crash. I couldn't boot my PC last night but today seems okay so far. CPU temp was fine, actually quite cool as I had my window open right by the PC with the side off
the case and it was cold last night. Today, so far, seems to be running okay...so far anyways..
Windows update recently installed a driver for my on-board video card (Nvidia GeForce 6150n) on the 18th I think as I started using a 2nd monitor using the on-board card in addition to my PCI Express Ati Radeon HD. To use the second screen, I switched
the primary video in CMOS to on-board instead of PCI-E 16x so the on-board Nvidia card would be enabled.
I also installed brand new ram (4gb DDR2) about a month ago
and a new power supply 2 months ago. The power supply is not "exactly" the same voltage as the one that was in there but it's dang close. But I don't have any power leeching components.
Other than that nothing new has happened. After I got the crash, I tried to enter CMOS yesterday and it glitched out on me twice. I hope it's not my motherboard..
I am willing to do a system re-format as I am running Windows 7 32bit on a 64bit AMD so I wouldn't mind having 64 bit Windows anyways but I'd like to know what the problem is before I do this. Thank you.
Update: Just did a MalwareByte's Anti-Malware scan and no malware but found these items:
Scan Date: 5/22/2014
Scan Time: 6:08:00 PM
Logfile:
OS: Windows 7 Service Pack 1
CPU: x86
File System: NTFS
Scan Type: Threat Scan
Result: Completed
Objects Scanned: 261539
Time Elapsed: 8 min, 10 sec
Processes: 0
(No malicious items detected)
Modules: 0
(No malicious items detected)
Registry Keys: 0
(No malicious items detected)
Registry Values: 0
(No malicious items detected)
Registry Data: 0
(No malicious items detected)
Folders: 2
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0, , [dd97c58f413a74c2503e7106649ec23e],
Files: 9
PUP.Optional.OptimumInstaller.A, C:\Users\Justin\Downloads\Player-Chrome.exe, , [6b090a4a4437d363a05f361717ea718f],
PUP.Optional.Outbrowse, C:\Users\Justin\Downloads\install-flashplayer.exe, , [561ee173fe7d1125edf4d9a443be5aa6],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\icon-128.png, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\icon-16.png, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\icon-48.png, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\jquery-1.10.2.min.js, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\manifest.json, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\tweetwiki.js, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\_DS_Store, , [dd97c58f413a74c2503e7106649ec23e],
Physical Sectors: 0
(No malicious items detected)Hi,
All of the attached DMP files are of the
WHEA_UNCORRECTABLE_ERROR (124) bug check.
A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).
If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:
BugCheck 124, {0, 867d2024, b2000010, 10c0f}
===============================================================================
Section 2 : x86/x64 MCA
Descriptor @ 867d2134
Section @ 867d22bc
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xb200001000010c0f
This is a pretty complicated error compared to other possibilities it could have been, as it implies you have a hardware fault somewhere along the bus (not very definitive on its own).
In our case however, we can go a bit deeper with this one:
0: kd> .formats 0xb200001000010c0f
Evaluate expression:
Hex: b2000010`00010c0f
Decimal: -5620492266238833649
Octal: 1310000001000000206017
Binary: 10110010 00000000 00000000 00010000 00000000 00000001 00001100 00001111
Chars: ........
Time: ***** Invalid FILETIME
Float: low 9.61613e-041 high -7.45059e-009
Double: -7.41853e-068
Now that we have this info, we'd refer to the AMD manual:
63 VAL Valid
62 OVER Status Register Overflow
61 UC Uncorrected Error
60 EN Error Condition Enabled
59 MISCV Miscellaneous-Error Register Valid
58 ADDRV Error-Address Register Valid
57 PCC Processor-Context Corrupt
56–32 Other Information
31–16 Model-Specific Error Code
15–0 MCA Error Code
In our specific case, bit 63 of the status code is set, so it is valid. Bit 62 of the status code is
unset, therefore there's no overflow. Bit 61 implies an uncorrected error has occurred, and Bit 60 implies an error condition was enabled. Last but not least, Bit 57 is
set and implies a corrupted processor context.
If we take a look at the last 15 bits of the binary:
Binary: [trimming] 00001100 00001111
In our case, the MSB in binary (00001100 ), implies a bus error occurred (as I mentioned above). We need to further decode the bits to understand more:
[0000]1100 00001111
0000 = 1PPT RRRR IILL.
PP = Participation Processor, T = Timeout,
R = Memory Transaction Type, I = Memory and/or I/O, and finally
L = Cache Level.
With this said, it appears we actually have a faulty motherboard as the processor seems fine, etc. The only other thing I see possible is bad RAM, which you can figure out whether or not is the case by running no less than ~8 passes of Memtest:
Memtest86+:
Download Memtest86+ here:
http://www.memtest.org/
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary
files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because
of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance
is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
indows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (12 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`01847000 PsLoadedModuleList = 0xfffff800`01a0bdd0
Debug session time: Mon Nov 3 05:27:34.976 2014 (UTC - 5:00)
System Uptime: 81 days 16:48:21.023
* Bugcheck Analysis *
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600007f200, Address of the instruction which caused the bugcheck
Arg3: fffffa60155fff70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0007f200 0fba60300f bt dword ptr [rax+30h],0Fh
CONTEXT: fffffa60155fff70 -- (.cxr 0xfffffa60155fff70)
rax=000000000002f6bc rbx=0000000000000000 rcx=fffff900c1fad250
rdx=fffffa82bc20a330 rsi=fffff900c327a940 rdi=fffffa6015600820
rip=fffff9600007f200 rsp=fffffa60156007d0 rbp=0000000000000000
r8=0000000000000000 r9=000000000003fb36 r10=0000000000000000
r11=fffffa82aa1d6bb0 r12=0000000000000000 r13=0000000000000000
r14=000000000000491f r15=0000000000000001
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
win32k!PFEOBJ::vFreepfdg+0xe8:
fffff960`0007f200 0fba60300f bt dword ptr [rax+30h],0Fh ds:002b:00000000`0002f6ec=????????
Resetting default scope
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x3B
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff96000244030 to fffff9600007f200
STACK_TEXT:
fffffa60`156007d0 fffff960`00244030 : 00000000`00000000 fffffa82`bc20a300 00000000`00000001 00000000`0000491f : win32k!PFEOBJ::vFreepfdg+0xe8
fffffa60`15600800 fffff960`0024e647 : 00000000`00000000 fffff900`c0092000 fffff900`c0010000 00000000`00000000 : win32k!RFONTOBJ::vDeleteRFONT+0x210
fffffa60`15600860 fffff960`0024e2ba : 00000000`00000000 fffff900`c1eb4010 fffff900`c1eb4010 fffff900`c2c773a0 : win32k!vRestartKillRFONTList+0xab
fffffa60`156008b0 fffff960`000f9bc2 : fffff900`c08ac998 fffff900`c2685350 00000000`00000000 fffff900`00000001 : win32k!PFTOBJ::bUnloadWorkhorse+0x196
fffffa60`15600930 fffff960`000fa7a1 : fffff900`c08ac910 00000000`00000000 00000000`00000001 00000000`00000001 : win32k!vCleanupPrivateFonts+0x72
fffffa60`15600970 fffff960`000eebc4 : 00000000`00000000 00000000`00000000 fffff900`c2621180 00000000`ffffffff : win32k!NtGdiCloseProcess+0x479
fffffa60`156009d0 fffff960`000ee42b : 00000000`00000000 fffff900`c2621180 00000000`00000000 00000000`00000000 : win32k!GdiProcessCallout+0x1f4
fffffa60`15600a50 fffff800`01afa77c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa82`aa1d6bb0 : win32k!W32pProcessCallout+0x6f
fffffa60`15600a80 fffff800`01afcc7d : 00000000`00000000 fffffa82`aa1d6b01 00000000`00000000 00000000`00000000 : nt!PspExitThread+0x41c
fffffa60`15600b70 fffff800`01aed942 : 00000000`00000000 00000000`0000000c 00000000`fffdd000 fffff880`0000000c : nt!PspTerminateThreadByPointer+0x4d
fffffa60`15600bc0 fffff800`018a0f33 : fffffa82`ab4eac10 fffffa82`aa1d6bb0 fffffa60`15600ca0 00000000`fffdd000 : nt!NtTerminateProcess+0xfa
fffffa60`15600c20 00000000`779d6e5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0007ded8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779d6e5a
FOLLOWUP_IP:
win32k!PFEOBJ::vFreepfdg+e8
fffff960`0007f200 0fba60300f bt dword ptr [rax+30h],0Fh
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!PFEOBJ::vFreepfdg+e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4de794fc
STACK_COMMAND: .cxr 0xfffffa60155fff70 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
BUCKET_ID: X64_0x3B_win32k!PFEOBJ::vFreepfdg+e8
Followup: MachineOwnerHi,
Would you please let me know whether had done any change before this issue occurred? For examples, install
any third-party application (chrome.exe) or any other? Meanwhile, would you please let me confirm whether this issue occurred regularly?
For Bug Check 0x3B, it indicates that an exception happened while executing a routine that transitions from
non-privileged code to privileged code. For more details, please refer to following article and check if can help you.
Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION
Please update drivers and install all necessary Windows Updates, then monitor the result. If this issue still
exists, please perform a
clean boot. Any difference?
By the way, it may be not effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer
Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope this helps.
Best regards,
Justin Gu
Maybe you are looking for
-
How can I say an Application "Push that button"?
Hi all, I have set up a script to launch an application, and this works. But the application opens and waits for the user to push the button "AVVIO" ("Start") to run. I would like to tell the application, through the script, to push that "Start" butt
-
How to Cancel The Enter Query mode?
Please help me to Cancel the �Enter Query� mode.
-
Most favorable way to set up with new system?
Alright so here are my drives: 1. Samsung 840 EVO 250GB 2.5" SSD (174 GB free of 232GB) 2. Western Digital Caviar Blue 1TB 3.5" 7200RPM (886GB free of 931GB) 3. Western Digital Caviar Blue 1TB 3.5" 7200RPM (931GB free of 931GB) The way I have it setu
-
The connection factory name for jobs must be "JobQueueFactory
Hi Experts Can you plase help me to reslove this issue Caused by: com.sap.engine.services.deploy.container.DeploymentException: Deployment of jobs in application [backgrounjobear] failed, reason is : [Job "BackGroundJob" of bean "BackGroundJob" does
-
Hi, I need to put some validations in web dynpro java page which is "employee address page". I checked the BADI's but no badi exists which serve my purpsoe. Now I want to make the code change in web dynpro java. Pls answer the followng questions. 1-