IRQL_NOT_LESS_OR_EQUAL / PAGE_FAULT_IN_NONPAGED_AREA
Hiya, I recently installed W7 on my GF's computer replacing both the CPU, HDD and Ram. Prior to this we were having alot of BSOD similar to the one's mentioned in the title that kept causing the computer to crash. The asumption at the time was this was related to either bad HDD or bad memory. However since install W7 64x on a fresh HDD these are now slowly cropping up. The first time the BSOD had happened was fairly early into setting up the computer again, At this point I was copying the nvidia driver install file from my USB stick onto the desktop ready to install the latest drivers. At this point I hadn't even installed the latest Soundcard drivers etc from the motherboard's website. I am not 100% sure what is causing this but currently all drivers are now up to the latest versions and as much is not plugged in or installed as possible to try and narrow down the issue. I've got 2 dump files (link to skydrive folder at bottom) which aren't very clear to me and I don't seem to be able to use the developer tool kit to read them or understand them as its asking for a MSDN subscription. At this point we aren't 100% sure what the best course of action is. Could this potentially be a hardware issue with the motherboard or graphics card now? I've run memtest and had no issues and the CPU, while 2nd hand and confirmed working, I ran a Prime95 and Intelburntest on it to make sure it was all comfortable. I will, now try to update the Mobo's bios to see if that has any affect, but this system was running XP without any issue for about 2 years without any issue and my GF didn't install any new specific drivers that suddenly prompted these BSOD of occur, hence our thought it might be a piece of HDD that has become faulty. Especially after this fresh install of Windows 7 seems to be prompting similar issues. Any help on the matter would be greatly appreciated. Thanks (Skydrive folder with x2 recent dump files) https://skydrive.live.com/redir.aspx?cid=337e3d0f43f146cf&resid=337E3D0F43F146CF!111&parid=337E3D0F43F146CF!109
February 19th, 2012 6:50pm

If you were having the problem with the previous operating system and your are still having the problems after installing windows 7, logic would tell you there is something wrong with your hardware! If you replaced the CPU, the HDD, and the DRAM, and your are still having problem, the LOGIC would indocate you have a defective MOTHERBOARD and Windows 7 cannot compensate for defective hardware!!! If might be the video card, too. However, this is STRICTLY a HARDWARE PROBLEM! It is not a Windows 7 problem!!!Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2012 9:51pm

1. For viewing dump file you can use viewer from Nirsoft, if the WinDbg too complex. 2. The first error points to fltmgr.sys and stop error 0x00000050. This is described in knowledge base here http://support.microsoft.com/kb/979538 , there should be hotfix. 3. When I install vanilla plain Windows operating system and there are problems like yours, I test as much componets, as I can. Memtest and hdd vendor's test tools are primary. I ran memtest as long as possible. There are more aggressive tests. You can fiddle with voltages in BIOS keepeng in mind RAM limits. Also the cycle parameters may play the role, namely if the chips are not identical ones. 4. First item after new install, that I add to system immediatelly is chipset driver, then video card driver and other components follows. If the motherboard is older, chances are that the install medium have appropriate drives included. 5. You have not mentioned the components vendors. You will not do mistake, if you address vendor's forum(s) and/or support. 6. If the motherboard is older, chances are, that some capacitors are faulty. Visual inspection may reveal "fat" capacitors. Regards Milos
February 19th, 2012 10:10pm

