K8NGM2-NBP MemTest Failure

My new K8NGM2-NBP system will not pass MemTest86+ (1.65). So far I have:
1. Tried all combinations of one and two sticks in all slots
2. Set command rate to 2T and relaxed timings from the 3-3-3-8 SPD settings
3. Increased RAM voltage
4. Tried 2 other memory sets (Corsair VS DDR400, PQI Turbo DDR500 - both had run MemTest error-free with this same processor on another board.)
5. Checked all connections, etc.
None of these measures reduced or eliminated the numerous errors in each test. I might be able to ignore the MemTest errors if I wasn't experiencing frequent crashes.
I've run out of ideas to deal with this - can anyone suggest another approach which I may have missed? Thanks.

Thanks for the suggestions. I have been testing every combination of factors. I have tried with cmd at 1T and have tightened timings, per kakarocht's suggestion, to 2.5-3-3-8 (two of the kits boot those timings by default) but no improvement. My sig pretty much reflects everything in this box, but I will update to show BIOS (currently back to 1.0 but 1.1 didn't work either) and PSU info (standard Aria custom w/18A 12V rail).
I've also tried, at Stick's suggestion, 1 stick at a time in each of the mem slots, but unfortunately the result is the same. I did learn that CPU-Z locks my machine if I only have 1 256Mb stick installed. Probably not enough memory left overall after onboard graphics takes its slice.
Thanks to all for your valuable help. I'm hoping that I can make this work right.

Similar Messages

USB trouble on k8NGM2-NBP new build

board: msi k8NGM2-NBP
cpu: amd 3800+
drives: single maxtor ide 80GB
ram: OCZ platinum 2-3-2-5 PC3200 512MB x2 (1GB) (slots 1 &2)
with the DDR voltage raised to 2.65+, detects at 400Mhz
psu: Antec 450 from a Sonata II
I get this board from www.mwave.com and start testing by connecting
components on my tabletop
The first post is OK. I set optimal defaults, reboot, then raise the DDR voltage so
that I see the RAM working at 400 Mhz, instead of 333.
Next I try testing with a bootable CD of memtest86+. I'm able to test without errors through test #4.
By accident I try memory testing with a
bootable USB flash disk. I get errors immediately. I then try the bootable CD again with an
external USB drive connected -- RAM errors again. Now I know that its the USB causing an instability.
So the board is OK as long as I have no USB ports inuse -- .
I don't continue on with the build, the next step being an install of FC5 linux, until I
know if this is an RMA issue or bad bios setting.
please advise and thanks

hello Kakarocht and Built2last,
This board has the nvidia 6150 northbridge with integrated graphics, which I'm using -- no addon video card for this build.
The bios is the latest, at 1.1 -- I checked the site.
I've been advised elsewhere that even with USB RAM errors I should go ahead and install an OS, since the OS can do integrity checks.
I don't agree with this and stand firm that there should never be any RAM errors, with or without USB connections.
I tried connecting to USB on the rear and with the onboard headers -- all gave the same bad results in memtest86.
From reading a few posts here very few posters test RAM in a tabletop build, but usually charge ahead and do their first
build in a case, then test after assembly. I don't do this anymore -- I did for my first few builds.
I'm going ahead with an RMA since I have confirmed that everything but the MB is good. I tested the RAM and CPU elsewhere.
ciao

RAID 5 unavailable in setup for K8NGM2-NBP MB

Hello,
I have purchased K8NGM2-NBP motherboard. It is base on nVidia GeForce 6150B + nForce 430 chipset. I have connected 4 HDDs (SATA WD4000YR). According to the MB specification nVidia raid controller should support RAID 5.
http://www.msicomputer.com/product/p_spec.asp?model=K8NGM2-NBP&class=mb
In BIOS setup I had enabled Serial-ATA1, Serial-ATA2 and nVidia Raid Function. Unfortunate when I enter RAID setup, the only RAID Mode I have are: Mirroring and Striping. According to MB manual I should be able to select RAID 5 right in setup menu.
I tried to find the latest BIOS update for my MB but I cannot find it.
Is there anything that I have to do to enable RAID 5?

