J. Rust Posted March 29, 2005 Report Share Posted March 29, 2005 ОС: Windows XP (SP2) Eng + все последние критические обновления, доступные через Windows Update Проблема: раз в 2-3 дня ОС падает в синий экран при закрытии окна IE со следующим текстом: A problem has been detected and windows has been shut dow to prevent damage to your computer. PAGE_FAULT_IN_NONPAGED_AREA If this is the first time you`ve seen this stop error screen, restart your computer. If this screen appears again, follow these steps:Chek to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need. If problems continue, disable or remove any newly installed hardware or software. Disable Bios memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode. Technical information: *** Stop : 0x00000050(……) Beginning dump of physical memory Physical memory dump complete Contact your system administrator or technical support group for further assistance. Повторюсь, что проблема возникает ТОЛЬКО при закрытии окна IE Уважаемые специалисты, есть какие-нибудь мысли ? Quote Link to comment Share on other sites More sharing options...
Stolik Posted March 29, 2005 Report Share Posted March 29, 2005 Есть :-) Появляется, когда запрошенная информация не была найдена в памяти. Система проверяет файл подкачки (page file), но отсутствующая информация была обозначена, как невозможная для записи в файл подкачки (page file). Подробности. Удачи. Quote Link to comment Share on other sites More sharing options...
J. Rust Posted April 7, 2005 Author Report Share Posted April 7, 2005 информация из минидампа: C:\Program Files\Support Tools>dumpchk -v c:\downloads\mini.dmp Loading dump file c:\downloads\mini.dmp ----- 32 bit Kernel Mini Dump Analysis DUMP_HEADER32: MajorVersion 0000000f MinorVersion 00000a28 DirectoryTableBase 00039000 PfnDataBase 8180a000 PsLoadedModuleList 8055ab20 PsActiveProcessHead 80560bd8 MachineImageType 0000014c NumberProcessors 00000001 BugCheckCode 10000050 BugCheckParameter1 bad0b148 BugCheckParameter2 00000000 BugCheckParameter3 80563fe2 BugCheckParameter4 00000000 PaeEnabled 00000000 KdDebuggerDataBlock 8054c760 MiniDumpFields 00000dff TRIAGE_DUMP32: ServicePackBuild 00000200 SizeOfDump 00010000 ValidOffset 0000fffc ContextOffset 00000320 ExceptionOffset 000007d0 MmOffset 00001068 UnloadedDriversOffset 000010a0 PrcbOffset 00001878 ProcessOffset 000024c8 ThreadOffset 00002728 CallStackOffset 00002980 SizeOfCallStack 000003d4 DriverListOffset 00002fe8 DriverCount 00000087 StringPoolOffset 00005800 StringPoolSize 000012a0 BrokenDriverOffset 00000000 TriageOptions 00000041 TopOfStack f64e4c2c DebuggerDataOffset 00002d58 DebuggerDataSize 00000290 DataBlocksOffset 00006aa0 DataBlocksCount 00000002 Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20 Debug session time: Thu Apr 07 11:45:46 2005 System Uptime: 0 days 1:37:34 start end module name 804d7000 806eb780 nt Checksum: 002160C9 Timestamp: Wed Aug 04 10: 19:48 2004 (41108004) Unloaded modules: f3ee1000 f3f0b000 kmixer.sys Timestamp: unavailable (00000000) f4f0c000 f4f36000 kmixer.sys Timestamp: unavailable (00000000) f5166000 f5190000 kmixer.sys Timestamp: unavailable (00000000) f4965000 f498f000 kmixer.sys Timestamp: unavailable (00000000) f5166000 f5190000 kmixer.sys Timestamp: unavailable (00000000) f5911000 f593b000 kmixer.sys Timestamp: unavailable (00000000) f5911000 f593b000 kmixer.sys Timestamp: unavailable (00000000) f5cc6000 f5cf0000 kmixer.sys Timestamp: unavailable (00000000) fa1c2000 fa1c3000 drmkaud.sys Timestamp: unavailable (00000000) f5e90000 f5e9d000 DMusic.sys Timestamp: unavailable (00000000) f5d90000 f5db3000 aec.sys Timestamp: unavailable (00000000) f5ea0000 f5eae000 swmidi.sys Timestamp: unavailable (00000000) fa02c000 fa02e000 splitter.sys Timestamp: unavailable (00000000) f6565000 f6572000 VPCNetS2.sys Timestamp: unavailable (00000000) f9e02000 f9e07000 Cdaudio.SYS Timestamp: unavailable (00000000) f9f0a000 f9f0d000 Sfloppy.SYS Timestamp: unavailable (00000000) Finished dump check Quote Link to comment Share on other sites More sharing options...
J. Rust Posted April 7, 2005 Author Report Share Posted April 7, 2005 Информация отладчика: C:\Program Files\Debugging Tools for Windows>kd -y srv*c:\symbols*http://msdl.mi crosoft.com/download/symbols -i c:\i386\i386 -z mini.dmp Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Program Files\Debugging Tools for Windows\mini.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: c:\i386\i386 Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_rtm.040803-2158 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20 Debug session time: Thu Apr 7 11:45:46.348 2005 (GMT+4) System Uptime: 0 days 1:37:34.951 Loading Kernel Symbols ................................................................................ ...................................................... Loading unloaded module list ................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10000050, {bad0b148, 0, 80563fe2, 0} Unable to load image spider.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for spider.sys *** ERROR: Module load completed but symbols could not be loaded for spider.sys Could not read faulting driver name Probably caused by : spider.sys ( spider+a48d ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * 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: bad0b148, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 80563fe2, If non-zero, the instruction address which referenced the bad me mory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: bad0b148 FAULTING_IP: nt!ObpRemoveObjectRoutine+cb 80563fe2 833800 cmp dword ptr [eax],0x0 MM_INTERNAL_CODE: 0 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 LAST_CONTROL_TRANSFER: from 804e3c55 to 80563fe2 STACK_TEXT: f64e4ca0 804e3c55 e1b0fd48 00000000 821a0b20 nt!ObpRemoveObjectRoutine+0xcb f64e4cc4 805814b1 00000000 821a08e8 00000000 nt!ObfDereferenceObject+0x5f f64e4ce8 f644248d e1b0fd48 00000000 00000000 nt!PsImpersonateClient+0x2f0 WARNING: Stack unwind information not available. Following frames may be wrong. f64e4d50 f64420cc ff49a518 f64e4d8c f64e4d88 spider+0xa48d f64e4dac 8057dfed 00000000 00000000 00000000 spider+0xa0cc f64e4ddc 804fa477 f6441fd0 00000000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: spider+a48d f644248d ?? ??? SYMBOL_STACK_INDEX: 3 FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: spider+a48d MODULE_NAME: spider IMAGE_NAME: spider.sys DEBUG_FLR_IMAGE_TIMESTAMP: 41c1cba7 STACK_COMMAND: kb FAILURE_BUCKET_ID: 0x50_BADMEMREF_spider+a48d BUCKET_ID: 0x50_BADMEMREF_spider+a48d Followup: MachineOwner --------- ---------------------------------------------------------------------------------------------- я так понял проблема в драйвере SPIDER.SYS (DrWeb) ??? Quote Link to comment Share on other sites More sharing options...
MrSlater Posted April 7, 2005 Report Share Posted April 7, 2005 Зайди на сайт майкрософт в меню поиска набери Stop : 0x00000050 и посмотри что там пишут. Обычно там могут дать решение этой проблемы Quote Link to comment Share on other sites More sharing options...
J. Rust Posted April 15, 2005 Author Report Share Posted April 15, 2005 проблема оказалась в драйвере SPIDER.SYS (DrWeb 4.32b) .. В службе поддержки обещали исправить баг к следующей версии .. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.