adik0011 Napisano Listopad 22, 2014 Zgłoś Share Napisano Listopad 22, 2014 Witam.Mam problem z Laptopem.System to Windows 7.Wczoraj wieczorem działał normalnie.Dziś przy starcie wywala bluescreena.Laptop odpala normalnie tylko w trybie awaryjnym.Dodaje ostatniego dumpaCrash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)Online Crash Dump Analysis ServiceSee http://www.osronline.com for more informationWindows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.18409.x86fre.win7sp1_gdr.140303-2144Machine Name:Kernel base = 0x82c06000 PsLoadedModuleList = 0x82d4f5b0Debug session time: Sat Nov 22 03:06:49.289 2014 (UTC - 5:00)System Uptime: 0 days 0:00:06.302******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)An attempt was made to write to readonly memory. The guilty driver is on thestack trace (and is typically the current instruction pointer).When possible, the guilty driver's name (Unicode string) is printed onthe bugcheck screen and saved in KiBugCheckDriver.Arguments:Arg1: 9291b484, Virtual address for the attempted write.Arg2: b2273121, PTE contents.Arg3: 833867e0, (reserved)Arg4: 0000000b, (reserved)Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program riage\modclass.ini, error 2DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULTBUGCHECK_STR: 0xBEPROCESS_NAME: SystemCURRENT_IRQL: 0TRAP_FRAME: 833867e0 -- (.trap 0xffffffff833867e0)ErrCode = 00000003eax=9291b484 ebx=00000000 ecx=9291b73e edx=9293ceac esi=00021980 edi=9291b5a6eip=9293ceac esp=83386854 ebp=83386878 iopl=0 nv up ei ng nz na pe nccs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210286aswSP+0x57eac:9293ceac ?? ???Resetting default scopeLAST_CONTROL_TRANSFER: from 82c46aa8 to 82c93879STACK_TEXT:833867c8 82c46aa8 00000001 9291b484 00000000 nt!MmAccessFault+0x104833867c8 9293ceac 00000001 9291b484 00000000 nt!KiTrap0E+0xdcWARNING: Stack unwind information not available. Following frames may be wrong.83386850 9282e21f 92852fac 00021980 8301c700 aswSP+0x57eac83386878 928832d0 82c349ce 00000000 00000000 aswSnx+0xd21f833868a4 9291bb48 003fc408 00000000 00000000 aswSnx+0x622d0833868d4 9291bd04 00000001 00000000 00000018 aswSP+0x36b4883386904 928ed301 00000001 9293df64 864f2d68 aswSP+0x36d04833869a0 9290f4be 864f2d68 864f9000 864f9000 aswSP+0x8301833869b8 82dc93b2 864f2d68 864f9000 8c103690 aswSP+0x2a4be83386b9c 82fb850e 00000001 00000000 83386bd4 nt!IopLoadDriver+0x7ed83386be8 82fb81b1 00000007 8080aea0 00000000 nt!IopInitializeSystemDrivers+0x16383386c6c 82fbc1fa 0080aea0 855710b8 85571d48 nt!IoInitSystem+0x6de83386d48 82d924d7 83386d90 82e0f141 8080aea0 nt!Phase1InitializationDiscard+0xcf783386d50 82e0f141 8080aea0 aaed645b 00000000 nt!Phase1Initialization+0xd83386d90 82cb6559 82d924ca 8080aea0 00000000 nt!PspSystemThreadStartup+0x9e00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19STACK_COMMAND: kbFOLLOWUP_IP:aswSP+57eac9293ceac ?? ???SYMBOL_STACK_INDEX: 2SYMBOL_NAME: aswSP+57eacFOLLOWUP_NAME: MachineOwnerMODULE_NAME: aswSPIMAGE_NAME: aswSP.sysDEBUG_FLR_IMAGE_TIMESTAMP: 53b44364FAILURE_BUCKET_ID: 0xBE_aswSP+57eacBUCKET_ID: 0xBE_aswSP+57eacFollowup: MachineOwner--------- Link do komentarza Udostępnij na innych stronach More sharing options...
Nairdak Napisano Listopad 22, 2014 Zgłoś Share Napisano Listopad 22, 2014 Skoro sprzęt uruchamia się w trybie awaryjnym, to radzę spróbować skorzystać z przywracania systemu i cofnąć stan do dnia sprzed awarii. Wielce prawdopodobne, że system sam utworzył punkt kontrolny. Link do komentarza Udostępnij na innych stronach More sharing options...
adik0011 Napisano Listopad 22, 2014 Autor Zgłoś Share Napisano Listopad 22, 2014 W przywracaniu systemu niema żadnego punktu przywracania. Link do komentarza Udostępnij na innych stronach More sharing options...