Hi ,
i just installed windows 7 in my dad's old netbook asus 1015CX reason installing win 7 is cause lack driver support for windows 8 and after some 500 mb update it crashing randomly with random errors as well as random up time so weird i checked build it is RTM comparing to my desktop that have GDR i think that is why
All of your dump files are the same.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, c080206c, ffff, 0} Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a ) Followup: MachineOwnerPlease fill out your System Specs
InformationYour System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs
Please Run Memtest86+
InformationPlease download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask
After giving it 6 hour rest i tried to install last update again that is IE 11 From ie 8All of your dump files are the same.
it crashed first time when i started after 2nd time i started and going to safe boot with cmd and running sfc /scannow ( no integrity found )
it now running from 30 min without bsod however updater taking too long for installing ie 11
so i looked to mindumps with bluescreenview all are the sames excluding some
there is IRQL not less not equal
after sorting dumps i finally collected 4 dumps and also the latest 1 that i just told you
i also installed win debugger in system and did run analysis with it of this 4 dump below
another thing i need to tell that is i i already installed win 7 in def partition also was using dual boot with win 8.1 from last 15 days no any BSOD th reason beside install again win 7 in new 30 gb partition is cause of i have problem of missing toolbar's on taskbar and any solution did not worked so i go though new installation
SO IT IS NOW Triple BOOT WITH win 7 (1st), win 8.1 (2nd) just installed win 7 that causing BSOD
here is link my taskbar prob that force me to new install
https://www.sevenforums.com/customiza...s-missing.html
IN ORDER OF FIRST IS OLDER AND LAST 1 IS NEWER
Code:Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [O:\Minidump\New folder\083114-23212-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {a6eb4008, 2, 1, 81ac403d} Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+89 ) Followup: MachineOwner --------- 0: 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: a6eb4008, memory referenced Arg2: 00000002, 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: 81ac403d, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81b7d84c Unable to read MiSystemVaType memory at 81b5cf00 a6eb4008 CURRENT_IRQL: 2 FAULTING_IP: nt!MiReleaseConfirmedPageFileSpace+89 81ac403d 2110 and dword ptr [eax],edx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: conhost.exe ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: a5ef5984 -- (.trap 0xffffffffa5ef5984) ErrCode = 00000003 eax=a6eb4008 ebx=00000100 ecx=00000000 edx=fffffffe esi=86d73478 edi=870b4000 eip=81ac403d esp=a5ef59f8 ebp=a5ef5a28 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiReleaseConfirmedPageFileSpace+0x89: 81ac403d 2110 and dword ptr [eax],edx ds:0023:a6eb4008=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 81ac403d to 81a54b7f STACK_TEXT: a5ef5984 81ac403d badb0d00 fffffffe 00000000 nt!KiTrap0E+0x1b3 a5ef5a28 81ab2f9c 00000000 ff000000 873ef220 nt!MiReleaseConfirmedPageFileSpace+0x89 a5ef5b28 81acde3c 00220000 0025ffff bb303435 nt!MiDeleteVirtualAddresses+0x356 a5ef5bc0 81a518c6 ffffffff a5ef5c6c a5ef5c60 nt!NtFreeVirtualMemory+0x60b a5ef5bc0 81a4f84d ffffffff a5ef5c6c a5ef5c60 nt!KiSystemServicePostCall a5ef5c48 81c1c86a ffffffff a5ef5c6c a5ef5c60 nt!ZwFreeVirtualMemory+0x11 a5ef5c64 81c7d952 00220000 bb303329 8615bfc8 nt!RtlFreeUserStack+0x1e a5ef5cdc 81c632e4 00000000 00000000 8615bd48 nt!PspExitThread+0x530 a5ef5cfc 81c8d74f 8615bd48 00000000 00000001 nt!PspTerminateThreadByPointer+0x61 a5ef5d24 81a518c6 00000000 00000000 0025f89c nt!NtTerminateThread+0x74 a5ef5d24 778970f4 00000000 00000000 0025f89c nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 0025f89c 00000000 00000000 00000000 00000000 0x778970f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiReleaseConfirmedPageFileSpace+89 81ac403d 2110 and dword ptr [eax],edx SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiReleaseConfirmedPageFileSpace+89 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0xA_nt!MiReleaseConfirmedPageFileSpace+89 BUCKET_ID: 0xA_nt!MiReleaseConfirmedPageFileSpace+89 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xa_nt!mireleaseconfirmedpagefilespace+89 FAILURE_ID_HASH: {923f4f61-3621-69f5-a3d6-6751908a8e36} Followup: MachineOwner ---------Code:Loading Dump File [O:\Minidump\New folder\083114-26769-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {c08a5, 0, 0, 0} Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+138 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 000c08a5 Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x24 PROCESS_NAME: conhost.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre LAST_CONTROL_TRANSFER: from 88246c76 to 81ae6bfc STACK_TEXT: a007fa30 88246c76 00000024 000c08a5 00000000 nt!KeBugCheckEx+0x1e a007faec 88245c39 00001000 86112900 2820f0a2 Ntfs!NtfsPagingFileIo+0x138 a007fb5c 81a3ec1e 85fba020 84711b40 84711b40 Ntfs!NtfsFsdRead+0xac a007fb74 8816c20c 85fb7258 84711b40 00000000 nt!IofCallDriver+0x63 a007fb98 8816c3cb a007fbb8 85fb7258 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa a007fbd0 81a3ec1e 85fb7258 84711b40 84711b40 fltmgr!FltpDispatch+0xc5 a007fbe8 81acce66 8753fb48 876946c8 8753fb18 nt!IofCallDriver+0x63 a007fc04 81aae940 860fe420 876946c8 8753fb50 nt!IoPageRead+0x1f5 a007fc9c 81a98350 85ec25f8 00258ff8 8753fb19 nt!MiIssueHardFault+0x28c a007fd1c 81a48aa8 00000001 00258ff8 00000001 nt!MmAccessFault+0x2bcc a007fd1c 776eefd9 00000001 00258ff8 00000001 nt!KiTrap0E+0xdc WARNING: Frame IP not in any known module. Following frames may be wrong. 0007ee44 00000000 00000000 00000000 00000000 0x776eefd9 STACK_COMMAND: kb FOLLOWUP_IP: Ntfs!NtfsPagingFileIo+138 88246c76 0fbe8728010000 movsx eax,byte ptr [edi+128h] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: Ntfs!NtfsPagingFileIo+138 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 52e1bb56 IMAGE_VERSION: 6.1.7601.18378 FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsPagingFileIo+138 BUCKET_ID: 0x24_Ntfs!NtfsPagingFileIo+138 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x24_ntfs!ntfspagingfileio+138 FAILURE_ID_HASH: {94fb501b-da6f-9ab4-e0bf-5a1a788da571} Followup: MachineOwner ---------Code:Loading Dump File [O:\Minidump\New folder\083114-31231-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, c0802058, ffff, 0} Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+41a ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 00041790, A page table page has been corrupted. On a 64 bit OS, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit OS, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs. Arg2: c0802058 Arg3: 0000ffff Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: TrustedInstall CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre LAST_CONTROL_TRANSFER: from 81aa4632 to 81aa4060 STACK_TEXT: a7d8e960 81aa4632 00f30002 0125efff 83ea2030 nt!MiDeleteVirtualAddresses+0x41a a7d8ea30 81aa42e7 83ea2030 a18416f0 83f6cbe0 nt!MiRemoveMappedView+0x325 a7d8ea58 81c4c506 83f6cbe0 00000000 83f91420 nt!MiRemoveVadAndView+0xe5 a7d8eabc 81c7b97a 83ea2030 00f30000 00000000 nt!MiUnmapViewOfSection+0x265 a7d8ead0 81c80a6d 83ea2030 00f30000 a73f84c8 nt!MmUnmapViewOfSection+0x12 a7d8eb14 81c7b99f a73f84e0 a73f84e0 83f91424 nt!AlpcpViewDestroyProcedure+0x184 a7d8eb24 81c7ef91 83f9141c 83f91370 83f9141c nt!AlpcpDestroyBlob+0x1c a7d8eb40 81c7e7fd 83ab14a0 83f91370 00000001 nt!AlpcpFlushResourcesPort+0xea a7d8eb50 81c6525b 83f91358 83f6cbe0 a7d8ebac nt!AlpcpDoPortCleanup+0x8a a7d8eb60 81c2911f 83ea2030 83f91370 00000001 nt!AlpcpClosePort+0x3b a7d8ebac 81c4a54c 83ea2030 a9144328 83f6cbe0 nt!ObpDecrementHandleCount+0x139 a7d8ebf0 81c78f3e a90f8068 a9144328 83ea2030 nt!ObpCloseHandleTableEntry+0x203 a7d8ec20 81c61371 a90f8068 a7d8ec34 a91b9710 nt!ExSweepHandleTable+0x5f a7d8ec40 81c6e9fd b8c589cd 83f6cbe0 000000ff nt!ObKillProcess+0x54 a7d8ecb4 81c823f7 000000ff 83ed0d08 00000001 nt!PspExitThread+0x5db a7d8eccc 81ab5c00 83ed0d08 a7d8ecf8 a7d8ed04 nt!PsExitSpecialApc+0x22 a7d8ed1c 81a42980 00000001 00000000 a7d8ed34 nt!KiDeliverApc+0x28b a7d8ed1c 76f770f4 00000001 00000000 a7d8ed34 nt!KiServiceExit+0x64 WARNING: Frame IP not in any known module. Following frames may be wrong. 005ae67c 00000000 00000000 00000000 00000000 0x76f770f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiDeleteVirtualAddresses+41a 81aa4060 cc int 3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiDeleteVirtualAddresses+41a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0x1a_41790_nt!MiDeleteVirtualAddresses+41a BUCKET_ID: 0x1a_41790_nt!MiDeleteVirtualAddresses+41a ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x1a_41790_nt!mideletevirtualaddresses+41a FAILURE_ID_HASH: {74f59fbc-68cc-18a4-f2dd-4d332b50b356} Followup: MachineOwner ---------
Latest one
Update of ie gone successful no sing of BSOD again will keep you updated :)
Specs
Asus Product pageCode:Summary Operating System Windows 7 Ultimate 32-bit SP1 CPU Intel Atom N2600 @ 1.60GHz 62 °C Cedarview 32nm Technology RAM 2.00GB Motherboard ASUSTeK COMPUTER INC. 1015CX (CPU 1) 27 °C Graphics HSD100IFW4A (1024x600@60Hz) Intel Graphics Media Accelerator 3600 Series (ASUStek Computer Inc) Storage 298GB Western Digital WDC WD3200BPVT-80JJ5T0 (SATA) 41 °C 931GB TOSHIBA External USB 3.0 USB Device (USB (SATA)) 34 °C 7GB Sony Storage Media USB Device (USB) Optical Drives No optical disk drives detected Audio High Definition Audio Device
Notebooks & Ultrabooks - Eee PC 1015CX - ASUS
Code:Loading Dump File [O:\Minidump\New folder\083114-45209-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck BE, {93b02008, 6fc88101, a3147a04, a} Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 93b02008, Virtual address for the attempted write. Arg2: 6fc88101, PTE contents. Arg3: a3147a04, (reserved) Arg4: 0000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: a3147a04 -- (.trap 0xffffffffa3147a04) ErrCode = 00000003 eax=93b02008 ebx=00000100 ecx=00000000 edx=fffffffe esi=86d300b0 edi=86f02000 eip=81b0103d esp=a3147a78 ebp=a3147aa8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiReleaseConfirmedPageFileSpace+0x89: 81b0103d 2110 and dword ptr [eax],edx ds:0023:93b02008=00001000 Resetting default scope LAST_CONTROL_TRANSFER: from 81a91aa8 to 81ade879 STACK_TEXT: a31479ec 81a91aa8 00000001 93b02008 00000000 nt!MmAccessFault+0x104 a31479ec 81b0103d 00000001 93b02008 00000000 nt!KiTrap0E+0xdc a3147aa8 81aeff9c 00000000 66000000 68195fff nt!MiReleaseConfirmedPageFileSpace+0x89 a3147ba8 81af0632 66e40002 68195fff 874b76a8 nt!MiDeleteVirtualAddresses+0x356 a3147c78 81af02e7 874b76a8 8724c760 876c4368 nt!MiRemoveMappedView+0x325 a3147ca0 81c98506 876c4368 00000000 ffffffff nt!MiRemoveVadAndView+0xe5 a3147d04 81cb6a1f 874b76a8 66e40000 00000000 nt!MiUnmapViewOfSection+0x265 a3147d24 81a8e8c6 ffffffff 66e40000 036aebe0 nt!NtUnmapViewOfSection+0x55 a3147d24 778870f4 ffffffff 66e40000 036aebe0 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 036aebe0 00000000 00000000 00000000 00000000 0x778870f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+dc 81a91aa8 85c0 test eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTrap0E+dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 FAILURE_BUCKET_ID: 0xBE_nt!KiTrap0E+dc BUCKET_ID: 0xBE_nt!KiTrap0E+dc ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xbe_nt!kitrap0e+dc FAILURE_ID_HASH: {9526f5c2-9c1b-c6b9-1949-a4d935a6ed15} Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 93b02008, Virtual address for the attempted write. Arg2: 6fc88101, PTE contents. Arg3: a3147a04, (reserved) Arg4: 0000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: a3147a04 -- (.trap 0xffffffffa3147a04) ErrCode = 00000003 eax=93b02008 ebx=00000100 ecx=00000000 edx=fffffffe esi=86d300b0 edi=86f02000 eip=81b0103d esp=a3147a78 ebp=a3147aa8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiReleaseConfirmedPageFileSpace+0x89: 81b0103d 2110 and dword ptr [eax],edx ds:0023:93b02008=00001000 Resetting default scope LAST_CONTROL_TRANSFER: from 81a91aa8 to 81ade879 STACK_TEXT: a31479ec 81a91aa8 00000001 93b02008 00000000 nt!MmAccessFault+0x104 a31479ec 81b0103d 00000001 93b02008 00000000 nt!KiTrap0E+0xdc a3147aa8 81aeff9c 00000000 66000000 68195fff nt!MiReleaseConfirmedPageFileSpace+0x89 a3147ba8 81af0632 66e40002 68195fff 874b76a8 nt!MiDeleteVirtualAddresses+0x356 a3147c78 81af02e7 874b76a8 8724c760 876c4368 nt!MiRemoveMappedView+0x325 a3147ca0 81c98506 876c4368 00000000 ffffffff nt!MiRemoveVadAndView+0xe5 a3147d04 81cb6a1f 874b76a8 66e40000 00000000 nt!MiUnmapViewOfSection+0x265 a3147d24 81a8e8c6 ffffffff 66e40000 036aebe0 nt!NtUnmapViewOfSection+0x55 a3147d24 778870f4 ffffffff 66e40000 036aebe0 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 036aebe0 00000000 00000000 00000000 00000000 0x778870f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+dc 81a91aa8 85c0 test eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTrap0E+dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 FAILURE_BUCKET_ID: 0xBE_nt!KiTrap0E+dc BUCKET_ID: 0xBE_nt!KiTrap0E+dc ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xbe_nt!kitrap0e+dc FAILURE_ID_HASH: {9526f5c2-9c1b-c6b9-1949-a4d935a6ed15} Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 93b02008, Virtual address for the attempted write. Arg2: 6fc88101, PTE contents. Arg3: a3147a04, (reserved) Arg4: 0000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: a3147a04 -- (.trap 0xffffffffa3147a04) ErrCode = 00000003 eax=93b02008 ebx=00000100 ecx=00000000 edx=fffffffe esi=86d300b0 edi=86f02000 eip=81b0103d esp=a3147a78 ebp=a3147aa8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiReleaseConfirmedPageFileSpace+0x89: 81b0103d 2110 and dword ptr [eax],edx ds:0023:93b02008=00001000 Resetting default scope LAST_CONTROL_TRANSFER: from 81a91aa8 to 81ade879 STACK_TEXT: a31479ec 81a91aa8 00000001 93b02008 00000000 nt!MmAccessFault+0x104 a31479ec 81b0103d 00000001 93b02008 00000000 nt!KiTrap0E+0xdc a3147aa8 81aeff9c 00000000 66000000 68195fff nt!MiReleaseConfirmedPageFileSpace+0x89 a3147ba8 81af0632 66e40002 68195fff 874b76a8 nt!MiDeleteVirtualAddresses+0x356 a3147c78 81af02e7 874b76a8 8724c760 876c4368 nt!MiRemoveMappedView+0x325 a3147ca0 81c98506 876c4368 00000000 ffffffff nt!MiRemoveVadAndView+0xe5 a3147d04 81cb6a1f 874b76a8 66e40000 00000000 nt!MiUnmapViewOfSection+0x265 a3147d24 81a8e8c6 ffffffff 66e40000 036aebe0 nt!NtUnmapViewOfSection+0x55 a3147d24 778870f4 ffffffff 66e40000 036aebe0 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 036aebe0 00000000 00000000 00000000 00000000 0x778870f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+dc 81a91aa8 85c0 test eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTrap0E+dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 FAILURE_BUCKET_ID: 0xBE_nt!KiTrap0E+dc BUCKET_ID: 0xBE_nt!KiTrap0E+dc ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xbe_nt!kitrap0e+dc FAILURE_ID_HASH: {9526f5c2-9c1b-c6b9-1949-a4d935a6ed15} Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 93b02008, Virtual address for the attempted write. Arg2: 6fc88101, PTE contents. Arg3: a3147a04, (reserved) Arg4: 0000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: a3147a04 -- (.trap 0xffffffffa3147a04) ErrCode = 00000003 eax=93b02008 ebx=00000100 ecx=00000000 edx=fffffffe esi=86d300b0 edi=86f02000 eip=81b0103d esp=a3147a78 ebp=a3147aa8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiReleaseConfirmedPageFileSpace+0x89: 81b0103d 2110 and dword ptr [eax],edx ds:0023:93b02008=00001000 Resetting default scope LAST_CONTROL_TRANSFER: from 81a91aa8 to 81ade879 STACK_TEXT: a31479ec 81a91aa8 00000001 93b02008 00000000 nt!MmAccessFault+0x104 a31479ec 81b0103d 00000001 93b02008 00000000 nt!KiTrap0E+0xdc a3147aa8 81aeff9c 00000000 66000000 68195fff nt!MiReleaseConfirmedPageFileSpace+0x89 a3147ba8 81af0632 66e40002 68195fff 874b76a8 nt!MiDeleteVirtualAddresses+0x356 a3147c78 81af02e7 874b76a8 8724c760 876c4368 nt!MiRemoveMappedView+0x325 a3147ca0 81c98506 876c4368 00000000 ffffffff nt!MiRemoveVadAndView+0xe5 a3147d04 81cb6a1f 874b76a8 66e40000 00000000 nt!MiUnmapViewOfSection+0x265 a3147d24 81a8e8c6 ffffffff 66e40000 036aebe0 nt!NtUnmapViewOfSection+0x55 a3147d24 778870f4 ffffffff 66e40000 036aebe0 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 036aebe0 00000000 00000000 00000000 00000000 0x778870f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+dc 81a91aa8 85c0 test eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTrap0E+dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 FAILURE_BUCKET_ID: 0xBE_nt!KiTrap0E+dc BUCKET_ID: 0xBE_nt!KiTrap0E+dc ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xbe_nt!kitrap0e+dc FAILURE_ID_HASH: {9526f5c2-9c1b-c6b9-1949-a4d935a6ed15} Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 93b02008, Virtual address for the attempted write. Arg2: 6fc88101, PTE contents. Arg3: a3147a04, (reserved) Arg4: 0000000a, (reserved) Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xBE PROCESS_NAME: explorer.exe CURRENT_IRQL: 2 ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre TRAP_FRAME: a3147a04 -- (.trap 0xffffffffa3147a04) ErrCode = 00000003 eax=93b02008 ebx=00000100 ecx=00000000 edx=fffffffe esi=86d300b0 edi=86f02000 eip=81b0103d esp=a3147a78 ebp=a3147aa8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!MiReleaseConfirmedPageFileSpace+0x89: 81b0103d 2110 and dword ptr [eax],edx ds:0023:93b02008=00001000 Resetting default scope LAST_CONTROL_TRANSFER: from 81a91aa8 to 81ade879 STACK_TEXT: a31479ec 81a91aa8 00000001 93b02008 00000000 nt!MmAccessFault+0x104 a31479ec 81b0103d 00000001 93b02008 00000000 nt!KiTrap0E+0xdc a3147aa8 81aeff9c 00000000 66000000 68195fff nt!MiReleaseConfirmedPageFileSpace+0x89 a3147ba8 81af0632 66e40002 68195fff 874b76a8 nt!MiDeleteVirtualAddresses+0x356 a3147c78 81af02e7 874b76a8 8724c760 876c4368 nt!MiRemoveMappedView+0x325 a3147ca0 81c98506 876c4368 00000000 ffffffff nt!MiRemoveVadAndView+0xe5 a3147d04 81cb6a1f 874b76a8 66e40000 00000000 nt!MiUnmapViewOfSection+0x265 a3147d24 81a8e8c6 ffffffff 66e40000 036aebe0 nt!NtUnmapViewOfSection+0x55 a3147d24 778870f4 ffffffff 66e40000 036aebe0 nt!KiSystemServicePostCall WARNING: Frame IP not in any known module. Following frames may be wrong. 036aebe0 00000000 00000000 00000000 00000000 0x778870f4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+dc 81a91aa8 85c0 test eax,eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTrap0E+dc FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f IMAGE_VERSION: 6.1.7601.18409 FAILURE_BUCKET_ID: 0xBE_nt!KiTrap0E+dc BUCKET_ID: 0xBE_nt!KiTrap0E+dc ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0xbe_nt!kitrap0e+dc FAILURE_ID_HASH: {9526f5c2-9c1b-c6b9-1949-a4d935a6ed15} Followup: MachineOwner ---------
Almost every dump file lists memory corruption, page file corruption or NTFS corruption. All of those are related to the same thing. Have you done anything to the default system configuration, such as change the default page file size or any of the system protection settings? I would suggest you run Check disk Disk Check, run the Manufacturer's diagnostic program on each of your hard drives, and I asked before for you to run memtest86+ and I don't see where you said you ran it. Also:
Please fill out your System Specs
InformationYour System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs
Open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Please fill out your System Specs
as this is not my laptop that is why i am not filling out system specs however i attached full spec my speccy if you noticed
and now system is running stable from last 3 hrs no BSOD smooth antivirus installation
what i did was ran sfc /scannow 1 time that i already told and
yes i did not ran memtest86+ BUT i ran windows diagnostic memory test from bootmngr screen with 2 PASS
i think prob is not in memory and hard drive that is it self OS because as i told other win 7 and win 8.1 working without any BSOD from last 15 days
and also did not modified any setting more then notification bar setting and SP1 and other updates
now i will going to install necessary softs that my dad need and will run lappy for whole night for stability check also will update some drivers with DRIVER BOOSTER if everything will go fine i will update
Update drivers from the manufacturer's web site. Do not use any driver finder of any kind. Windows memory diagnostic function is not real good. You can do whatever you want. I can only make suggestions. It is up to you whether to follow them.
No bsod till this date thanks bro for helping out
Quote