Need help on how to find a memory leak...

Started by guest2859, April 11, 2013, 02:12:26 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

guest2859

Okay, I've searched an got many answers for this, almost all point to RAM. I know it's a memory leak due to how it lines up.

I have 6 chips in (2gb each), they were there since the computer was bought.

I replaced the hard drive less than 2 months ago, same brand, model and size, cloned from previous hard drive installation. [1TB, using 275gb]

If I start up the computer and go right to work, the RAM will max out, the computer freezes, and it "bluescreens" [no BSOD] then force-restarts.

If I set and let it get through all the startup processess, it runs without problems.

I've run Windows' memory checker, and it says all are fine. Possible other answers for this?

Quick Specs:
RAM : 12gb DDR3
Vid. : 1gb AMD Rad. HD 6800
Pro. : Intel i7 @ 3.07gHz
MB. : Sabertooth x58

Tìtstewan

Maybe you can check out with an other HDD, and with an OS only just for testing?
I think, you don't had this problem before replacing the HDD, do you?

-| Na'vi Vocab + Audio | Na'viteri as one HTML file | FAQ | Useful Links for Beginners |-
-| Kem si fu kem rä'ä si, ke lu tìfmi. |-

Taronyu Leleioae

#2
That sounds like RAM failure.  You could certainly play the... pull one or two out and do the swap game.  I had to spend days last year with a new server to prove I had a bad stick.  Also ended up being a bad batch of mobo's...

Now... we're presuming it's hardware.  I've also had the experience where older versions of SQL Server running on a server, have caused memory leaks.  It was all in the SQL code and the only thing we could do, was a full shut down and reboot once every few months to clear the problem (ram not being released after a process).


So... to check your ram..., what I would do...

1)  Forget Windows memory checker ever existed...

2)  Download Hiren's boot cd and burn it to a cd or dvd.  Then run memtest86+ completely.  (+ is the much better newer version).
http://www.hirensbootcd.org/files/Hirens.BootCD.15.2.zip

You'll need an iso burning software to burn the iso file to a cd or dvd.  Here's a good one that's also free.
http://www.imgburn.com

If you have an issue with a hdd, then I'd also do a full sector test (non invasive) on your hdd.  Hiren's has all those tools too in the hdd menu.  (Seagate, Western Digital, Hitachi...)

Every once in awhile, Hirens will hang on certain computers.  Or on certain hdd tests.  It's totally random.  I've had to pull a hdd and stick it in another machine, then MAKE SURE you boot to the Hiren's disk...

If you find a failure on a particular ram stick, pull it (and probably the matching dual channel mate), run Memtest86+ again.  And again to be sure.  There's always the odd chance you have a bad mobo.  However keep in mind, the extremely rare possibility would be bad cpu since the i series now has the memory controller built into the cpu.  But I'd still say bad mobo first.  

3)  You should also look at the BIOS (firmware) and check the manufacturer for BIOS updates.  May be an update addressing a memory or cpu problem.  Ran into this problem once too for a very recently new computer used in graphics design and gaming that would crash randomly.  Problem was a BIOS conflict with the latest version of cpu that had been installed.  A BIOS upgrade fixed the problem...


(also see additional post below...)

Tìtstewan

Memtest86+ will work on USB-sticks too. (If the mainboard support boot from USB stick. ;)

-| Na'vi Vocab + Audio | Na'viteri as one HTML file | FAQ | Useful Links for Beginners |-
-| Kem si fu kem rä'ä si, ke lu tìfmi. |-

Taronyu Leleioae

#4
Quote from: Tìtstewan on April 11, 2013, 10:20:03 AM
Memtest86+ will work on USB-sticks too. (If the mainboard support boot from USB stick. ;)
Very true.  I have the old reliable Hirens 10.6 version which works best on old desktops and servers on a USB.  (Not every computer or server has a (functional) cd or dvd drive...)  HOWEVER..., by booting from USB, you introduce an additional element (USB circuits) which too could be affected.  The goal is to isolate everything to find the actual root cause.  Granted a usb issue is truly minimal..


4)  In rereading your original post, I'd also serious check out your graphics card and go to that manufacturer directly to find out if there is a recent drivers update.  Just to be sure and eliminate this item.  Graphics drivers are well known to cause random bluescreens...

It still sounds like a faulty ram stick.  But you need the process of test and elimination just to be sure, and to have peace of mind...

Tìtstewan

#5
He repleced the HDD and doesn't touch other hardware. If everything works well before, I think something goes wrong with cloneing.
RAM going very rarely broken. after rebooting his PC runs without problems.

