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 IRQL Help!


  • Please log in to reply
No replies to this topic

#1 peteyo

peteyo

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:59 AM

Posted 15 February 2016 - 08:32 AM

Hi everyone,
 
I was hoping someone here could help me.
I am running Server 2003 SP2 and about a week or so ago the machine 
BSODs randomly. I have not installed any new software and all windows update are up to date.
Here is the log of my most recent minidmp file. Any help is greatly appreciated!
 
 
-----------------------------------------------------
 
Microsoft ® Windows Debugger Version 10.0.10586.567 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [\\192.168.1.30\Public_Storage\Mini021116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: srv*
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.150316-2035
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808b1a08
Debug session time: Thu Feb 11 16:25:46.140 2016 (UTC - 5:00)
System Uptime: 1 days 7:12:06.859
Loading Kernel Symbols
...............................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck A, {34, d0000002, 1, 80a854a9}
 
Probably caused by : ntkrnlmp.exe ( nt!KiTrap0E+18c )
 
Followup:     MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000034, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80a854a9, address which referenced memory
 
Debugging Details:
------------------
 
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 400
 
BUILD_VERSION_STRING:  3790.srv03_sp2_qfe.150316-2035
 
SYSTEM_MANUFACTURER:   
 
BIOS_VENDOR:  Award Software International, Inc.
 
BIOS_VERSION:  6.00 PG
 
BIOS_DATE:  12/20/2002
 
BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., LTD
 
BASEBOARD_PRODUCT:  7DPXDW-P
 
BASEBOARD_VERSION:  1.x
 
DUMP_TYPE:  2
 
BUGCHECK_P1: 34
 
BUGCHECK_P2: ffffffffd0000002
 
BUGCHECK_P3: 1
 
BUGCHECK_P4: ffffffff80a854a9
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 808a7294
Unable to get MmSystemRangeStart
 00000034 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+19
80a854a9 8711            xchg    edx,dword ptr [ecx]
 
CPU_COUNT: 2
 
CPU_MHZ: 855
 
CPU_VENDOR:  AuthenticAMD
 
CPU_FAMILY: 6
 
CPU_MODEL: 8
 
CPU_STEPPING: 1
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
ANALYSIS_SESSION_HOST:  JIMLEW
 
ANALYSIS_SESSION_TIME:  02-15-2016 08:16:37.0368
 
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
 
TRAP_FRAME:  f78c6c64 -- (.trap 0xfffffffff78c6c64)
ErrCode = 00000002
eax=f78c6ce8 ebx=00000000 ecx=00000034 edx=f78c6ce8 esi=00000000 edi=89f988b8
eip=80a854a9 esp=f78c6cd8 ebp=f78c6cf4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19:
80a854a9 8711            xchg    edx,dword ptr [ecx]  ds:0023:00000034=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from 80a854a9 to 808369dc
 
STACK_TEXT:  
f78c6c64 80a854a9 badb0d00 f78c6ce8 f78c6c84 nt!KiTrap0E+0x18c
f78c6cd4 8083df41 8084bbd0 e23a29d0 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x19
f78c6cf4 f72749f9 f78c6d54 8871c5c0 00000000 nt!ExReleaseResourceLite+0x20
f78c6d08 80844606 e23a2908 808aebf0 886394b0 Ntfs!NtfsReleaseScbFromLazyWrite+0x76
f78c6d40 80842e36 89f988b8 808b9140 89f8d100 nt!CcWriteBehind+0x12a
f78c6d80 8082d893 89f8d100 00000000 89f988b8 nt!CcWorkerThread+0x15a
f78c6dac 809225d3 89f8d100 00000000 00000000 nt!ExpWorkerThread+0xeb
f78c6ddc 8083fa5f 8082d7d6 00000000 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  72c952e2fd7a1cef5384fafc4ecf78d14812c7b7
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  48829303c1c08156c034ea5d3ed2d26a3e2c0598
 
THREAD_SHA1_HASH_MOD:  c550c79cab0c579e3cebd36fbb95efdb30821d6e
 
FOLLOWUP_IP: 
nt!KiTrap0E+18c
808369dc 833d000e8b8000  cmp     dword ptr [nt!KiFreezeFlag (808b0e00)],0
 
FAULT_INSTR_CODE:  e003d83
 
SYMBOL_STACK_INDEX:  0
 
SYMBOL_NAME:  nt!KiTrap0E+18c
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5507c4b5
 
IMAGE_VERSION:  5.2.3790.5583
 
FAILURE_BUCKET_ID:  0xA_nt!KiTrap0E+18c
 
BUCKET_ID:  0xA_nt!KiTrap0E+18c
 
PRIMARY_PROBLEM_CLASS:  0xA_nt!KiTrap0E+18c
 
TARGET_TIME:  2016-02-11T21:25:46.000Z
 
OSBUILD:  3790
 
OSSERVICEPACK:  2000
 
SERVICEPACK_NUMBER: 2
 
OS_REVISION: 0
 
SUITE_MASK:  272
 
PRODUCT_TYPE:  3
 
OSPLATFORM_TYPE:  x86
 
OSNAME:  Windows Server 2003
 
OSEDITION:  Windows Server 2003 Server (Service Pack 2) TerminalServer SingleUserTS
 
OS_LOCALE:  
 
USER_LCID:  0
 
OSBUILD_TIMESTAMP:  2015-03-17 02:07:49
 
BUILDOSVER_STR:  5.2.3790.srv03_sp2_qfe.150316-2035
 
ANALYSIS_SESSION_ELAPSED_TIME: 223
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0xa_nt!kitrap0e+18c
 
FAILURE_ID_HASH:  {a125c8d1-2345-ee89-8cda-62b4ff676382}
 
Followup:     MachineOwner


BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users