ntoskrnl.exe and ntkrnlmp.exe after windows update(new build)

dlb · 03 Jun 2011

hi all, dave here. i am having nothing but bad luck with this build. it originall went out at xmas time. since then i have reimaged it twice. this is the 3rd time. when i get it back, i can't even repair windows with the recovery disk i made. i have stripped it down to the bare essentials to run. i installed a new hdd, reinstalled windows and updated until it would update no more. i had prev. replaced power supply, rma-ed the ram. i ran prime 95 for 20+ hours with no faults. i reloaded most of the software i orig. found on the computer, and ran it again for 24 hrs. no faults. i updated once more, this time installing windows suggested drivers.
All hell broke loose. comp wouldn't boot. wouldn't post properly for the 1st 3 attempts, then started. it wanted to do a startup repair. i let it do that. it took over 10mins to get to a desktop. oh oh, i said to my self.
i have whocrashed loaded on already so i ran that. it reported the 2 errors i mentioned in the title, ntoskrnl.exe and ntkrnlmp.exe. made a reference to the athros ethernet adapter. i rolled back the driver and rebooted.
i thought i was in the clear until it bsod-ed on me while i was readin the dump files.
i m pretty frustrated at the moment and looking for some assistance please.

mgorman87 · 03 Jun 2011

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

A known BSOD maker in Windows 7. The 2005 version of this driver is known to cause BSOD on Windows 7 systems.
Download the ATK0110 utility from here - ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE.
After you install it browse to C:\windows\system32\drivers and check the properties of ASACPI.sys and make sure it now says 2009.

Code:

L1E62x64.sys Thu Jun 11 02:45:22 2009 (4A30A802)

Update your Atheros driver - Atheros Communications

Run a system file check - SFC /SCANNOW Command - System File Checker

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests (Small FFTs, Large FFTs, Blend) for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan using SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jun  3 12:47:44.912 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:02.068
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4621f )
BUGCHECK_STR:  0x50
PROCESS_NAME:  lsass.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+4621f
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun  2 19:43:30.977 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:40.132
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BiosReleaseDate = 08/20/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

dlb · 03 Jun 2011

thankyou mgorman87 for your wildly fast reply. i have performed the recommended changes. i am at the 4th pass of memtest. i am pretty sure it will mow down these tests. it has done so already. as for checking the seagate, it is a known good tester. i am doing low level format and zero write to the orig. tbyte hdd. i will clone with clonezilla back to the wdd tbyte hdd if all goes well. what are your thoughts on reinstalling the motherboard software from asus. i really have no use for expressgate, but some of the other utilties look interesting. i have intentionally stayed away from them at this point. the only other troubling thing i noticed was on boot i had some corrupted charactors on the bios screen. as a precaution, i have started a possible rma for the motherboad. thankyou.
dave.

dlb · 04 Jun 2011

hi all. this rig ran 8 passes of memtest last night. was getting late so i shut it down. it will not post now. motherboard is going to be rma-ed, asus sent me a rma numer. i'm not 100% that the motherboard is at fault, but i think strongly that it might be. if the memory controller was on the motherboard i think i would be more convinced. i will keep you posted, and pick up where we left off when the new board arrives. thanks everyone.