******************************************************************************* * * * 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: fffffa85456b95b0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002b11799, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d14100 fffffa85456b95b0 FAULTING_IP: nt!MiWaitForInPageComplete+89d fffff800`02b11799 488b4cc530 mov rcx,qword ptr [rbp+rax*8+30h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800adcc3d0 -- (.trap 0xfffff8800adcc3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000a8004b74 rbx=0000000000000000 rcx=0000000000000001 rdx=000fffffa8004b74 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002b11799 rsp=fffff8800adcc560 rbp=fffffa80056939e0 r8=fffffa8004b747d0 r9=0000000000000000 r10=fffffa8005693920 r11=00000000000007d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!MiWaitForInPageComplete+0x89d: fffff800`02b11799 488b4cc530 mov rcx,qword ptr [rbp+rax*8+30h] ss:0018:fffffa85`456b95b0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a8c3bf to fffff80002ae1c40 STACK_TEXT: fffff880`0adcc268 fffff800`02a8c3bf : 00000000`00000050 fffffa85`456b95b0 00000000`00000000 fffff880`0adcc3d0 : nt!KeBugCheckEx fffff880`0adcc270 fffff800`02adfd6e : 00000000`00000000 fffffa85`456b95b0 fffff880`0adcc400 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791 fffff880`0adcc3d0 fffff800`02b11799 : 00000000`00000000 fffffa80`00000009 fffffa80`05693900 fffffa80`05693900 : nt!KiPageFault+0x16e fffff880`0adcc560 fffff800`02ad0cd3 : fffffa80`05693920 00000000`00000000 00000000`00000000 00000000`000001c0 : nt!MiWaitForInPageComplete+0x89d fffff880`0adcc640 fffff800`02dcbe10 : 00000000`00000000 00000000`001c0000 fffffa80`060bfb50 00000000`057dc110 : nt!CcFetchDataForRead+0x1c3 fffff880`0adcc6a0 fffff880`012e4f08 : fffff880`00000000 00000000`00000001 fffffa80`00040000 fffffa80`00004001 : nt!CcCopyRead+0x180 fffff880`0adcc760 fffff880`010ab098 : fffffa80`060bfb50 fffffa80`06050768 fffffa80`04fd4920 fffffa80`060bfb01 : Ntfs!NtfsCopyReadA+0x1a8 fffff880`0adcc940 fffff880`010ae8ba : fffff880`0adcca10 00000000`057dc103 00000000`057dc100 fffffa80`060bfb00 : fltmgr!FltpPerformFastIoCall+0x88 fffff880`0adcc9a0 fffff880`010cc630 : fffffa80`060bfb50 00000000`00000000 fffff880`0adccb00 00000000`00004000 : fltmgr!FltpPassThroughFastIo+0xda fffff880`0adcc9e0 fffff800`02dcb949 : fffffa80`060bfb50 fffffa80`00000001 fffffa80`039f7de0 fffffa80`060bfb50 : fltmgr!FltpFastIoRead+0x1d0 fffff880`0adcca80 fffff800`02ae0ed3 : 00000000`000007fc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417 fffff880`0adccb70 00000000`77ac137a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`03ebe3a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac137a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiWaitForInPageComplete+89d fffff800`02b11799 488b4cc530 mov rcx,qword ptr [rbp+rax*8+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiWaitForInPageComplete+89d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiWaitForInPageComplete+89d BUCKET_ID: X64_0x50_nt!MiWaitForInPageComplete+89d Followup: MachineOwner --------- ------------------------------------------------------- Bug Check Code 0x50: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx Please start by that: Uninstall all unused programsUpdate all possible driversDisable all security softwares you haveRun memtest86+ to check if all is okay with RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical SupportRun chkdsk /r /f and check your HDD cablesRun msconfig and disable all startup items / services except Microsoft ones Once done, check results. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2012 10:54am

Hiya, All drivers where up to date as I'd pulled them of the various manufacturers websites when I installed windwos 7 onto the machine. I realise that just installing Win 7 wouldn't fix a hardware issue. But coupled with new Ram, CPU and a new HDD, then installing the latest up to date drivers on a fresh install of windows, should at least rule out (in theory) possible driver issues. I ran memtest again but like previously it went fine. as with chkdsk. We had a new BSOD error message come up that said. DRIVER_CORRUPTED_MMPOOL This popped up when the computer was just idleing and no one was using it. I wondered if it was possible that it might be the motherboard that is dieing, I say this as a few crashes have been forced to happen when copying data around, mainly from USB sticks. Could that mean there are issues with the mobo's southbridge? We're still at a loss here. I've had the computer running now since that error both with only MSServices running, and then running for a few hours with no issue with just the drivers for the mouse/keyboard/realtek soundcard installed and the HP Printer unplugged. Sadly there is no way to force a BSOD so we can't really test if things have been improved or not until we potentially see another one appear.
February 20th, 2012 9:42pm

I've just had a quick look for potential 'bad' drivers in one of the dumps. The following are what I would concentrate on, they're listed from oldest at the top. Update, uninstall or disable all of them to test, Use MSE instead of AVG, the most likely offenders imo are underlined if you want to try those first: Lycosa.sys Razer Tarantula Keyboard Driver http://www.razersupport.com amdiox64.sys AMD IO Driver Uncertain if currently used/needed, if so: http://support.amd.com/us/Pages/AMDSupportHub.aspx If not, rename to amdiox64.BAK and see if that fixes the problem. SCDEmu.SYS PowerISO Virtual Drive driver http://www.poweriso.com/download.htm WmVirHid.sys Logitech WingMan Virtual Hid Device Driver http://www.logitech.com/index.cfm/support_downloads/downloads/ SmartDefragDriver.sys Smart Defrag http://www.iobit.com/iobitsmartdefrag.html asmtxhci.sys Asmedia USB 3.0 driver http://www.asmedia.com.tw/eng/e_products_list.php?item=83&cate_index=0 speedfan.sys SpeedFan http://www.almico.com/sfdownload.php AODDriver2.sys AMD Overdrive; also in EasyTune6 for Gigabyte motherboard http://game.amd.com/us-en/drivers_overdrive.aspx AVGIDSDriver.sys AVG http://www.avg.com/us-en/downloads ================================================ The USB3 can be disabled from the BIOS if you don't use them. Also ensure that you are not overclocking. If you have a new dump, please upload it. Thanks to Carrona.org and Sysnative for creating the database the above details are lifted from.
Free Windows Admin Tool Kit Click here and download it now
February 20th, 2012 10:53pm

Your Memory is bad.I had the same problem and also the problem is that systems tells you sometimes the memory has changed its size. I replaced mine and it is working as before. Hope that i was helpfull.
February 20th, 2012 11:41pm

I've just had a quick look for potential 'bad' drivers in one of the dumps. The following are what I would concentrate on, they're listed from oldest at the top. Update, uninstall or disable all of them to test, Use MSE instead of AVG, the most likely offenders imo are underlined if you want to try those first: Lycosa.sys Razer Tarantula Keyboard Driver http://www.razersupport.com amdiox64.sys AMD IO Driver Uncertain if currently used/needed, if so: http://support.amd.com/us/Pages/AMDSupportHub.aspx If not, rename to amdiox64.BAK and see if that fixes the problem. SCDEmu.SYS PowerISO Virtual Drive driver http://www.poweriso.com/download.htm WmVirHid.sys Logitech WingMan Virtual Hid Device Driver http://www.logitech.com/index.cfm/support_downloads/downloads/ SmartDefragDriver.sys Smart Defrag http://www.iobit.com/iobitsmartdefrag.html asmtxhci.sys Asmedia USB 3.0 driver http://www.asmedia.com.tw/eng/e_products_list.php?item=83&cate_index=0 speedfan.sys SpeedFan http://www.almico.com/sfdownload.php AODDriver2.sys AMD Overdrive; also in EasyTune6 for Gigabyte motherboard http://game.amd.com/us-en/drivers_overdrive.aspx AVGIDSDriver.sys AVG http://www.avg.com/us-en/downloads ================================================ The USB3 can be disabled from the BIOS if you don't use them. Also ensure that you are not overclocking. If you have a new dump, please upload it. Thanks to Carrona.org and Sysnative for creating the database the above details are lifted from. Hiya, I'm really confused where you pulled the information for these bad drivers from? I checked the dump files on the skydrive and I don't see information relating to half those things, for a start the system IS running MSE not AVG, it was one of the things I installed on purpose after telling my GF that I prefered MSE over AVG anyway, so on this current build of Win7, AVG was never installed, and we certainly don't have "Lycosa.sys Razer Tarantula Keyboard Driver" Are these things really both in those 2 dump files from the skydrive I posted for the 18th and 19th of Feb? I'd love to show some more dump files but currently its crashing out totally and just freezing on the BSOD and not actually creating any new ones. The last crash that happened about 20 mins ago only said 0x00000000000001 (might of got number of zero's incorrect. I'm really can't see refence to those drivers in the dump files I uploaded. I realise this of course might be just me not reading these correctly but I'm using BlueScreenViewer to read the dump files, sorry if I'm in the wrong here. I realise this is about Win7 and not so much about hardware issues but I am really happy to say this ram is ok. Its been ran through MemTest now for the best part of 72 hours combined in this system and backup system I ahve at home to make sure it was ok to use in my GF's machine. Sorry for getting worked up about it this is really frustrating and diagnosing this is really annoying. Its not like I can see, oh the graphics card is broken, i'll go replace it. Thanks for all help so far
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2012 1:30am

Well spotted, ignore that post. I see now what happened, your dumps are zipped so don't show with the Open menu, I actually used someone elses that was 1 digit different in the 2nd part of the filename :( I'll take a real look now they're unzipped.
February 21st, 2012 1:46am

It looks like you updated some drivers between crashes, correct? From 2007, update, uninstall or disable: Alpham264.sys Ideazon ZBoard/Ideazon Fang MM USB HID driver http://www.steelseries.com/download =================================================== Older dump@ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {8, 2, 1, fffff800026dc9f2} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcVSyncCookie+464 ) Followup: MachineOwner --------- 2: 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: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff800026dc9f2, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800028fe0e8 0000000000000008 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTryUnwaitThread+182 fffff800`026dc9f2 48894108 mov qword ptr [rcx+8],rax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88002f8b680 -- (.trap 0xfffff88002f8b680) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa800460f610 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8003eae168 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800026dc9f2 rsp=fffff88002f8b810 rbp=fffff88002f63180 r8=0000000000000000 r9=0000000000000000 r10=fffffa8004ee9bd0 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!KiTryUnwaitThread+0x182: fffff800`026dc9f2 48894108 mov qword ptr [rcx+8],rax ds:00000000`00000008=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800026ccbe9 to fffff800026cd640 STACK_TEXT: fffff880`02f8b538 fffff800`026ccbe9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`02f8b540 fffff800`026cb860 : fffffa80`05659000 00000000`00000000 00000000`00000000 fffffa80`03eae060 : nt!KiBugCheckDispatch+0x69 fffff880`02f8b680 fffff800`026dc9f2 : 00000000`00000002 fffffa80`04b21240 00000000`00000019 00000000`fffffffe : nt!KiPageFault+0x260 fffff880`02f8b810 fffff800`02670b2e : fffffa80`05659030 00000000`00000000 fffffa80`05659038 fffffa80`05659038 : nt!KiTryUnwaitThread+0x182 fffff880`02f8b870 fffff880`041732bc : fffffa80`04ee9410 fffffa80`056589a0 fffffa80`03ead010 fffff880`000023db : nt!KePulseEvent+0xde fffff880`02f8b8d0 fffff880`04172ce8 : fffffa80`00000000 fffffa80`00000019 fffffa80`00000001 000047c0`000047bf : dxgmms1!VidSchiProcessDpcVSyncCookie+0x464 fffff880`02f8b990 fffff880`04172c4c : 00000000`00000000 fffffa80`04ee9410 fffffa80`04dd0480 fffffa80`04dd0aa8 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80 fffff880`02f8b9e0 fffff880`040791cf : fffffa80`04dd0480 00000000`00000002 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94 fffff880`02f8ba30 fffff880`0495f39d : 00000000`00000000 fffffa80`04ded000 fffffa80`04dd0480 fffffa80`04ca2000 : dxgkrnl!DxgNotifyDpcCB+0x77 fffff880`02f8ba60 00000000`00000000 : fffffa80`04ded000 fffffa80`04dd0480 fffffa80`04ca2000 fffffa80`04ded000 : nvlddmkm+0x6d39d STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VidSchiProcessDpcVSyncCookie+464 fffff880`041732bc 488d4c2450 lea rcx,[rsp+50h] SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+464 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidSchiProcessDpcVSyncCookie+464 BUCKET_ID: X64_0xA_dxgmms1!VidSchiProcessDpcVSyncCookie+464 Followup: MachineOwner --------- -------------------------------------------------------------------------------------------------------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa85456b95b0, 0, fffff80002b11799, 5} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+89d ) Followup: MachineOwner --------- 2: 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: fffffa85456b95b0, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002b11799, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000005, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d14100 fffffa85456b95b0 FAULTING_IP: nt!MiWaitForInPageComplete+89d fffff800`02b11799 488b4cc530 mov rcx,qword ptr [rbp+rax*8+30h] MM_INTERNAL_CODE: 5 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: MsMpEng.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800adcc3d0 -- (.trap 0xfffff8800adcc3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000a8004b74 rbx=0000000000000000 rcx=0000000000000001 rdx=000fffffa8004b74 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002b11799 rsp=fffff8800adcc560 rbp=fffffa80056939e0 r8=fffffa8004b747d0 r9=0000000000000000 r10=fffffa8005693920 r11=00000000000007d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!MiWaitForInPageComplete+0x89d: fffff800`02b11799 488b4cc530 mov rcx,qword ptr [rbp+rax*8+30h] ss:0018:fffffa85`456b95b0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a8c3bf to fffff80002ae1c40 STACK_TEXT: fffff880`0adcc268 fffff800`02a8c3bf : 00000000`00000050 fffffa85`456b95b0 00000000`00000000 fffff880`0adcc3d0 : nt!KeBugCheckEx fffff880`0adcc270 fffff800`02adfd6e : 00000000`00000000 fffffa85`456b95b0 fffff880`0adcc400 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791 fffff880`0adcc3d0 fffff800`02b11799 : 00000000`00000000 fffffa80`00000009 fffffa80`05693900 fffffa80`05693900 : nt!KiPageFault+0x16e fffff880`0adcc560 fffff800`02ad0cd3 : fffffa80`05693920 00000000`00000000 00000000`00000000 00000000`000001c0 : nt!MiWaitForInPageComplete+0x89d fffff880`0adcc640 fffff800`02dcbe10 : 00000000`00000000 00000000`001c0000 fffffa80`060bfb50 00000000`057dc110 : nt!CcFetchDataForRead+0x1c3 fffff880`0adcc6a0 fffff880`012e4f08 : fffff880`00000000 00000000`00000001 fffffa80`00040000 fffffa80`00004001 : nt!CcCopyRead+0x180 fffff880`0adcc760 fffff880`010ab098 : fffffa80`060bfb50 fffffa80`06050768 fffffa80`04fd4920 fffffa80`060bfb01 : Ntfs!NtfsCopyReadA+0x1a8 fffff880`0adcc940 fffff880`010ae8ba : fffff880`0adcca10 00000000`057dc103 00000000`057dc100 fffffa80`060bfb00 : fltmgr!FltpPerformFastIoCall+0x88 fffff880`0adcc9a0 fffff880`010cc630 : fffffa80`060bfb50 00000000`00000000 fffff880`0adccb00 00000000`00004000 : fltmgr!FltpPassThroughFastIo+0xda fffff880`0adcc9e0 fffff800`02dcb949 : fffffa80`060bfb50 fffffa80`00000001 fffffa80`039f7de0 fffffa80`060bfb50 : fltmgr!FltpFastIoRead+0x1d0 fffff880`0adcca80 fffff800`02ae0ed3 : 00000000`000007fc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417 fffff880`0adccb70 00000000`77ac137a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`03ebe3a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac137a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiWaitForInPageComplete+89d fffff800`02b11799 488b4cc530 mov rcx,qword ptr [rbp+rax*8+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiWaitForInPageComplete+89d FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x50_nt!MiWaitForInPageComplete+89d BUCKET_ID: X64_0x50_nt!MiWaitForInPageComplete+89d Followup: MachineOwner --------- =============================================================================== The fault lay with the nVidia driver for the first dump, those drivers were replaced before the second dump, for which the details aren't obvious. I looked at 2 threads elsewhere that seemed to be similar to the latest dump, both were pointing towards memory being at fault. Please test each RAM stick separately using MemTest86+, you'll find details at Carrona.org. If you're sure it's not memory, work through the other hardware tests here.
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2012 2:17am

Hiya, Yeah, the difference between the Nvidia drivers was me updating the latest ones from the Nvidia website, vs the ones windows 7 installed upon starting the computer for the first time. I'm not sure why the standard ones caused the crash. but ironically at the time of the first crash I was transfering the new Nvidia drivers from my usb stick to her pc to install. Not that that is really related. I've been running verifier and I have updated the Keyboards drivers which appears to have caused the crash for this 3rd dump. 022112-36519-01.zip located : https://skydrive.live.com/?cid=337e3d0f43f146cf&id=337E3D0F43F146CF!111 It just BSOD again but this time it called ndiswan.sys as the culprit stating: The drive Mistakenly Marked part of it's image pagable instead of nonpageable. This seems to be related to the Realtek onboard ethernet adaptor so I updated that from the Realtek website and I have verifier running again. this is getting v frustrating, it seems to be a random BSOD each time :( Oh and I run both stick for 3 hours each on memtest, not long I realise but no faults as before with both sticks
February 21st, 2012 5:40pm

How long are going to screw around with this mess before you finally realize you have a defective motherboard causing your random problems? When you have a system with random faults, it is the hardware causing those random faults. It is not Windows causing the problems! Or do you enjoy beating your head against a brick wall because it feels good when you stop?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2012 6:02pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics