(no subject)

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xc0000005, 0x004ea8a6, 0xf895ca20, 0xf895c720). A dump was saved in: F:\WINDOWS\Minidump\Mini030304-01.dmp.

This is with only the boot drive, not the storage drive, all drivers updated. FUCK.

I'm getting very tempted to see what the monthly payment would be on a FalconNW Fragbox or something similar.

(no subject)

The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xdd8fdde9, 0x00000001, 0xf4845356, 0x00000000).

Man, I wish this actually helped me solve the damn problem.

[Job Search]

Talked a bit with my contact at RHT, he's working on getting me an interview with one strong candidate, and put me in contact with two of their placement managers in Dayton and Chicago. We'll see how that works out. The Dayton guy was out of his office, but I talked to a lady in Chicago and we hit it off fairly well. (In fact, she mentioned that she got helpdesk support stuff fairly frequently, so let's cross fingers.)

buschap, I passed on your info to him as we discussed, and he said he'd try to call and speak to you today if at all possible.

(no subject)

Well, that was a fun and busy afternoon. But, 2 hours until it's over.

I think I have a plan (tm) for my computer. I know when I ran memcheck before, it didn't see anything, but that was also with at least 2 other problems. (Since the HDD and videocard replacement seem to have removed the major system error/device driver problem. Yay for apparently 3 things failing at once.) So, I've downloaded the latest version as well as Microsoft's equivalent, and will run them when I get home.

If, as I'm starting to suspect, the memory does not check out, I'm going to contact Kingston about an RMA, and see if my grandparents would mind helping with a (smaller) replacement stick in the meantime. (The problem with a DDR only board is that we don't keep DDR around the office that I could take home for helping with troubleshooting. Otherwise, my boss actually offered to give me a 256 stick of PC133 to use.)

I've also learned not to go around with all your memory on one stick. Redundancy good.

If this all works out how I think it will, hopefully this is the light at the end of the tunnel.

(no subject)

Something else, here.

I want to apologize to everyone for my bad mood of late. I really am going to try and work on it.

(no subject)

I am going to (very, very, very cautiously) predict that I may have found a very little detail that might just have solved the problem.

You see, the AGP slot on my board has one of those push-down to lock latches for the card. It happens to be right below DIMM0, where my memory resides.

After the memory test didn't show anything obvious, Jeremy G. suggested I try reseating the memory in case something got loose when I installed the AGP card.

So far, I've been up for a half an hour with no problems, and I'm crossing my fingers. If this does it, it means the video card was the only real problem, and I bought myself my own trouble for the rest, but it's okay, because I probably needed the wipe/reinstall anyhow.

(no subject)

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf49068de, 0xf4f99bbc, 0x00000000). A dump was saved in: \WINDOWS\Minidump\Mini030304-03.dmp.

I need to stop saying I think I have this figured out.

But, I stayed up for over 40 minutes, which was damn near a record since this problem started.

(no subject)

Well, I changed the memory slot, and that got most of it, I think.

But, I also now know exactly what causes that device driver error: Star Wars Galaxies. It appeared right after I installed it and DirectX 9.0a, and disappeared after I uninstalled and then updated to DX 9.0b.

I think that tomorrow I may try installing SWG again without DX 9.0a, and see what happens, but for now, I'm gonna do some bare-bones basic restoration stuff, and then sleep.

If SWG doesn't work, that'll kinda annoy me, but I don't think there's much I can do.