Saturday, June 6, 2009

Bad RAM

I had a Dell Vostro 1720 with bad RAM. It gave me a message when I turned it on that said "resource conflict- allocation error 0x02." Then when Windows XP tried to start it would either bluescreen or say that the file C:\Windows\System32\Config\SYSTEM was corrupted and that I would need to run the repair program on my Windows XP CD.

Fortunately, I was able to run the Dell diagnostics program and it told me that my RAM was bad. But the behavior was peculiar and unexpected- I thought it had a bad hard drive!
at No comments:
Subscribe to: Posts (Atom)

We Need to Teach Critical Thinking Again

One thing most people don’t realize about tech people that are roughly my age (plus or minus five years, let’s say) is how many of the dark ...

  • Crackling sound in Virtualbox
    I had a problem with crackling sound after upgrading Virtualbox to v5.2, similar to the bug report filed here .  I found a forum post where ...
  • Putty crashing on Windows 10
    Using a dynamic proxy in Putty, I was encountering an issue where Putty would crash in Windows 10.  I got an error in the Application event ...
  • Guide to using GPS with Airodump CSV Tools
    There is an Android app included that will capture GPS coordinates from your Android device and save them to a file. Airodump CSV Tools will...