Solved Lots of BSODs, different errors

[Veliremus]

Okay, that sounds reasonable... *sigh* Man, what a pain in the ass. But I guess I'll try that out, I agree it would be a good way of finding out whether it's software or hardware. Having got time today, but will start this adventure in a day or two. Cross your fingers for me .

Also, would you say I'd use the onboard audio? Because I'm pretty sure Windows automatically uses Creative drivers for that audiocard. Then again, the VIA audio is said be to notoriously sucky...

And what about enabling AHCI? Both my motherboard and HDD support it, and I guess I'd like to use the features it provides (namely NCQ). So do I enable it in the BIOS before beginning the install/format?

And lastly, I'm a loving the tutorials on this site, really fantastic! I wondered if there is one that details the order in which it would be best to install your driver (eg. motherboard first, then gfx card, then audio, etc). Can't seem to find it.

EDIT: FYI, I followed this guide:
http://www.sevenforums.com/tutorials/3413-repair-install.html

But now a friend is telling me that I should boot the DVD and choose Repair instead of running it from Windows. Maybe I should try that first?

EDIT2: Hm, doesn't seem to be such an option in boot. Guess I'll try to run the Repair Install like in the guide once more before trying a clean install.

EDIT3: Nope, again failed. Didn't get a message this time, but oddly enough, the Event Viewer shows a crash. And IE suddenly opened when I logged in.

 

[Veliremus]

So, interesting development, guys.

