Код ошибки 0x805000f

В течении полугода от 2 х раз в день до 1 раза в три дня система выпадает в синий экран и перезагружается.

Код ошибки 000000d1, параметр1 00f89005, параметр2 00000002, параметр3 00000001, параметр4 77f509dc.

Причина непредвиденного завершения работы данного компьютера, предоставленная пользователем IAFNSERVER\Administrator: Отказ системы: Ошибка STOP
Код причины: 0x805000f
Код ошибки:
Строка проверки: 0x000000d1 (0x00f89005, 0x00000002, 0x00000001, 0x77f509dc)
Комментарий: 0x000000d1 (0x00f89005, 0x00000002, 0x00000001, 0x77f509dc)

поиски инфы по похожим ошибкам  в интеренте причин этой ошибки дали мало.

1) Переустановка драйверов не помогла.

2) Тест винтов и оперативки выявил полную годность обоих

3) Смена питальника тоже не принесла результата

Может быть сдесь найдется специалист сталкивавшийся с этой проблемой… Если есть возможность помочь помогите плиз. Система Windows 2003 Enterprise Edition на ней крутится IIS, фтп сервер, файловый сервер. Антивирь нод32, фаервол Агниттум.

Сама система: Pentium D 2,66, 2 гб оператвки Samsung, Питальник FSP 350 w, но честный. 3 винта 2 саташника и 1н идешник

  • Изменен тип

    2 августа 2010 г. 12:48
    давность и отсутствие активности в теме

Источник
  • Remove From My Forums

  • Question

  • Hello,

    We have a system running windows server 2003 R2 64bit with  Oracle RAC (oracle database 11g )

    some times an Unexpected shutdown occur with the error below :

    Event Type:    Warning
    Event Source:    USER32
    Event Category:    None
    Event ID:    1076
    Date:        12/14/2011
    Time:        6:25:48 AM
    User:        XX\administrator
    Computer:    XXXXXXX
    Description:
    The reason supplied by user XX\administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
     Reason Code: 0x805000f
     Bug ID:
     Bugcheck String: 0x000000d1 (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffffadd8cf20216)
     Comment: 0x000000d1 (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffffadd8cf20216)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 0f 00 05 08               ….   

    after search for a solution on this issue i found this hot fix from Microsoft and it seems to me they are talking about the same issue

    http://support.microsoft.com/kb/937455

    anyone know if this patch is useful or there is no side effects

    Thanks. 

Answers

    • Marked as answer by

      Tuesday, December 27, 2011 12:57 AM

Источник

I had this problem a few days ago, and this information might help you.

Problem:

Hardware: IBM Blade – Firmware and drivers are not upgraded since December 2010

OS: windows Server 2003 Enterprise, Service Pack 2, Not Updated since November 2011

Function :  Front end Web Servers.

Problem : Server crashed reporting the reason “System Failure: Stop error Reason Code: 0x805000f”.

Evidence that could collect at the System log, and memory DUMPS.

This slideshow requires JavaScript.

Check Slide Show to see events is System Log.

Were also generated two Dump files (Mini022112-01.DMP e MEMORY.DMP), when server failed.

After a review of “Mini022112-01.dmp” it was found that the process that led to the Crash was ProcessXP version 11.3 (MODULE_NAME: PROCEXP113), see Annex CrashDumpAnalisys.txt.

After a review of “MEMORY.DMP” the following sentence was removed from the report “Probably Caused by: PROCEXP113.SYS (PROCEXP113 +1210).” Check Slide Show.

Recommendations to prevent the problem from occurring again, and work plan to perform in all Servers Windows 2003 32 Bits.

1 – It is advisable to use the latest version of Process Explorer v15.13 http://technet.microsoft.com/en-us/sysinternals/bb896653

2 – Installation of all Security Updates on failure, and Service Packs

3 – Upgrade Firmware and drivers. It was withdrawn following information from “CrashMemoryDUMP” analysis.

“BAD_POOL_HEADER (19)

The pool is corrupt Already at the time of the current request. This may or may not be due to the caller.
The internal pool links must be Walked to figure out the Possible causes of the problem, and then special pool Applied to the suspect tags or the driver verifier to a suspect driver. ” check this link http://msdn.microsoft.com/en-us/library/ff557389%28v=vs.85%29.aspx

4 – I’ve checked that the file Ntfs.sys is not the most recent file and should be Updated to a newer version, check security patchKB937455, will undoubtedly reduce the number of similar problems. However it is not imperative that it be installed.

After speaking with the user that was working with the ProcessXp.exe we clear the last dough that is: He lost connection to the server RDP session, at the moment that he choose the option “Find” in ProcessXP.

To Resume:
An older version of ProcessXP, when option find is used, with Firmware and Drivers not updated), will caused a unexpected Shut down (blue screen).

