Major BSODs

Just minutes ago, while I was browsing the net, the computer BSODed, first with an 0x50 page fault in non paged area. The surprising thing about it was that it did not create a dump file or even begin to do so. I hit the restart button and was faced with another BSOD of 0x07 (I think), and it didn't create a dump file either, but it did list the CI.dll at the bottom.

Hitting the restart again didn't get even that far, because all that happened was that the fans turned and the component light internal to the case lit, but the monitor remained black as though it was getting no signal, but with no message to that effect.

I'm fairly certain that this is going to require a major breakdown and diagnosis to solve, but the fact that what I Googled seemed to indicate that the CI.dll is associated with a BHO of the adware variety and the fact that I indeed was using FF, and that the BSOD occurred the very instant that I clicked on a button on pcidatabase.com, seemed a bit coincidental to be nothing more than a regular hardware failure of some kind.

I know that no one can offer any advise on how to directly solve the problem, without more information that I won't have until later, but on the off chance that this rings any bells, I would sure like to hear what they say?

Sounds like the memory has gone bad. Once that happens the system will not even post because it doesn't see any usable memory in the system.
If you can remove all but one stick of memory and then switch it around the slots then try a different stick doing the same and see if you can get it to post.

I knew that there was some reason that I posted this question, despite the fact that I didn't expect an answer, or at least one that worked, but you hit the nail on the head. I pulled 3 sticks and it started right up. You save me a lot of work and headaches. Now I have to learn which stick(s) or slot(s) are bad. Thank you kindly.

seekermeister said:

I knew that there was some reason that I posted this question, despite the fact that I didn't expect an answer, or at least one that worked, but you hit the nail on the head. I pulled 3 sticks and it started right up. You save me a lot of work and headaches. Now I have to learn which stick(s) or slot(s) are bad. Thank you kindly.

You are Welcome.

I played musical chairs with the RAM, until I narrowed the problem down to the second black slot. So I guess that I'll have to live with only 3 sticks of RAM, until I upgrade the system. The bright side of all of this, is that it does give me just one more reason to justify the expense.

This problem kind of makes me question the usefulness of either Memtest86 or the Windows Memory Diagnostic, because I had used both of them only 2 days before this occurred and they didn't provide a clue that this was in the offing. I suppose that might have been more likely to have been the case, if it was actually a RAM stick that failed, rather than the RAM slot though.

essenbe said:

Seekmeister, you have my sympathy. I went through the same issue with my board. when I ran memtest I showed numerous errors-later to be determined it came from slots 3&4. I ran the sticks in almost every configuration. After running memtest at least 10 times (10 hours each test) I could run any 1 stick in any slot with no errors, however no matter whick stick I ran, if slots 1&2 were populater 3 or 4 would show errors. I contacted MSI technical support. They did not know as much about the board as I did. I was told I needed to upgrade my CPU. When I told him I was running a PhenomIIx6 and asked what CPU he would suggest, he hung up. After RMAing the new board, 8 weeks later I received a used board that someone else had RMAd with similar problems. They have refused to respond to me now. I contacted G Skill and had wonderful results. They RAMd the ram several times and even sent me different types of ram to try-at no additional cost. With G Skill help, I finally have a stable but troubled board. Just a suggestion, Try Corsair tech support and see what advice they can give you. Just a suggestion, maybe you can work around the problem.

You learned the hard way, just I had, not to touch a MSI motherboard with a 10 foot pole. Even if their tech support was any good, their motherboards are not. I have been told that other components that they make are good, but I doubt that I will ever know, because once burned, I tend to keep my fingers away from the fire.

EDIT: I can't blame Asus for this, because this motherboard is becoming vintage, and I bought it second hand on eBay a couple of years ago. Under the circumstances, it has done fairly well.

seekermeister said:

This problem kind of makes me question the usefulness of either Memtest86 or the Windows Memory Diagnostic, because I had used both of them only 2 days before this occurred and they didn't provide a clue that this was in the offing. I suppose that might have been more likely to have been the case, if it was actually a RAM stick that failed, rather than the RAM slot though.

Right Memtest test the RAM not the slots it in