I wipe my partition, make new ones, format it, etc (all using Partition Wizard Boot CD). And I wanted the system to run on AHCI, so I enable it in the BIOS, both the Intel chipset and the Marvell controller. I try to install Windows, but I get a Disk Read Error. Later a PFN_LIST_CORRUPT when I tried again. Oh-oh. Turns out that putting the Intel back to IDE fixed it, but, long story short: eventually I physically trace the HDD SATA cable (I have a Cooler Master 690 Advanced II, which has cable management, so that's difficult to do) and guess what I find.....the HD is plugged into the regular SATA ports, and not in the Marvell! I totally missed this when I check last time. Apparently, it wasn't correctly installed by the webshop. Booting, now suddenly a Marvell display appears which confirms I've got a 1TB 6GB/s HDD plugged in.

So I try the Windows install again, and it freezes at 96%. But after I install the Marvell Controller (AHCI) driver in the Windows installation, it works. Of course, then I got to the unpleasant discovery that my product code didn't work (I thought you could just install Windows with the upgrade!) so I had to install XP first. Fun, fun, fun (read: killlll meeee!). After that, the Windows installation worked. I've got Windows running now.

It's interesting, isn't it? Maybe having the Marvell driver installed in Windows, but not having a disk on it, was causing the random BSODs? Anyway, it's on vanilla now, let's see how it works.

About operation Vanilla Install: how about the Windows Updates? Right now, I don't have any sound from my Creative. Also some sort of ATK update is available, and an Nvidia graphics driver. Are these the generic Microsoft drivers, or are they actual drivers? Should I install them?

(I'm making an image now, so I NEVER have to go through this again... Man, this literally took all day. My god.)

EDIT: Maybe I should switch to my normal onboard audio and see if that does get generic drivers? Because if I want to "mimic my normal behaviour", I'm going to at least need sound so I can use Spotify and watch movies.

 

[cybercore]

You can disable Creative or any other device in Control Panel -> System -> Device Manager.

Again, I'd be moving this way:

1. Clean install. As soon as done, do not install any drivers yet. Just go to Device Manager and disable any unknown devices and ones with the yellow marks next to them. Run your system this way for a couple of days. I know this is no fun - yes I do.

If crashes happen, you gotta hardware problem. Attach the .dmp's.

2. Next, install the drivers ensuring they are the end of 2009 or preferably the middle of 2010. + Install this BSOD-proof MSE. Run your system this way for a couple of days, see if any crashes and attach the .dmp's.

Now if it doesn't a single time crash on the system with generic drivers only but does on it with the drivers from manufacturers, it could be a driver then. Or yet a device.


Of course memtest, prime95, and hdd diagnostics would do the job but I guess you've run them already and they didn't detect any errrors. So now it's either a driver issue or a well hidden hardware problem.

Fingers crossrd, you know praying, and good luck. I'll be around.

 

[Veliremus]

Well, it's not so much that I'm having problems with the fun aspect (the fun aspect of working on this PC ended a few months ago, I just want to get it working properly ). I'm just saying it's hard to actually do stuff on my PC without sound, hehe. But okay, I'll try. But I've already installed MSE in this step, because I do need protection, right?

As for all those diagnostics, yeah, I ran them a lot. Especially memtest and HDD Diagnostics. But I'm sort of hopeful that both installing a clean Windows and switching to the Marvell controller will have fixed the problem.

I've got a couple of The Tudors episodes which I suppose I'll just continously run in the background. Can I install K-lite Codec pack, or would you advise against it?

Thanks for your tips, again .

 

[cybercore]

Well, that's why I'm saying I know how hard and depressing it is, but since any BSOD has in fact only two causes, hardware or drivers, and since you have sorted your drivers and run the diagnostics without errors yet, you need to locate the cause what's crashing you. So,

1. Clean install. As soon as done, do not install any drivers yet. Just go to Device Manager and disable any unknown devices and ones with the yellow marks next to them. Run your system this way for a couple of days. I know this is no fun - yes I do.

If crashes happen, you gotta hardware problem. Attach the .dmp's.

2. Next, install the drivers ensuring they are the end of 2009 or preferably the middle of 2010. + Install this BSOD-proof MSE. Run your system this way for a couple of days, see if any crashes and attach the .dmp's.

I don't think K-Lite will crash you, just get the latest if you need it. Probably gonna watch movies, cartoons, huh? ; )

 

[Veliremus]

I don't think K-Lite will crash you, just get the latest if you need it. Probably gonna watch movies, cartoons, huh? ; )

Yeah, I usually work on Google Docs (currently working on a review of Enslaved for PS3) with Family Guy or something in the background (Always on Top function in Mediaplayer Classic is very useful for that). I prefer watching series and movies on my PS3 (USB ftw), but since I can't play any games on this PC without proper drivers I'll just watch some on here, see how it goes .

But about that whole Marvell controller thing, do you see any way how that could explain the BSODs? I mean, it would be great if that had been the problem, 'cause that would mean actually properly using it now would fix the BSODs .

EDIT: Oh wait, I still can't watch stuff without sound, lol.

 

[Veliremus]

Status update: no BSODs so far. Of course, it's hard to simulate my usual behaviour (K-lite refused to show anything without a videocard driver and Spotify wouldn't play without an audiocard driver), but I've spent quite some time installing a lot of stuff, and no errors. So, one more day, and then I'm installing the drivers . Wish me luck!

 

[CarlTR6]

I do wish you luck!

 

[Veliremus]

Nope, it wasn't meant to be...

I didn't even start installing my drivers. I plugged in my old MyBook to load some backups unto. Deleted a lot of stuff there, whilst browsing through some images on my computer, and boom. MEMORY_MANAGEMENT BSOD.

I am royally screwed now, right? It must have been a hardware issue after all. Maybe it's the motherboard.

Ho man, I'm at the end of my wits now.

EDIT:

What about this, though? The sticks are supposed to be DDR3-1333, but when I was scanning with one stick in, I suddenly noticed that it's too high. Shouldn't that 1337 be 1333? And shouldn't that 2046GB be 2048GB?

http://img502.imageshack.us/img502/1899/ramweird.jpg

This isn't right, is it?

 

[Veliremus]

Okay, second stick also shows the same speeds.

I called the webshop, and they said that Asus and Corsair is a combination they recently recommend against. So, I'm sending the whole thing back, I guess.

 

[CarlTR6]

I am sure sorry to hear that you have to send the whole thing back; but it does look like you have found the problem. Please keep us updated.

 

[Veliremus]

Good news, they are replacing the memory with Kingston KVR1333D3N9K2/4G.

Whether they found an actual defect or just went with my extensive diagnostics remains to be seen, but hey, I don't care. I'm just glad I'm getting new memory.

 

[CarlTR6]

Absolutely! That is very good. Let us know how your system does with the new memory. I suspect they tested everything themselves.

 

[Veliremus]

Okay, the PC is back. Time will tell if the problem has been fixed. But sensor programs still say the memory runs at 668MHz instead of 667MHz, is that a problem?

 

[CarlTR6]

I am not a RAM expert by any stretch of the imagination. I suggest that you start a thread in the Hardware & Devices section. There are some really knowledge folks there about RAM and motherboards.

 

[Veliremus]

Cool, I'll do that.

In the mean time, I'll post back here to see if this RAM switching has finally solved the damn problem. *crosses fingers*

 

[CarlTR6]

Thanks much; we are looking forward to a good report.

 

[Veliremus]

As am I, man . As am I.

 

[Veliremus]

Okay, seems like the frequency difference is within the boundaries:
http://www.sevenforums.com/hardware-devices/124534-ram-frequency-indiscrepancy.html#post1075044

Good, will post back in a few days to see if my PC stays this way .

 

[CarlTR6]

Thanks for the update. And that is great news, the kind we like to hear!