Quote from: Nantang 'Rrtayä on April 11, 2013, 02:12:26 AM
I replaced the hard drive less than 2 months ago, same brand, model and size, cloned from previous hard drive installation. [1TB, using 275gb]
...and a different hardware-ID that could cause problems with the HDD driver.
That is, why I would test an other HDD with an clean OS instalation. Also possible is to install an OS on a bootable USB stick for testing if you don't have an other HDD.

(Maybe I understood his post wrong? :-[)

-| Na'vi Vocab + Audio | Na'viteri as one HTML file | FAQ | Useful Links for Beginners |-
-| Kem si fu kem rä'ä si, ke lu tìfmi. |-

Taronyu Leleioae

It could still easily be the ram.  I had one server (Dell rack) that was nice enough to flash me a warning that one of the recently (3 month old) new sticks had failed a self test.  But then I had another server (Supermicro mobo) that ended up having a faulty one that would only fail once every 3-6 weeks causing a blue screen.  So the problem becomes identifying the problem.  It could be an OS install issue, but I wouldn't bet money on that...

Best to check EVERYTHING before having to do a clean OS installation where you may have to buy a new OS key (presuming Microsoft Windows) if it's a Windows 7 or 8 OEM version.

But I agree, it could be the OS.  Still need to eliminate the ram and check the mobo BIOS though...

Tìtstewan

Quote from: Taronyu Leleioae on April 11, 2013, 11:31:23 AM
Best to check EVERYTHING before having to do a clean OS installation where you may have to buy a new OS key (presuming Microsoft Windows) if it's a Windows 7 or 8 OEM version.
You can test Windows 90 days (standard is 30 days, but you can reset max 3 times) than you have to activate Windows.

-| Na'vi Vocab + Audio | Na'viteri as one HTML file | FAQ | Useful Links for Beginners |-
-| Kem si fu kem rä'ä si, ke lu tìfmi. |-

Taronyu Leleioae

#8
Quote from: Tìtstewan on April 11, 2013, 11:43:28 AM
[You can test Windows 90 days (standard is 30 days, but you can reset max 3 times) than you have to activate Windows.
Provided you have a fully tested, working 2nd hard drive to swap out with...  Saving your original image.  And you remember to install all the extra mobo and other device drivers.  But that is more work than hardware testing.  Which I would still do to try do the process of elimination and for personal sanity...


>  ma Nantang 'Rrtayä,
Please post what you learn from the testing and whether you identify the root of your problem!  :)

bommel

Did you have a look at the Windows event log? If it reboots, it actually could log something. However, if the computer freezes (i. e. no reboot and it is unresponsive) then usually nothing is logged - at least that is my experience. I had such funny issues when doing my first time OC.

Taronyu Leleioae

Bommel has a good point.  Check and see if windows event viewer managed to record an error.


FYI...  If that's an ASUS mobo and the one that I think it is, that's part of the same series that had cpu compatibility issues (not quite 100% compatible) that I ran into which caused random blue screens.  If it is, I checked and there are BIOS updates available towards end of 2011.  See what version yours is running...

http://support.asus.com/Download.aspx?SLanguage=en&m=Sabertooth+X58&os=29

Tìtstewan

I think, he have an Intel i7-950 3,06GHz. If is a kompatibility issues, just a BIOS update will help.

-| Na'vi Vocab + Audio | Na'viteri as one HTML file | FAQ | Useful Links for Beginners |-
-| Kem si fu kem rä'ä si, ke lu tìfmi. |-

Taronyu Leleioae

If i7-950 is the cpu, then yes, there were reported problems with this newer released Gen1 series with that era ASUS mobo's.  The BIOS update addressed CPU compatibility and, I'm suspecting, changed the bios to be able to handle the newer cpu architecture refinement (which included changes to the memory controller for the ram).

But again, this is thinking you have an ASUS Sabertooth x58 mobo with the Intel i7-950 as Tìtstewan suggested you might have...


And then I'd still run the Memtest86+ test afterwards...  Just start it and walk away for awhile...  ;)

Tìtstewan

The i7-950 ist exacly the same architecture like the i7-920, just with higher clock. (I'm really sure it is a i7-950, because I know only one CPU for the LGA 1366 with 3,06 GHz which use the X58 chipset like this Sabertooth.) Indeed, the memory controller is in the CPU. But if the mainboard one of the first genertion it need a BIOS update.

-| Na'vi Vocab + Audio | Na'viteri as one HTML file | FAQ | Useful Links for Beginners |-
-| Kem si fu kem rä'ä si, ke lu tìfmi. |-

guest2859

Well, this thread possibly just has the answer to replace my whole computer piece by piece lol.

Quote from: Tìtstewan on April 11, 2013, 09:25:47 AM
Maybe you can check out with an other HDD, and with an OS only just for testing?
I think, you don't had this problem before replacing the HDD, do you?

Yes, the problems have been occurring since before I replaced the HDD.

Quote from: Taronyu Leleioae on April 11, 2013, 10:14:40 AM
That sounds like RAM failure.  You could certainly play the... pull one or two out and do the swap game.  I had to spend days last year with a new server to prove I had a bad stick.  Also ended up being a bad batch of mobo's...

Now... we're presuming it's hardware.  I've also had the experience where older versions of SQL Server running on a server, have caused memory leaks.  It was all in the SQL code and the only thing we could do, was a full shut down and reboot once every few months to clear the problem (ram not being released after a process).


So... to check your ram..., what I would do...

1)  Forget Windows memory checker ever existed...

2)  Download Hiren's boot cd and burn it to a cd or dvd.  Then run memtest86+ completely.  (+ is the much better newer version).
http://www.hirensbootcd.org/files/Hirens.BootCD.15.2.zip

