My new machine...
-
Let's see my fellow CPians can help me with that... Well... I'm working on a large project so I bought a new machine this week. The problem is that the machine is random rebooting. I use a small software to check the memory of the new machine (http://www.memtest86.com) and I figured out that some blocks of my memory are not working (before someone asks, the CPU is not overheating... I check it). I'll send the machine to the store on monday, but I have lot of things to do on the weekend for the project. Does anyone know a program that can block bad memory addresses !? I can identify the bad block with the test program... but I wasn't enable to block them on WinXP. I could try the VirutalAlloc funcion in a small app, but I think it adresses to the Process Virtual Address space... not the physical memory. Does anyone know some way to solve this !? :confused: Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know. -
Let's see my fellow CPians can help me with that... Well... I'm working on a large project so I bought a new machine this week. The problem is that the machine is random rebooting. I use a small software to check the memory of the new machine (http://www.memtest86.com) and I figured out that some blocks of my memory are not working (before someone asks, the CPU is not overheating... I check it). I'll send the machine to the store on monday, but I have lot of things to do on the weekend for the project. Does anyone know a program that can block bad memory addresses !? I can identify the bad block with the test program... but I wasn't enable to block them on WinXP. I could try the VirutalAlloc funcion in a small app, but I think it adresses to the Process Virtual Address space... not the physical memory. Does anyone know some way to solve this !? :confused: Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know.I don't know if this applies anymore, but in the old days (90's) we used to just swap around memory chips to remove the offending one, although these days there seems to be less of them in there than before and they seem to need to be in sets or something (I haven't opened a PC in anger in a few years now). Sometimes what used to happen is there would be a bad contact with the chip to socket which would be resolved by taking it out and re-seating. And finally (many years before that in the 80's) I used to work in an electronic repair shop and sometimes chips would have a cracked circuit trace on them which is usually a maddening intermittent problem only diagnosed by spraying them with coolant spray ("super cool") which causes the metal to contract and force the problem to happen by temporarily seperating the trace, so the opposite might ameliorate the problem (heat it up?).
-
Let's see my fellow CPians can help me with that... Well... I'm working on a large project so I bought a new machine this week. The problem is that the machine is random rebooting. I use a small software to check the memory of the new machine (http://www.memtest86.com) and I figured out that some blocks of my memory are not working (before someone asks, the CPU is not overheating... I check it). I'll send the machine to the store on monday, but I have lot of things to do on the weekend for the project. Does anyone know a program that can block bad memory addresses !? I can identify the bad block with the test program... but I wasn't enable to block them on WinXP. I could try the VirutalAlloc funcion in a small app, but I think it adresses to the Process Virtual Address space... not the physical memory. Does anyone know some way to solve this !? :confused: Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know.Before you do anything drastic, like trying to block off any memory, I'd suggest that you open up the case, remove the memory sticks, and reinsert them a couple of times. While you're in there you might as well wiggle all the PCI cards and cable connectors you can reach, as well. Make sure that you are well grounded and touch the case a few times before you dive in, of course, and yank the power cable out of the case (turning off power is not enough) before you start. Things sometimes get loose in shipping, and dust gets into connectors in storage. A bad connection might be the only problem you really have with the new machine - I hope so.:-D
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus Long -
Before you do anything drastic, like trying to block off any memory, I'd suggest that you open up the case, remove the memory sticks, and reinsert them a couple of times. While you're in there you might as well wiggle all the PCI cards and cable connectors you can reach, as well. Make sure that you are well grounded and touch the case a few times before you dive in, of course, and yank the power cable out of the case (turning off power is not enough) before you start. Things sometimes get loose in shipping, and dust gets into connectors in storage. A bad connection might be the only problem you really have with the new machine - I hope so.:-D
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus LongRoger Wright wrote: Before you do anything drastic, like trying to block off any memory, I'd suggest that you open up the case, remove the memory sticks, and reinsert them a couple of times If I open the case I'll lose the machine warranty... :(:( Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know. -
I don't know if this applies anymore, but in the old days (90's) we used to just swap around memory chips to remove the offending one, although these days there seems to be less of them in there than before and they seem to need to be in sets or something (I haven't opened a PC in anger in a few years now). Sometimes what used to happen is there would be a bad contact with the chip to socket which would be resolved by taking it out and re-seating. And finally (many years before that in the 80's) I used to work in an electronic repair shop and sometimes chips would have a cracked circuit trace on them which is usually a maddening intermittent problem only diagnosed by spraying them with coolant spray ("super cool") which causes the metal to contract and force the problem to happen by temporarily seperating the trace, so the opposite might ameliorate the problem (heat it up?).
J Cardinal wrote: Sometimes what used to happen is there would be a bad contact with the chip to socket which would be resolved by taking it out and re-seating. I would do that, but if I open the case I'll lose the warranty. :(:(:( Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know. -
J Cardinal wrote: Sometimes what used to happen is there would be a bad contact with the chip to socket which would be resolved by taking it out and re-seating. I would do that, but if I open the case I'll lose the warranty. :(:(:( Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know. -
Roger Wright wrote: Before you do anything drastic, like trying to block off any memory, I'd suggest that you open up the case, remove the memory sticks, and reinsert them a couple of times If I open the case I'll lose the machine warranty... :(:( Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know.Bummer. Most here don't use any tricks to detect when you've opened it, so they don't know I've been inside. If you can get in without leaving a trace, don't admit that you've ever seen the inside. If not, best leave it to the factory.
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus Long -
Bummer. Most here don't use any tricks to detect when you've opened it, so they don't know I've been inside. If you can get in without leaving a trace, don't admit that you've ever seen the inside. If not, best leave it to the factory.
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus LongThere are some stickers that will "break" if the case is opened. http://www.imprints-usa.com/page2.html[^] -Steven "the yellow dart" Hicks
CPA
CodeProjectAddict
Actual Linux Penguins were harmed in the creation of this message.
More tutorials: Ltpb.8m.com: Tutorials |404Browser.com (Download Link)
-
There are some stickers that will "break" if the case is opened. http://www.imprints-usa.com/page2.html[^] -Steven "the yellow dart" Hicks
CPA
CodeProjectAddict
Actual Linux Penguins were harmed in the creation of this message.
More tutorials: Ltpb.8m.com: Tutorials |404Browser.com (Download Link)
(Steven Hicks)n+1 wrote: There are some stickers that will "break" Yes, I've seen them rarely. Another stunt they use is a dab of colored lacquer or glue on or under a screwhead. Any attempt to open such cases cracks it or makes it lose adhesion to the metal panel, thus giving away an attempt to open the box. Although I understand the practice, I resent it greatly, and try to avoid buying products from manufacturers that use these techniques.
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus Long -
(Steven Hicks)n+1 wrote: There are some stickers that will "break" Yes, I've seen them rarely. Another stunt they use is a dab of colored lacquer or glue on or under a screwhead. Any attempt to open such cases cracks it or makes it lose adhesion to the metal panel, thus giving away an attempt to open the box. Although I understand the practice, I resent it greatly, and try to avoid buying products from manufacturers that use these techniques.
"The Lion shall lie down with the Lamb;
but the Lamb will not get much sleep..."
Lazarus LongThis is a pet peeve of mine as well. I can understand tamper detecting seals on things like hard disk drives. There's really nothing constructive I could achieve by opening one. But on a PC? [conspiracy theory] with the brand name manufacturers now offering three year warranties it's an obvious attempt to lock the consumer in. You want a bigger hard drive? Great! We'll install it for you (else you void your warranty) and charge you a hundred bucks for the privilege. Oh, and you buy the drives we approve (ie, sell) at our price. Sweet! [/consipracy theory] :suss: Rob Manderson http://www.mindprobes.net
-
Let's see my fellow CPians can help me with that... Well... I'm working on a large project so I bought a new machine this week. The problem is that the machine is random rebooting. I use a small software to check the memory of the new machine (http://www.memtest86.com) and I figured out that some blocks of my memory are not working (before someone asks, the CPU is not overheating... I check it). I'll send the machine to the store on monday, but I have lot of things to do on the weekend for the project. Does anyone know a program that can block bad memory addresses !? I can identify the bad block with the test program... but I wasn't enable to block them on WinXP. I could try the VirutalAlloc funcion in a small app, but I think it adresses to the Process Virtual Address space... not the physical memory. Does anyone know some way to solve this !? :confused: Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter
English is not my native language so, if you find any spelling erros in my posts, please let me know.If you are using XP, go to control panels, system, startup and recovery. Uncheck the Restart on error box. Now you will get the BSOD instead of restarting, and you will be able to read the error message. Hope this helps.