KVR Audio

Spion · Post by **Spion** » Wed Sep 28, 2005 3:09 pm

Could be handy if you have a few (or at least one) RAM chip(s) lying arround and try replacing the current with them, if you suspect the RAM. But this smells like a huge badarse memory leak in some background program to me.

daviencrow · Post by **daviencrow** » Thu Sep 29, 2005 9:29 pm

Spion wrote:Are you sure its not a program which has a pretty serious memory leak?

I'm positive, the error occurs in Sonar, Paintshop, AOL, AIM, Windows Media Player, Energy XT, hell it can happen when removing something from the Recycling Bin.

daviencrow · Post by **daviencrow** » Thu Sep 29, 2005 9:31 pm

Spion wrote:Could be handy if you have a few (or at least one) RAM chip(s) lying arround and try replacing the current with them, if you suspect the RAM. But this smells like a huge badarse memory leak in some background program to me.

What could it possibly be, it occurs in EVERY program. Unless the memory leak is in Windows itself I am really unsure as to what it could be.

daviencrow · Post by **daviencrow** » Thu Sep 29, 2005 9:32 pm

Anyways Guys I just tested the RAM 1 stick at a time, first by booting up with 1 then the other, then running tests on each stick by itself .. Niether reported errors after several passes.. So I Reseated my Memory.

I don't think it is the RAM but the thing with Diskeeper wanting to raise my paging file so high kinda makes me suspicious still.

Anyone have any suggestions on how to pinpoint the problem a little more. You can view what I have already tried and done in my previous posts BTW.

daviencrow · Post by **daviencrow** » Thu Sep 29, 2005 9:36 pm

Also note the AOL one is the only one that doesnt give the whole instruction at 0x0009090 blah blah memory could not be read message ... AOL tells me I do not have enough memory to complete the current operation.

Paintshop has given me the same error once. The other times it crashed with the error I mentioned in the first post.

C00kie · Post by **C00kie** » Thu Sep 29, 2005 9:41 pm

So what does your memory & swap file usage look like? Any indication there is an actual leak filling the megabytes rapidly? Being an MCSA yourself you should know how to monitor that.

daviencrow · Post by **daviencrow** » Thu Sep 29, 2005 11:13 pm

C00kie wrote:So what does your memory & swap file usage look like? Any indication there is an actual leak filling the megabytes rapidly? Being an MCSA yourself you should know how to monitor that.

The Swap files, performance monitors, and everything else doesn't look like there is a memory leak. But if the memory leak is being caused by a program it might not be visible by looking at those things without knowing how to recreate the error on an whim. It appears to happen randomly... My first guess was it happend when the clipboard or something RAM intensive was going on, but it doesnt appear to be the case ... In fact it hasn't ocurred YET today... But I'm sure it will once I start using Sonar 5 or something

daviencrow · Post by **daviencrow** » Thu Sep 29, 2005 11:14 pm

BTW Windows 2000 is a slightly different story compared to XP Professional when it comes to some things. 2000 is what my cert is for. They are almost identical, but there are some specific differences that relate to this.

paragon · Post by **paragon** » Fri Sep 30, 2005 3:15 am

With it going at least 9 days now why not just do a reinstall of the OS?

A3ntar · Post by **A3ntar** » Fri Sep 30, 2005 3:52 am

I would go with Paragon. Reinstall the OS. This is typically not a hardware failure error. I think your RAM is fine, and it is something else.

josevin2000 · Post by **josevin2000** » Fri Sep 30, 2005 6:38 pm

hi daviencrow. i had faced the exact same prob u mentioned.since i am no where close to an mcsa, i simply backed up my data and reinstalled XP.. In my case the prob disappeared..

btw i was reading your posts... man u have tried every shit possible in tracing the prob.. i wish i was an msca.. still building my computer knowledge thru net research ...

neways try the resinstalll... hope it works for u too, like it did for me...

daviencrow · Post by **daviencrow** » Fri Sep 30, 2005 8:15 pm

A3ntar wrote:I would go with Paragon. Reinstall the OS. This is typically not a hardware failure error. I think your RAM is fine, and it is something else.

Reinstalling the OS would be such a pain in the ass, so im trying to make sure that the OS isnt having the problem that the hardware is. I have almost a terabyte of data that would need to be backed up. Luckily I have enough space on my external drives that I could squeeze just what I needed onto them for now.

HOWEVER On the Contrary this usually IS an indication the Ram has gone bad. No matter where I have searched or gone to for helped everything points to the RAM being the issue or a memory resident virus (which we have eliminated as a possibility) or in some cases just a f**ked up MFT.

BUT I AM HAPPY TO SEE (in a bitter sweet way) this error message I just got in photoshop while simply trying to save something, then it occured whenever pressing any tool button at all, I had never gotten before that said:

I mean come now I have 2 GB of DDR2 RAM and saving a file was too much for it to handle. Everything spiked at that moment RAM performance and usage wise. Dunno what triggered it still though exactly.

DevonB · Post by **DevonB** » Fri Sep 30, 2005 8:24 pm

What is the size of your swap file? Do you have a swap file? If not, make a 3 gig swap file (Since you have 2 gigs of RAM I think you said?) If you do already have a 3 gig swap file (maximum and minimum are same size, I'm assuming here) then remove your swap file, reboot, then recreate your swap file. It could very well be corrupted if you have a swap file, or you're getting the error because you don't have a swap file.

Devon

C00kie · Post by **C00kie** » Fri Sep 30, 2005 8:35 pm

AHA!! That's it, you have too much RAM!

Risking I'm talking a bit bollux now, but hang on: in the old DOS days, there were some gaps in the RAM memory map that were taken by ROM or the video card or whatever, and those pages were relocated. So instead of 1 MB you had 1.064 because there was 64K salvaged.

2GB is the upper limit you can address in 32bits. Now suppose there is a tiny bit (say 64k again?) relocated, the top address will go from &hFFFFFFFF to &h0000FFFF. Coicidentally I saw some of the addresses you got faults at, and they were pretty low right? Maybe Adobe wanted a bit of memory, but was polite enough to check weather the OS had it in stock, and the OS reported &h0000FFFF which was not enough for Adobe. In reality it is &h1.0000FFFF. Get my drift ??

Is this why there is a "3GB" switch somewhere in boot.ini for XP??

jouni · Post by **jouni** » Fri Sep 30, 2005 8:41 pm

You could try the oldest trick in the "when adding new memory chips to Windows" book.

Disable all swap files, boot and try after that. If ok, delete all pagefile.sys files (might be system hidden) located in partition root directories (probably only on your Windows partition). Then boot again, add swap back and boot.

Wouldn't be first time when swap file is corrupted and causes this kind of memory problems (ie. friend of mine got these errors when starting to play games). Also if you got overclocked computer, it might cause these problems if memory is running too fast. Not even cooling will help.

Memory cannot be read errors !! PLEASE HELP