You'll need an iso burning software to burn the iso file to a cd or dvd.  Here's a good one that's also free.
http://www.imgburn.com

If you have an issue with a hdd, then I'd also do a full sector test (non invasive) on your hdd.  Hiren's has all those tools too in the hdd menu.  (Seagate, Western Digital, Hitachi...)

Every once in awhile, Hirens will hang on certain computers.  Or on certain hdd tests.  It's totally random.  I've had to pull a hdd and stick it in another machine, then MAKE SURE you boot to the Hiren's disk...

If you find a failure on a particular ram stick, pull it (and probably the matching dual channel mate), run Memtest86+ again.  And again to be sure.  There's always the odd chance you have a bad mobo.  However keep in mind, the extremely rare possibility would be bad cpu since the i series now has the memory controller built into the cpu.  But I'd still say bad mobo first. 

3)  You should also look at the BIOS (firmware) and check the manufacturer for BIOS updates.  May be an update addressing a memory or cpu problem.  Ran into this problem once too for a very recently new computer used in graphics design and gaming that would crash randomly.  Problem was a BIOS conflict with the latest version of cpu that had been installed.  A BIOS upgrade fixed the problem...


(also see additional post below...)

Will definitely look into it, I'm trying not to murder the ram but I guess you can't kill what's already dead

Quote from: Taronyu Leleioae on April 11, 2013, 10:49:51 AM
Quote from: Tìtstewan on April 11, 2013, 10:20:03 AM
Memtest86+ will work on USB-sticks too. (If the mainboard support boot from USB stick. ;)
Very true.  I have the old reliable Hirens 10.6 version which works best on old desktops and servers on a USB.  (Not every computer or server has a (functional) cd or dvd drive...)  HOWEVER..., by booting from USB, you introduce an additional element (USB circuits) which too could be affected.  The goal is to isolate everything to find the actual root cause.  Granted a usb issue is truly minimal..


4)  In rereading your original post, I'd also serious check out your graphics card and go to that manufacturer directly to find out if there is a recent drivers update.  Just to be sure and eliminate this item.  Graphics drivers are well known to cause random bluescreens...

It still sounds like a faulty ram stick.  But you need the process of test and elimination just to be sure, and to have peace of mind...

I've been installing Catalyst updates the day they come out, I see an update popup once per version

Quote from: Tìtstewan on April 11, 2013, 03:13:55 PM
I think, he have an Intel i7-950 3,06GHz. If is a kompatibility issues, just a BIOS update will help.
Possible. I do use i7-950 so I'll have to check into that aswell. So many things need to be done to this computer so I'll just start from the top and go down. Sorry for short replies, but I'll definitely get this done and see what is wrong.

Taronyu Leleioae

You haven't confirmed it's an ASUS board, but from what you've replied with..., I'm fairly confident you do.

Run the ram Memtest86+.  It'll take you longer to burn the Hirens to a cd (more usable with other computers) and boot to cd/dvd.  You start the MemTest86+, it'll start sequencing data patterns in test mode.  Then walk away for awhile.  I'm (almost) going to predict it comes back clean. 

Then go check out your BIOS version and do the update.  I'm thinking you have v1006 or earlier.  And there likely lies your compatibility issue causing cpu to memory glitches.

Taronyu Leleioae

Curious how you made out and what the results and possible solution(s) were...