Quote from: ptomasze on 02-June-06, 22:28:57
Hello,
I have purchased K8NGM2-NBP motherboard. It is base on nVidia GeForce 6150B + nForce 430 chipset. I have connected 4 HDDs (SATA WD4000YR). According to the MB specification nVidia raid controller should support RAID 5.
http://www.msicomputer.com/product/p_spec.asp?model=K8NGM2-NBP&class=mb
In BIOS setup I had enabled Serial-ATA1, Serial-ATA2 and nVidia Raid Function. Unfortunate when I enter RAID setup, the only RAID Mode I have are: Mirroring and Striping. According to MB manual I should be able to select RAID 5 right in setup menu.
I tried to find the latest BIOS update for my MB but I cannot find it.
Is there anything that I have to do to enable RAID 5?
Your own link states:
On-Board IDE/SATA
•    An IDE controller on the NVIDIA® nForce MPC51 (nForce 430) chipset provides IDE HDD/CD-ROM with PIO, Bus Master and Ultra DMA133/100/66 operation modes.
-    Can connect up to 4 IDE devices
•    NVIDIA® nForce MPC51 (nForce 430) supports 4 SATA II ports
-    Transfer rate is up to 300MB/s
-    Supports RAID 0 or 1
Need to say more?
However, you might be able to hack the BIOS and replace the RAID Option rom to support Raid5.....
But I don't think the standard BIOS does it.

K8NGM2-NBP USB problem

I have a K8NGM2-NBP and the USB will not operate. It shows up as:
Universal Serial Bus Controller
- Standard Enhanced PCI to USB host controller
- standard OpenHCD Host controller
- USB Root Hub
- USB Root Hub
I have been running this machine with Linux for several months with no issue. I had a reason to move it to Windows XP.
I installed WinXP SP2.
While it thinks the hardware is there, it will not use it or show any device that is in a USB port either front or on the motherboard.
I've read through a number of the post, but have a feeling that it's related to going straight to SP2.
Most of the MS post talk about USB 2.0 support in SP1.
Appreciate any help!

Thanks for the post.
I deleted all the USB entries, and rebooted from no power attached.
Same result, but now it thinks I have a floppy drive. Which I don't. I have plenty of them, but only attach them for a BIOS operation.
rest of system is working perfectly.
Robert

MEMTEST FAILURE

I keep getting failure on memtest dont know why. I have tested eveything set on stock,fast and slow timings with no effects. I also tried with 1 memory stick at a time but still fails.
I think i must RMA my memorys what do u think?

Quote from: filleCarpet on 08-July-05, 00:05:36
tiresmoke my computer is running everything on stock except the memory voltage set to 2.8 volts
and what do u mean on test 5 or 7 there is no such test numbers on memtest, all u can see is percentage rate and errors
Tiresmoke is right, if you read the instructions from the memtest86 you will see that it makes several test pattern tests (redundant).
If you look at the top of the screen when memtest is working you'll see the numbers.
Be well....

SpeedFan doesn't see K8NGM2-NBP temps/speeds

This new build is working fine except that I can't get SpeedFan (4.28) to see hardware sensors except the HD. The temp/speed/voltage values are reported in bios and also in MSI's utility and the bios smartfan control seems to work fine. What am I doing wrong? Thanks.

Thanks for your suggestion, but the current beta didn't work for me. I did use the test feature to send info to the author so maybe he will respond with a suggestion. Until then, I am using nTune's monitor. I'm surprised that SpeedFan doesn't seem to work with this board because the K8NGM2-FID is listed on its website as allowing fan control (and presumably hardware monitoring).

K8NGM2-FID Boot Failure

I have the system for my HTPC in my signature below, with the addition of a Hauppauge PVR-500MCE. I put the machine all together friday night and when I connected monitor (VGA analog) keyboard/mouse (PS2) and power cord, the Computer booted, gave me a very fragmented Bios, told me I needed to press F2 to reset the defaults, when I did the video went "funny" and then began to reboot but never fired back up. No Post beeps, I pulled the power, switched it on and off a few times, reapplied the power and still nothing.
Any thoughts, suggestions, comments, questions would be appreciated. I am not near the machine currently, but will be in an hour or two. I do know that the CPU, Memory and harddrives worked in another machine but I am pulling my hair out.
Thanks
Hoot.

One of the first things that I notice is the PSU listed under your HTPC rig. Only 10A on 12V1 .
Usually socket 939 boards have needed at least 18A on the the 12V. You may want to try another PSU that has a single rail with over 18A on the 12V, or a different multi rail with at least 18A on 12V1. However higher Amps are preferred. See if you have a friend that might have one you can borrow to test out.
Also try unplugging your system and clear your CMOS. See if that helps any.

MOVED: K8NGM2 Questions

This topic has been moved to AMD64 nVidia Based board.
https://forum-en.msi.com/index.php?topic=99406.0

