Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD - Windows Server 2003


  • Please log in to reply
7 replies to this topic

#1 JinXiang91

JinXiang91

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 15 May 2017 - 08:40 PM

Hi Guys, Please assist on the following problem below.
 

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\itdept01\Desktop\Mini051517-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_qfe.130703-1535
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808b1a08
Debug session time: Mon May 15 22:36:24.421 2017 (UTC + 8:00)
System Uptime: 3 days 13:33:32.187
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000007E, {c0000095, 83a1a315, f514eae8, f514e7e4}
 
Probably caused by : srv.sys ( srv!ExecuteTransaction+29e )
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
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: c0000095, The exception code that was not handled
Arg2: 83a1a315, The address that the exception occurred at
Arg3: f514eae8, Exception Record Address
Arg4: f514e7e4, Context Record Address
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000095 - {EXCEPTION}  Integer overflow.
 
FAULTING_IP: 
+cdb475a1c0
83a1a315 ce              into
 
EXCEPTION_RECORD:  f514eae8 -- (.exr 0xfffffffff514eae8)
ExceptionAddress: 83a1a315
   ExceptionCode: c0000095 (Integer overflow)
  ExceptionFlags: 00000000
NumberParameters: 0
 
CONTEXT:  f514e7e4 -- (.cxr 0xfffffffff514e7e4;r)
eax=85f4f330 ebx=80800000 ecx=86ba27d0 edx=85f4f5b0 esi=e1db4ba1 edi=f514ebd5
eip=83a1a316 esp=f514ebb0 ebp=83513000 iopl=0         ov up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000a86
83a1a316 6d              ins     dword ptr es:[edi],dx es:0023:f514ebd5=5f808969
Last set context:
eax=85f4f330 ebx=80800000 ecx=86ba27d0 edx=85f4f5b0 esi=e1db4ba1 edi=f514ebd5
eip=83a1a316 esp=f514ebb0 ebp=83513000 iopl=0         ov up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000a86
83a1a316 6d              ins     dword ptr es:[edi],dx es:0023:f514ebd5=5f808969
Resetting default scope
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0x7E
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ERROR_CODE: (NTSTATUS) 0xc0000095 - {EXCEPTION}  Integer overflow.
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
LAST_CONTROL_TRANSFER:  from 8082dbd9 to 83a1a316
 
STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
f514ec68 8082dbd9 00000010 00000040 00000198 0x83a1a316
f514ecec f588a5bb 85acd1f0 85acd1f0 808385ed nt!ExAllocatePoolWithTagPriority+0x13f
f514ed78 f5867e87 85acd1f8 85add980 f58806c7 srv!ExecuteTransaction+0x29e
f514ed84 f58806c7 00000000 85f4f330 00000000 srv!SrvProcessSmb+0xb7
f514edac 809225c3 00add980 00000000 00000000 srv!WorkerThread+0x138
f514eddc 8083fa5f f5880602 85add980 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
FOLLOWUP_IP: 
srv!ExecuteTransaction+29e
f588a5bb 8bd8            mov     ebx,eax
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  srv!ExecuteTransaction+29e
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: srv
 
IMAGE_NAME:  srv.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4d5d53a9
 
IMAGE_VERSION:  5.2.3790.4832
 
STACK_COMMAND:  .cxr 0xfffffffff514e7e4 ; kb
 
FAILURE_BUCKET_ID:  0x7E_srv!ExecuteTransaction+29e
 
BUCKET_ID:  0x7E_srv!ExecuteTransaction+29e
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x7e_srv!executetransaction+29e
 
FAILURE_ID_HASH:  {2b45039c-6c84-3b5f-ecf9-3f1cae326dfa}
 
Followup: MachineOwner
 
 
Please advise what could be the problem?

Thanks.

Minidmp : https://www.mediafire.com/?hhnqkc318x1jaf3

Edited by JinXiang91, 15 May 2017 - 09:16 PM.


BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,952 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:46 PM

Posted 15 May 2017 - 08:53 PM

Please follow these BSOD posting instructions and attach the requested files by replying to this topic.
 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 JinXiang91

JinXiang91
  • Topic Starter

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 15 May 2017 - 09:17 PM

Please follow these BSOD posting instructions and attach the requested files by replying to this topic.
 

Hi,

As SysnativeBSODCollectionApp doesn't support Windows Server 2003, I will be uploading the msinfo32 instead.

See attached for details.

Thanks.

Attached Files



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,952 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:46 PM

Posted 15 May 2017 - 10:24 PM

Sorry, forgot about that. Try this alternate tool (thanks blueelvis!):

 

https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

 

If that fails too, zip up the contents of C:\Windows\Minidump and attach them in your next reply.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 JinXiang91

JinXiang91
  • Topic Starter

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 15 May 2017 - 10:28 PM

Sorry, forgot about that. Try this alternate tool (thanks blueelvis!):

 

https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

 

If that fails too, zip up the contents of C:\Windows\Minidump and attach them in your next reply.

Hi,

 

It can't be used as well. 

 

I have already attached the link on my thread >> Minidmp : https://www.mediafire.com/?hhnqkc318x1jaf3

 

Thanks.


Edited by JinXiang91, 15 May 2017 - 10:28 PM.


#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,952 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:46 PM

Posted 15 May 2017 - 10:44 PM

Sorry, but please upload the files directly here at BleepingComputer.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 JinXiang91

JinXiang91
  • Topic Starter

  • Members
  • 97 posts
  • OFFLINE
  •  

Posted 15 May 2017 - 10:52 PM

Sorry, but please upload the files directly here at BleepingComputer.

Hi 

Ok noted. Here you go.

Thanks.

Attached Files



#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,952 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:12:46 PM

Posted 17 May 2017 - 10:13 AM

Very little info in that dump. Let's have a look at a full kernel dump file:

:step1: Upload MEMORY.DMP

• Press and hold the Windows Key + R on your keyboard at the same time.
• In the Run box, type in %WinDir% and hit Enter on your keyboard.
• Find the file MEMORY.DMP and copy/paste it on to your Desktop.
• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to a trustworthy file-sharing service (not MediaFire please!)

Apart from that, since this is an older system, I tend to think hardware is the real issue. Suggest you do the following:

-monitor your temps with HWMonitor
-update your BIOS (if your computer could lose power unexpectedly, please don't!)
-run MemTest86 for a minimum of eight passes. A guideis available here if you need help.
-run Seagate SeaTools for Windows. Test all your drives with the S.M.A.R.T. and Long Generic tests.
-run Prime95 (read the details in the link)
-run these remaining hardware diagnostics


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users