To analyse the problem I’ve used Win debug, Dumps generated when crash happened and Event Logs. The user input, was also very important to get all the information needed.

You can also check this website that has valid information about this problem. http://forum.sysinternals.com/procexpexe-bluescreen-on-find_topic22598.html

hope that this information can be useful.

Источник

I have a Windows 2003 installation sitting on an Intel 945GNTL MB, 2.8 GHz P4, 3GB of RAM. For over half a year, the Windows 2003 crash randomly when copying files, causing file corruption/data lost and virtually an unusable server. Quite a bit of time is devoted investigating the problem, and I appreciate if you can help me out :)

I learned that a server dump may pin point the root of the problem, and I want to dig it out and fix the problem…please let me know any findings, thanks :)

Case reproduction

  1. The case is reproducible either HDD to HDD or network to HDD copy/move operations
  2. The case is reproducible using 3 different models of harddrives from 2 manufracturers
  3. The case is reproducible in a FRESH installation of Windows 2003 SP2 with a slow (not quick) format, power supply and system/HDD cooling not a problem
  4. The case is reproducible when write operation is performed — crash randomly and causing data lost/file corruption -> unuseable server
  5. The case is not reproducible when read operation is performed

Event log entry

Event ID:
1076

Description:
The reason supplied by user HKSRV01\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x0000007e (0xc0000005, 0x8088c10b, 0xb95fab28, 0xb95fa824)
Comment: 0x0000007e (0xc0000005, 0x8088c10b, 0xb95fab28, 0xb95fa824)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Debugger output

Opened log file ‘c:\debuglog.txt’
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
…………………………………………………………………………………………………….
Loading User Symbols

Loading unloaded module list
……….
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8088c10b, The address that the exception occurred at
Arg3: b95fab28, Exception Record Address
Arg4: b95fa824, 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:
nt!ExDeferredFreePool+105
8088c10b 8b10 mov edx,dword ptr [eax]

EXCEPTION_RECORD: b95fab28 — (.exr ffffffffb95fab28)
.exr ffffffffb95fab28
ExceptionAddress: 8088c10b (nt!ExDeferredFreePool+0x00000105)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 32731123
Attempt to read from address 32731123

CONTEXT: b95fa824 — (.cxr ffffffffb95fa824)
.cxr ffffffffb95fa824
eax=32731123 ebx=00000000 ecx=000001ff edx=00000000 esi=8a9bd060 edi=e553a000
eip=8088c10b esp=b95fabf0 ebp=b95fac28 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!ExDeferredFreePool+0x105:
8088c10b 8b10 mov edx,dword ptr [eax] ds:0023:32731123=????????
.cxr
Resetting default scope

DEFAULT_BUCKET_ID: 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».

READ_ADDRESS: 32731123

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8088c881 to 8088c10b

STACK_TEXT:
b95fac28 8088c881 8a9bd060 8997fd48 e553ba40 nt!ExDeferredFreePool+0x105
b95fac7c b8e08722 e553ba38 00000000 b8e0f155 nt!ExFreePoolWithTag+0x54b
b95fac88 b8e0f155 00000015 e553ba40 8997fd48 srv!SrvFreePagedPool+0x2a
b95fac9c b8e114a7 899c1bf0 e553ba40 8976f148 srv!SrvFreeTransaction+0x70
b95facb0 b8e0eb06 00000000 8976f148 e553ba40 srv!SrvDereferenceTransaction+0x6b
b95face8 b8e12772 00000014 00000000 8976f148 srv!SrvCompleteExecuteTransaction+0xd0
b95fad00 b8e11432 b8e0380c 8976f148 89996738 srv!ExecuteTransaction+0x352
b95fad78 b8df4e87 8976f150 89996700 b8e086c7 srv!SrvSmbTransaction+0x7ac
b95fad84 b8e086c7 00000000 8920a8a8 00000000 srv!SrvProcessSmb+0xb7
b95fadac 809418f4 00996700 00000000 00000000 srv!WorkerThread+0x138
b95faddc 80887f4a b8e08602 89996700 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
nt!ExDeferredFreePool+105
8088c10b 8b10 mov edx,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

SYMBOL_NAME: nt!ExDeferredFreePool+105

MODULE_NAME: Pool_Corruption

STACK_COMMAND: .cxr 0xffffffffb95fa824 ; kb

FAILURE_BUCKET_ID: 0x7E_nt!ExDeferredFreePool+105

BUCKET_ID: 0x7E_nt!ExDeferredFreePool+105

Followup: Pool_corruption
———
(Refer to attachment for the rest)

Источник

Понравилась статья? Поделить с друзьями:
  • Код ошибки 0x803fb005 windows store
  • Код ошибки 0x8024a10a
  • Код ошибки 0x803f8001 майнкрафт
  • Код ошибки 0x80300024 при установке windows 10
  • Код ошибки 0x803fabba