If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#31
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
I don't see a CD install version.
Creating the floppy on another machine would probably be the easiest. "Will Pittenger" wrote in message ... Do they have a CD version? I still can't access my floppy from Windows. My other option is to create the floppy it needs with another machine. Bill Blanton wrote: I have no idea why they require you to register. (They used to not.) You would have to ask them. Create an account using a throwaway email address, or try this link to obtain an older version- http://www.simmtester.com/page/produ...ownload_fp.asp Frankly, I think you already have enough evidence. "Will Pittenger" wrote in message ... I was unable to load DocMemory. Their website has two download options. One demands you log in. (Why?) The other is a broken link to C-Net. Bill Blanton wrote: That is a problem with testing memory with software. You can never be sure that the test program's space is sane. OTOH, testing memory with "proper" equipment is not really worth the price for SOHO users. It's much cheaper just to buy new. I've never used RAMProbe, but looking at your screen shot it looks like it was writing out and reading back dword 0x80808080 for this stage of the test. It seems to have failed the test at the high order word at location 0x1ef2e000. Or IOW, address 0x1ef2e002. (There are 2 words in one dword.) 0x1ef2e000 is 495.2MB past 0 Not sure what Err-Bits or Count Chan means, (Err-Bits could be the number of bits that did not return as expected) It does show a total? of 7 errors in the preceding lines. Given all the "random" errors and this test, I would suspect bad memory, or possibly the motherboard. Replacing the memory would be the simplest and cheapest route. If you want another opinion try DocMemory. |
Ads |
#32
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
Don't have more sticks.
------ Will Pittenger [will 68 at mtco dot com] [will dot pittenger 1 at gmail dot com] Bill Blanton wrote: Even if it fails multiple memory tests, it's not 100% definitive, though it does narrow it down, there is the possibility it could be another component of the motherboard that is failing. (and manifesting as corrupted read/writes to memory.) It could be the memory, or any other circuitry between that and the CPU. The only way to test each explicitly is with very expensive hardware. The cheapest way to test is to try different sticks and run the diags again. "Will Pittenger" wrote in message ... Evidence? Yes. But memory or motherboard? You suggested both. Bill Blanton wrote: I have no idea why they require you to register. (They used to not.) You would have to ask them. Create an account using a throwaway email address, or try this link to obtain an older version- http://www.simmtester.com/page/produ...ownload_fp.asp Frankly, I think you already have enough evidence. "Will Pittenger" wrote in message ... I was unable to load DocMemory. Their website has two download options. One demands you log in. (Why?) The other is a broken link to C-Net. Bill Blanton wrote: That is a problem with testing memory with software. You can never be sure that the test program's space is sane. OTOH, testing memory with "proper" equipment is not really worth the price for SOHO users. It's much cheaper just to buy new. I've never used RAMProbe, but looking at your screen shot it looks like it was writing out and reading back dword 0x80808080 for this stage of the test. It seems to have failed the test at the high order word at location 0x1ef2e000. Or IOW, address 0x1ef2e002. (There are 2 words in one dword.) 0x1ef2e000 is 495.2MB past 0 Not sure what Err-Bits or Count Chan means, (Err-Bits could be the number of bits that did not return as expected) It does show a total? of 7 errors in the preceding lines. Given all the "random" errors and this test, I would suspect bad memory, or possibly the motherboard. Replacing the memory would be the simplest and cheapest route. If you want another opinion try DocMemory. |
#33
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
Don't have more sticks.
------ Will Pittenger [will 68 at mtco dot com] [will dot pittenger 1 at gmail dot com] Bill Blanton wrote: Even if it fails multiple memory tests, it's not 100% definitive, though it does narrow it down, there is the possibility it could be another component of the motherboard that is failing. (and manifesting as corrupted read/writes to memory.) It could be the memory, or any other circuitry between that and the CPU. The only way to test each explicitly is with very expensive hardware. The cheapest way to test is to try different sticks and run the diags again. "Will Pittenger" wrote in message ... Evidence? Yes. But memory or motherboard? You suggested both. Bill Blanton wrote: I have no idea why they require you to register. (They used to not.) You would have to ask them. Create an account using a throwaway email address, or try this link to obtain an older version- http://www.simmtester.com/page/produ...ownload_fp.asp Frankly, I think you already have enough evidence. "Will Pittenger" wrote in message ... I was unable to load DocMemory. Their website has two download options. One demands you log in. (Why?) The other is a broken link to C-Net. Bill Blanton wrote: That is a problem with testing memory with software. You can never be sure that the test program's space is sane. OTOH, testing memory with "proper" equipment is not really worth the price for SOHO users. It's much cheaper just to buy new. I've never used RAMProbe, but looking at your screen shot it looks like it was writing out and reading back dword 0x80808080 for this stage of the test. It seems to have failed the test at the high order word at location 0x1ef2e000. Or IOW, address 0x1ef2e002. (There are 2 words in one dword.) 0x1ef2e000 is 495.2MB past 0 Not sure what Err-Bits or Count Chan means, (Err-Bits could be the number of bits that did not return as expected) It does show a total? of 7 errors in the preceding lines. Given all the "random" errors and this test, I would suspect bad memory, or possibly the motherboard. Replacing the memory would be the simplest and cheapest route. If you want another opinion try DocMemory. |
#34
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
Here's a good place to purchase memory-
http://www.crucial.com/ That's all I can offer. "Will Pittenger" wrote in message ... Don't have more sticks. Bill Blanton wrote: Even if it fails multiple memory tests, it's not 100% definitive, though it does narrow it down, there is the possibility it could be another component of the motherboard that is failing. (and manifesting as corrupted read/writes to memory.) It could be the memory, or any other circuitry between that and the CPU. The only way to test each explicitly is with very expensive hardware. The cheapest way to test is to try different sticks and run the diags again. "Will Pittenger" wrote in message ... Evidence? Yes. But memory or motherboard? You suggested both. |
#35
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
Here's a good place to purchase memory-
http://www.crucial.com/ That's all I can offer. "Will Pittenger" wrote in message ... Don't have more sticks. Bill Blanton wrote: Even if it fails multiple memory tests, it's not 100% definitive, though it does narrow it down, there is the possibility it could be another component of the motherboard that is failing. (and manifesting as corrupted read/writes to memory.) It could be the memory, or any other circuitry between that and the CPU. The only way to test each explicitly is with very expensive hardware. The cheapest way to test is to try different sticks and run the diags again. "Will Pittenger" wrote in message ... Evidence? Yes. But memory or motherboard? You suggested both. |
#36
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
I may take the sticks I have out and see if a local computer repair
store can test them. ------ Will Pittenger [will 68 at mtco dot com] [will dot pittenger 1 at gmail dot com] Bill Blanton wrote: Here's a good place to purchase memory- http://www.crucial.com/ That's all I can offer. "Will Pittenger" wrote in message ... Don't have more sticks. Bill Blanton wrote: Even if it fails multiple memory tests, it's not 100% definitive, though it does narrow it down, there is the possibility it could be another component of the motherboard that is failing. (and manifesting as corrupted read/writes to memory.) It could be the memory, or any other circuitry between that and the CPU. The only way to test each explicitly is with very expensive hardware. The cheapest way to test is to try different sticks and run the diags again. "Will Pittenger" wrote in message ... Evidence? Yes. But memory or motherboard? You suggested both. |
#37
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
I may take the sticks I have out and see if a local computer repair
store can test them. ------ Will Pittenger [will 68 at mtco dot com] [will dot pittenger 1 at gmail dot com] Bill Blanton wrote: Here's a good place to purchase memory- http://www.crucial.com/ That's all I can offer. "Will Pittenger" wrote in message ... Don't have more sticks. Bill Blanton wrote: Even if it fails multiple memory tests, it's not 100% definitive, though it does narrow it down, there is the possibility it could be another component of the motherboard that is failing. (and manifesting as corrupted read/writes to memory.) It could be the memory, or any other circuitry between that and the CPU. The only way to test each explicitly is with very expensive hardware. The cheapest way to test is to try different sticks and run the diags again. "Will Pittenger" wrote in message ... Evidence? Yes. But memory or motherboard? You suggested both. |
#38
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
Update: I got my machine back from the people that were testing it. They
said the RAM was good. However, they did think that one or both DIMMs might have been worked loose. The error that appeared when I ran RAM Probe no longer appears. However, the program gets no farther before hanging. ------ Will Pittenger [will 68 at mtco dot com] [will dot pittenger 1 at gmail dot com] Bill Blanton wrote: I don't see a CD install version. Creating the floppy on another machine would probably be the easiest. "Will Pittenger" wrote in message ... Do they have a CD version? I still can't access my floppy from Windows. My other option is to create the floppy it needs with another machine. Bill Blanton wrote: I have no idea why they require you to register. (They used to not.) You would have to ask them. Create an account using a throwaway email address, or try this link to obtain an older version- http://www.simmtester.com/page/produ...ownload_fp.asp Frankly, I think you already have enough evidence. "Will Pittenger" wrote in message ... I was unable to load DocMemory. Their website has two download options. One demands you log in. (Why?) The other is a broken link to C-Net. Bill Blanton wrote: That is a problem with testing memory with software. You can never be sure that the test program's space is sane. OTOH, testing memory with "proper" equipment is not really worth the price for SOHO users. It's much cheaper just to buy new. I've never used RAMProbe, but looking at your screen shot it looks like it was writing out and reading back dword 0x80808080 for this stage of the test. It seems to have failed the test at the high order word at location 0x1ef2e000. Or IOW, address 0x1ef2e002. (There are 2 words in one dword.) 0x1ef2e000 is 495.2MB past 0 Not sure what Err-Bits or Count Chan means, (Err-Bits could be the number of bits that did not return as expected) It does show a total? of 7 errors in the preceding lines. Given all the "random" errors and this test, I would suspect bad memory, or possibly the motherboard. Replacing the memory would be the simplest and cheapest route. If you want another opinion try DocMemory. |
#39
|
|||
|
|||
not accessible due to inpage error" -- Why is this happening?
Update: I got my machine back from the people that were testing it. They
said the RAM was good. However, they did think that one or both DIMMs might have been worked loose. The error that appeared when I ran RAM Probe no longer appears. However, the program gets no farther before hanging. ------ Will Pittenger [will 68 at mtco dot com] [will dot pittenger 1 at gmail dot com] Bill Blanton wrote: I don't see a CD install version. Creating the floppy on another machine would probably be the easiest. "Will Pittenger" wrote in message ... Do they have a CD version? I still can't access my floppy from Windows. My other option is to create the floppy it needs with another machine. Bill Blanton wrote: I have no idea why they require you to register. (They used to not.) You would have to ask them. Create an account using a throwaway email address, or try this link to obtain an older version- http://www.simmtester.com/page/produ...ownload_fp.asp Frankly, I think you already have enough evidence. "Will Pittenger" wrote in message ... I was unable to load DocMemory. Their website has two download options. One demands you log in. (Why?) The other is a broken link to C-Net. Bill Blanton wrote: That is a problem with testing memory with software. You can never be sure that the test program's space is sane. OTOH, testing memory with "proper" equipment is not really worth the price for SOHO users. It's much cheaper just to buy new. I've never used RAMProbe, but looking at your screen shot it looks like it was writing out and reading back dword 0x80808080 for this stage of the test. It seems to have failed the test at the high order word at location 0x1ef2e000. Or IOW, address 0x1ef2e002. (There are 2 words in one dword.) 0x1ef2e000 is 495.2MB past 0 Not sure what Err-Bits or Count Chan means, (Err-Bits could be the number of bits that did not return as expected) It does show a total? of 7 errors in the preceding lines. Given all the "random" errors and this test, I would suspect bad memory, or possibly the motherboard. Replacing the memory would be the simplest and cheapest route. If you want another opinion try DocMemory. |
Thread Tools | |
Display Modes | |
|
|