My MSI K8NGM2-NBP is giving problems with the red in the video,first was intermitent and later died, only green and blue are working, so I decide to upgrade with an PCI-E video card to solve the problem then I bought an MSI geforce 7300 gs and it didn't work,,no video at all, thinkiing that the msi card came damage I changed for as MSi 8400 gs and the same problem no video at all,,only the onboard video had video.
I verify that the bios was the PCI-E the primary as it was, then I went to my father house which have an ASUS A8N with the same nforce 6150 to see if my mobo was the problem and it didn't work either with the bios set to PCI-E as primary so is not a problem of bios setting, is a problem of compatibility, it looks this first generation of PCI-E motherboards only works with old first generation PCI-E cards.
I'm frustrated thinking the need of change mobo, ram and procesor because I cant find any information about my motherboard PCI-E compatibilities.
MSI K8NGM2-NBP
2x 512mb corsair value = 1gb of ram
2 WD 500gb sata2
sound blaster platinum 5.1 pci is old but i love the bay
aspire x-dreamer 450w
athlon x2 4200
samsung syncmaster 750 analog crt( LCD's dont have the colors of a crt yet)
Please help me...I dont have red in my monitor and my monitor is not the problem

MOVED: MS-7207 Question

This topic has been moved to AMD64 nVidia Based board.
https://forum-en.msi.com/index.php?topic=103171.0

Quote from: nicethugbert on 03-December-06, 11:40:52
I'm looking for drivers, etc., for a MS 7207 V 2.0, K8NGM2 H, N1996 but I haven't found them. I found K8NGM2 NBP/IL/L/FID/V but not H. Please tell me where they are. TIA.
hi there welcome to forum,
there are the same. "H" mean its RoHS compilant.
here mate, for K8NGM2-FID, K8NGM2-H-FID, K8NGM2-IL, K8NGM2-L ---> http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=702&kind=1
for K8NGM2-NBP --> http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=723&kind=1

MS-7207G network driver

My network driver (NVENETFD.sys) became corrupted. Searching this site I've been unable to locate it. Running Win XP Pro SP3. Any suggestions?

Well, is that a retail board or oem from a prebuilt PC? The only MS-7202 board I could find is K8NGM2-NBP (MS-7207NNG). Check if this is your board: http://global.msi.com.tw/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3_no=&prod_no=245
If so you can download NVIDIA GeForce 6100/6150 + nForce 430/410 System Drivers (which are containing the ethernet driver) here: http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=245

MacBook Pro Retina (mid 2014) failing Memtest ?

Hi !
I'm experiencing issues with my MB pro retina mid 2014 since I have it (1 month now) : kernel panic, reboots, freeze, and so on. As I have a little experience with computers, I thought it sound like a memory issue. So I ran memtest (from USB stick, and from the OS) after a complete reinstall (from the network).
Now, memtest from USB stick shows 10560 errors and freezes the computeur after 1h30. Memtest from the OS shows that :
Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only
NOTE: No command-line arguments have been specified
Using defaults: Test all available memory, one test pass, no logfile
Mac OS X 10.9.4 (13E28) running in multiuser mode
Memory Page Size: 4096
System has 4 Intel core(s) with SSE
Requested memory: 5943MB (6232047616 bytes)
Available memory: 5943MB (6232047616 bytes)
Allocated memory: 5943MB (6232047616 bytes) at local address 0x0000000101000000
Attempting memory lock... locked successfully
Partitioning memory into 2 comparison buffers...
Buffer A: 2971MB (3116023808 bytes) starts at local address 0x0000000101000000
Buffer B: 2971MB (3116023808 bytes) starts at local address 0x00000001babac000
Running 1 test sequence... (CTRL-C to quit)
Test sequence 1 of 1:
Running tests on full 5943MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 2971MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : testing 19 of 64
FAILURE! Data mismatch at local BUFA address 0x00000001a144b978, BUFB address 0x000000025aff7978
BUFA Data: 0xaaaaaaaaaaaaaaae, BUFB Data: 0xaaaaaaaaaaaaaaaa
Bit Spread : testing 1 of 128
FAILURE! Data mismatch at local BUFA address 0x00000001a42e09f8, BUFB address 0x000000025de8c9f8
BUFA Data: 0xfffffffffffffffe, BUFB Data: 0xfffffffffffffffa
Bit Flip : testing 3 of 512
FAILURE! Data mismatch at local BUFA address 0x00000001a0d4f978, BUFB address 0x000000025a8fb978
BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000000000001
Walking Ones : testing 3 of 128
FAILURE! Data mismatch at local BUFA address 0x00000001a18c1978, BUFB address 0x000000025b46d978
BUFA Data: 0xffffffffffffffff, BUFB Data: 0xfffffffffffffffb
Walking Zeroes : testing 4 of 128
FAILURE! Data mismatch at local BUFA address 0x00000001a21bd978, BUFB address 0x000000025bd69978
BUFA Data: 0x000000000000000c, BUFB Data: 0x0000000000000008
*** Memory Test Failed *** Please check transcript for details.
Execution time: 512 seconds.
I run the global Apple Hardware test that says there is probably an issue with a memory module.
Here's my trouble : I went to my nearest Apple Premium reseller, the tech guy says my Macbook has no issue, and is in perfect condition... he just made a test like in the terminal : yes something, to "stress" the memory. He says memtest isn't edited by Apple and its results are not relevant, and AHT is just a simple user diagnostic tool, but it's not relevant neither...
But I'm pretty sure AHT AND memtest can't be wrong ? What can I do ?

I have the same problem with MBP 15 retina 2013 late... I think something goes wrong.... ((((

In and out of sleep (no reboots) for over a week: instability, failures

My wife rarely reboots her MacBook. She'll literally go a month without rebooting it. She just puts it to sleep when she's done and wakes it up again when she needs it. Only for the occasional software update will she begrudgingly and belatedly reboot the thing.
The same isn't true for my MacBook Pro. It takes about a week (or two at the outside) from the time I reboot my MBP until the time it manifests some kind of instability or soft hardware failure. Sometimes, apps crash, or I'll get a kernel panic (the gray screen that asks you, in multiple languages, to reboot). The last time, the computer wouldn't go to sleep when I closed it, and bluetooth became "unavailable". The time before that, the core keyboard and trackpad stopped working, so I had to use a USB mouse to cleanly shut everything down. A reboot always completely clears everything up.
I called AppleCare about this. They told me to run the hardware tests that come on the MacOS install disc. It ran for over 24 hours and could find no problems. Without some kind of diagnosis, they can't help me.
Both the MacBook and the MBP have had their memory upgraded. The MacBook now has one of the Apple (Samsung) 1GB sticks that had been in the MBP, along with another 1GB stick from Crucial. The MBP has one of the original 1GB sticks that came with the MBP, along with a 2GB stick from Crucial. My understanding is that in sleep mode, the memory is in a low power auto-refresh state (I get the impression that some of the peripherals are also not entirely switched off either). It seems to me that perhaps one of the memory sticks is bad. In fact, the 2GB one from Crucial I have is actually a replacement for the one I originally bought from them. Could I get two bad ones in a row? Is Crucial having quality problems?
I've decided I'm going to try each memory stick in isolation for two weeks with no reboots to see if I can tell which one is the culprit. (It's not going to be fun running with only the 1GB stick.)
There's one other thing to mention. These instability problems didn't always happen. They just started happening one day with two kernel panics in a row. Prior to that, I had been running some neural nets experiments, where I was running SSE-heavy code on both processors at full tilt for two weeks straight. I was concerned about the CPU temperature getting awfully high, so I installed a fan control tool to set the RPM to max, and I directed external fans at the computer. The problems started happening just after that. I'm concerned that some component(s) may have been damaged due to sustained excessive heat.
Can anyone give me any tips on resolving what's going on here?

Have you considered the possibility that the third party fan software might itself be implicated in the issue, theosib (or perhaps something else introduced at about that time?).
My inclination in a situation like this would be to back up your drive to an external, wipe the drive, and do a clean installation. At the very least I'd try an archive and install.
Do you have plenty of free space on the drive? Once you get things down below the last 10 to 20% things can get hairy at times, and may not be fixed as a result of simply freeing up some room, as free space fragmentation is likely to have set in.
As far as RAM goes, either "Rember" - http://www.kelleycomputing.net:16080/rember/ or, better still, but less user friendly, "memtest" - http://www.memtestosx.org/ does a much better job of checking your RAM than the AHT. Still takes a while to run for a thorough test, but much quicker than the approach you are planning on using.
You might also want to use "Activity Monitor" to check for any applications with progressive "memory leaks" or that are acting as CPU hogs, given your symptoms
Cheers
Rod

TS 140 Windows Server 2012 R2 install failure error 0x80070570

Recently bought 2 TS140 70A4001PUX servers with Xeon E3 1245 v3 attempting to install eval version of server 2012 R2 (latest on site April refresh) and keep getting the following error at around 62% in the getting files ready for installation:
Windows can not install required files. The file may be corrupt or missing. Make sure all files required for installation are available, and restart the installation. Error code: 0x80070570
I have seen web search results for various MS OSes that indicate this is due to bad memory, corrupt installation media or download, Nic cards, BIOS settings etc.
To rule out memory ran memtest for hours with no errors against the crucial 32GB mem 2 (CT2KIT102472BD160B) also tried installing against the 4GB mem that came with the system. I think I have done enough to rule out the memory.
Installation media, I downloaded the ISO from Microsoft's eval site three different times using Firefox, Chrome and IE burned the image to DVD 2 different times and tried numerous times using Rufus on an 8GB USB stick in different USB ports. I’ve tried installing the datacenter version with both GUI and server core options. Next thing I’m going to try is to install Server 2012 from an older ISO that I have used successfully many times in the past will update later though I would prefer to install fresh from R2.
I also have the Lenovo 1GBPS Ethernet I350-T2 Server adapter by Intel for ThinkServer. I have tried installing with it inserted and with it removed, also with nothing even disabling the on board Nic in the BIOS. Same result.
The SSD drive I have is the Samsung 850 Pro 128GB. After the failure I am able to mount this drive on another machine and see that a significant amount of files get copied to it so I ruled out the sata cable. I also tried with another no SSD WD HD with the same result. I even break out at install run dispart and clean the partitions.
Excerpts from setupact.log on SSD:
2015-03-24 13:58:37, Info       [0x0606cc] IBS   Calling WIMApplyImage (flags = 0x180)...
[800] [UncompressFile994) -> file corrupted in block at offset 000000541283B3F2] G:\Windows\System32\DriverStore\FileRepository\netelx.inf_amd64_82d20ebbcbf8b5af\netelx.PNF (Error = 1392)
2015-03-24 13:59:54, Error     [0x0606cc] IBS   WIMApplyImage failed; hr = 0x80070570[gle=0x00000570]
2015-03-24 13:59:54, Error     [0x0600a1] IBS   DeployImage:Image application failed; hr = 0x80070570[gle=0x00000057]
For BIOS settings I have reverted back to defaults tried IDE instead of AHCI and also tried CSM support enabled and disabled, NIC both enabled disabled.
Any suggestions would greatly be appreciated.
Thanks.
Solved!
Go to Solution.

In case anyone is interested the Server 2012 R@ eval ISO I had issues with is the following file:
9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.ISO
I am also reporting this to MS.

Mac Mini late 2012 turns on after electrical failure

Hi. I bought a Mac Mini (late 2012 model) with OS X Mountain Lion in November 2013.
I upgraded to OS X Mavericks.
I have not changed any of my Mac's settings. They are all on default settings.
Under Energy Saver, only "Put hard disks to sleep when possible" and
"Wake for network access" are checked. Nothing else is checked.
Nothing is scheduled to turn on.
What happens is I always put my Mac to sleep when I'm not using it.
I have my Mac, speakers, cable modem and LCD monitor plugged
into an expensive name brand 500VA electromechanical voltage regulator
to prevent power spikes and surges from damaging my computer.
There are electrical blackouts a few times a month and this happens
when the Mac is either sleeping or being used.
The blackouts last about 30 to 45 minutes when they occur.
When the power comes back on, approximately 5 to 10 minutes later
the Mac Mini turns on by itself. I hear that familiar startup
sound from the speaker and then it boots until it reaches the login screen.
I'm confused why it would turn on by itself.
I use cable internet but my cable modem was unplugged at the time.
My internet connection is a wired ethernet connection using a Cisco 2100
cable modem.
Barring the paranormal, what would cause it to turn on by itself?
I'm not using a UPS.. just a voltage regulator (line conditioner).
Thanks for any help. I appreciate it.

Hi brody. I turned off printer and screen sharing.
I have a new problem related to sleep:
I put my Mac Mini to sleep using the menu and selecting "sleep".
Mac goes to sleep and you can see the LED on the front of the Mac
getting brighter and dimmer (as it always does when sleeping, no problem).
Problem was when I woke up 7 hours later the LED light was off, so
I thought there was another power failure but there wasn't because
my cable decoder box will switch from displaying the time to displaying
channel 1 if there's a power outage and power returns. However, it
still displayed the time so that meant there was no outage.
So, I figured it was not a power outage although we sometimes
get very brief (split-second) "brownouts" or blackouts.. they happen
so fast so I can't rule out that happening.
I tried pressing keys on the keyboard and clicking the middle button
of my Logitech mouse but no go.
Thinking the Mac had shut itself off, I briefly pushed the power button
on the back of the Mac.
Mac woke up with the login screen covered in a white haze with
|||||||||||||||||||||| at the bottom (like a progress bar).
That only lasted 15 seconds or so and finally the normal
login colors appeared and I could type my password.
So, the Mac was asleep but that behavior disturbed me.
1. Why did the LED turn off after being asleep for several hours?
2. Why couldn't I wake it from sleep using traditional methods (pushing a key/clicking middle mouse button)?
3. Why did the Mac wake up only by pushing the power button on the back?
4. What was the reason for the foggy white overlay that appeared when it woke up along
with a | | | | | | | | progress bar at the bottom of the screen for 15 seconds or so?
I ran an Apple Hardware Test by booting with the "D" key held down and it passed.
I also booted into Single User Mode and ran Memtest twice with no errors.
I really appreciate your help. My Mac is covered under AppleCare but I hope nothing
is wrong with it. I'd hate to be without my Mac even for a day. heh. :-)
Thanks.

Black Screen After Wakeup / Sleep failure code 0x00000000 0x1f006500

Problem waking up from sleep on my mid-'09 MacBook Pro 5.4 running Lion. Bought new, under 2 years old. Upgraded RAM to 8GB and installed an SSD around Janurary this year. Problem started under Snow Liopard no more than a couple weeks back from today. Searched the web up and down for this, found a lot of people with the exact same issue, and tried quite a few suggestions.
- changed settings to wake up on pressed keyboard instead of lid open
- logged in under a different user
- repaired permissions and checked disk (some permission fail to repair)
- run extensive Apple's hardware test and memtest, together with AppleJack in single user mode (all passed, although Apple hardware test sometimes froze & I had to restart)
- removed all side programs that use kext files, only leaving Google's
- uninstalled istatpro, iAlertU and LittleSnitch
- set not to wake up for bluetooth nor network
- set fast sleep instead of hibernation so that RAM is not written to an SSD
- switched RAM modules around. Sometimes after a hard reset my RAM is cut in half and shows either 4GB or 7.75GB instead of normal 8GB (only the second module slot is displayed as empty)
- removed ethernet network settings (disabling it), restarted & added settings / reenabled it
- SMC, PMU resets
- deleted power management plist file
Haven't tried hibernation when RAM is written to a disk but this is an absolute last resort...
Now trying out the "SmartSleep" program / application.
After every hard reset the login screen freezes (mosue works but no response from the keyboard) so I wait for a few minutes or restart the boot and wait a minute or so again.
My plan now is to find a set of RAM modules somewhere to test and go into an Apple store for a check-up. I had AppleCare transferred from another laptop that expired on March this year. So I am not covered now. So far my Apple laptops haven't been all that reliable, it seems. This one went for nearly two years with no hardware problems - this could be the first one.
Here is a full log extract of the problem area:
Jul 27 23:09:39 Super-Bad-Dude kernel[0]: macx_swapon SUCCESS
Jul 27 23:35:13 Super-Bad-Dude kernel[0]: hfs: cat_lookup_siblinglinks: getkey for 2389754 failed 2
Jul 27 23:51:43 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 27 23:51:43 Super-Bad-Dude kernel[0]:
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: Wake reason: OHC1
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: Previous Sleep Cause: 5
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 6 of Hub at 0x4000000) may have caused a wake by issuing a remote wakeup (2)
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link DOWN
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'X3'.
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
Jul 28 09:12:55 Super-Bad-Dude kernel[0]: HID tickle 24 ms
Jul 28 09:12:56 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 09:12:57 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'US'.
Jul 28 09:12:57 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 MAC AUTH succeeded
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link UP
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: AirPort: Link Up on en1
Jul 28 09:12:59 Super-Bad-Dude kernel[0]: en1: BSSID changed to 94:44:52:70:30:88
Jul 28 09:13:00 Super-Bad-Dude kernel[0]: AirPort: RSN handshake complete on en1
Jul 28 09:13:30 Super-Bad-Dude kernel[0]: nspace-handler-set-snapshot-time: 1311840811
Jul 28 09:25:04 Super-Bad-Dude kernel[0]: hfs: cat_lookup_siblinglinks: getkey for 2392242 failed 2
Jul 28 09:29:03 Super-Bad-Dude kernel[0]: nspace-handler-set-snapshot-time: 1311841745
Jul 28 09:29:08 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80230b7b20 (sessions; ret 22; type 2)
Jul 28 09:29:08 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80230b7b20. dropping the event.
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff802590a268 (chatsync; ret 22; type 2)
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802590a268. dropping the event.
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff802590a268 (chatsync; ret 22; type 2)
Jul 28 09:29:09 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802590a268. dropping the event.
Jul 28 09:29:10 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff802590a268 (chatsync; ret 22; type 2)
Jul 28 09:29:10 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff802590a268. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:14 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235be930 (Keychains; ret 22; type 2)
Jul 28 09:29:15 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235be930. dropping the event.
Jul 28 09:29:18 Super-Bad-Dude kernel[0]: add_fsevent: unable to get path for vp 0xffffff80235b4d90 (login.keychain; ret 22; type 9)
Jul 28 09:29:18 Super-Bad-Dude kernel[0]: add_fsevent: unabled to get a path for vp 0xffffff80235b4d90. dropping the event.
Jul 28 09:30:20 Super-Bad-Dude kernel[0]: IOSurface: buffer allocation size is zero
Jul 28 09:32:14 Super-Bad-Dude kernel[0]: IOSurface: buffer allocation size is zero
Jul 28 10:12:42 localhost kernel[0]: Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64
Jul 28 10:12:42 localhost kernel[0]: vm_page_bootstrap: 1959200 free pages and 56032 wired pages
Jul 28 10:12:42 localhost kernel[0]: kext submap [0xffffff7f8072e000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff800072e000]
Jul 28 10:12:42 localhost kernel[0]: zone leak detection enabled
Jul 28 10:12:42 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jul 28 10:12:42 localhost kernel[0]: mig_table_max_displ = 72
Jul 28 10:12:42 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Jul 28 10:12:42 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Jul 28 10:12:42 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
Jul 28 10:12:42 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Jul 28 10:12:42 localhost kernel[0]: calling mpo_policy_init for Sandbox
Jul 28 10:12:42 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Jul 28 10:12:42 localhost kernel[0]: calling mpo_policy_init for Quarantine
Jul 28 10:12:42 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Jul 28 10:12:42 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 28 10:12:42 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jul 28 10:12:42 localhost kernel[0]: MAC Framework successfully initialized
Jul 28 10:12:42 localhost kernel[0]: using 16384 buffer headers and 10240 cluster IO buffer headers
Jul 28 10:12:42 localhost kernel[0]: IOAPIC: Version 0x11 Vectors 64:87
Jul 28 10:12:42 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jul 28 10:12:42 localhost kernel[0]: PFM64 0xf10000000, 0xf0000000
Jul 28 10:12:42 localhost kernel[0]: [ PCI configuration begin ]
Jul 28 10:12:42 localhost kernel[0]: console relocated to 0xf10010000
Jul 28 10:12:42 localhost kernel[0]: PCI configuration changed (bridge=3 device=1 cardbus=0)
Jul 28 10:12:42 localhost kernel[0]: [ PCI configuration end, bridges 6 devices 18 ]
Jul 28 10:12:42 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 13:08:12 Jun 18 2011) initialization complete
Jul 28 10:12:42 localhost kernel[0]: Sleep failure code 0x00000000 0x1f006500
Jul 28 10:12:42 localhost kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in now active, GUID 60fb42fffef17f9a; max speed s800.
Jul 28 10:12:42 localhost kernel[0]: USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833
Jul 28 10:12:42 localhost kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
Jul 28 10:12:42 localhost kernel[0]: mbinit: done [64 MB total pool size, (42/21) split]
Jul 28 10:12:42 localhost kernel[0]: Pthread support ABORTS when sync kernel primitives misused
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib kmod start
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeDataless kmod start
Jul 28 10:12:42 localhost kernel[0]: 2.4.0 Little Snitch: starting
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Jul 28 10:12:42 localhost kernel[0]: com.apple.AppleFSCompressionTypeDataless load succeeded
Jul 28 10:12:42 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Jul 28 10:12:42 localhost kernel[0]: BTCOEXIST off
Jul 28 10:12:42 localhost kernel[0]: wl0: Broadcom BCM432b 802.11 Wireless Controller
Jul 28 10:12:42 localhost kernel[0]: 5.100.98.75
Jul 28 10:12:42 localhost kernel[0]: CoreStorage: fsck has finished successfully for lvg "9EE70322-2538-4C97-ABBF-840E47EC5495"
Jul 28 10:12:42 localhost kernel[0]: thr 0xffffff801357da40 cs_thread_create thread=0xffffff8013beac68 arg=0xffffff8013bea800
Jul 28 10:12:42 localhost kernel[0]: thr 0xffffff801357da40 cs_thread_create thread=0xffffff8013beaee0 arg=0xffffff8013bea800
Jul 28 10:12:42 localhost kernel[0]: rooting via boot-uuid from /chosen: 8AAB677E-1234-3FCA-A115-09A923BB759D
Jul 28 10:12:42 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jul 28 10:12:42 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@B/AppleMCP79AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/OWC Mercury Extreme Pro SSD Media/IOGUIDPartitionScheme/X X X@2/CoreStoragePhysical/CoreStorageGroup/X X X@s0
Jul 28 10:12:42 localhost kernel[0]: BSD root: disk1, major 14, minor 4
Jul 28 10:12:42 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 12953088 to: 16393216 (joffset 0x37e000)
Jul 28 10:12:42 localhost kernel[0]: jnl: unknown-dev: journal replay done.
Jul 28 10:12:42 localhost kernel[0]: Kernel is LP64
Jul 28 10:12:42 localhost kernel[0]: hfs: Removed 53 orphaned / unlinked files and 3052 directories
Jul 28 10:12:43 localhost kernel[0]: NVEthernet: Ethernet address 60:fb:42:f1:7f:9a
Jul 28 10:12:43 localhost kernel[0]: AirPort_Brcm4331: Ethernet address 00:26:bb:18:46:7c
Jul 28 10:12:43 localhost kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Jul 28 10:12:43 localhost kernel[0]: IO80211Interface::efiNVRAMPublished():
Jul 28 10:12:45 localhost kernel[0]: Created virtif 0xffffff8015054000 p2p0
Jul 28 10:12:45 localhost kernel[0]: NVDANV50HAL loaded and registered.
Jul 28 10:12:45 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Jul 28 10:12:45 localhost kernel[0]: Previous Shutdown Cause: -128
Jul 28 10:12:45 localhost kernel[0]: DSMOS has arrived
Jul 28 10:12:46 localhost kernel[0]: jnl: disk2s3: replay_journal: from: 24017408 to: 5658624 (joffset 0x6ff000)
Jul 28 10:12:46 localhost kernel[0]: macx_swapon SUCCESS
Jul 28 10:12:46 localhost kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: nspace-handler-set-snapshot-time: 1311844369
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'US'.
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: AppleLMUController found an AG vendor product (0x9cb1), notifying SMC.
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 MAC AUTH succeeded
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link UP
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: AirPort: Link Up on en1
Jul 28 10:12:48 Super-Bad-Dude kernel[0]: en1: BSSID changed to 94:44:52:70:30:88
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: AirPort: RSN handshake complete on en1
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: DAD detected duplicate IPv6 address fe80:0005::0226:bbff:fe18:467c: NS in/out=1/1, NA in=0 inx=0
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: DAD complete for fe80:0005::0226:bbff:fe18:467c - duplicate found
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: manual intervention required
Jul 28 10:12:49 Super-Bad-Dude kernel[0]: en1: possible hardware address duplication detected, disable IPv6
Jul 28 10:12:53 Super-Bad-Dude kernel[0]: nstat_lookup_entry failed: 2
Jul 28 10:12:56 Super-Bad-Dude kernel[0]: jnl: disk2s3: journal replay done.
Jul 28 10:13:02 Super-Bad-Dude kernel[0]: hfs: Removed 0 orphaned / unlinked files and 888 directories
Jul 28 10:18:51 Super-Bad-Dude kernel[0]: hfs: cat_lookup_siblinglinks: getkey for 2392900 failed 2
Jul 28 10:23:00 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:23:00 Super-Bad-Dude kernel[0]:
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: Wake reason: EC LID0
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: HID tickle 0 ms
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: Previous Sleep Cause: 5
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link DOWN
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'X3'.
Jul 28 10:23:13 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
Jul 28 10:23:14 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:23:41: --- last message repeated 1 time ---
Jul 28 10:23:41 Super-Bad-Dude kernel[0]:
Jul 28 10:24:09 Super-Bad-Dude kernel[0]: Wake reason: EC LID0
Jul 28 10:24:09 Super-Bad-Dude kernel[0]: HID tickle 0 ms
Jul 28 10:24:09 Super-Bad-Dude kernel[0]: Previous Sleep Cause: 5
Jul 28 10:24:10 Super-Bad-Dude kernel[0]: 00000000 00000020 NVEthernet::setLinkStatus - not Active
Jul 28 10:24:12 Super-Bad-Dude kernel[0]: en1: 802.11d country code set to 'US'.
Jul 28 10:24:12 Super-Bad-Dude kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
Jul 28 10:24:17 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 Auth timed out
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: MacAuthEvent en1   Auth result for: 94:44:52:70:30:88 MAC AUTH succeeded
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: wlEvent: en1 en1 Link UP
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: AirPort: Link Up on en1
Jul 28 10:24:19 Super-Bad-Dude kernel[0]: en1: BSSID changed to 94:44:52:70:30:88
Jul 28 10:24:20 Super-Bad-Dude kernel[0]: AirPort: RSN handshake complete on en1

All sorts of ways. Nothing here helped. Went into the store and the consensus is a faulty / failed logic board. Although on my first visit I was sent back home because the company doesn't support self installed SSDs, on my second visit Alex and his manager have graciously agreed to replace be part and weave the fee for me despite expired AppleCare. This is great. I am chuffed. Problem solved, hopefully. Thanks to Apple & it's professional and efficient staff.

K8NGM2-NBP MemTest Failure

Similar Messages

Maybe you are looking for