BSODs Just Starting!

[computersplus]

sometimes you would need to reinstall after changing that

 

[imacken]

Yes well I spoke too soon. Another BSOD. The thing is, why should they stop if I just reinstall all the same stuff?

 

[computersplus]

if you run the setup again in IDE mode it will not corrupt upon install like I said I have seen a lot of issues when AHCI is used

 

[imacken]

Oh well, there goes a couple of evenings then!
BTW, why do you think the problems only started occurring in the last 2-3 weeks? Everything was fine for months before.
As I said in the OP - I think - the only thing that has changed is the install of Office 2010 beta.

 

[computersplus]

corruption worsen sometimes till you start seeing problems go through your event viewer logs and see how far back you have errors you would be shocked the errors that are going on behind the scenes

 

[imacken]

Thanks again. I've never used Event Viewer before. Where should I look in it, and what am I looking for?

 

[computersplus]

click on the start orb and in the search box type event viewer click on the link provided in the search results when it opens look at the Windows logs on the left then in the center window look at system events that's usually where the serious errors will be also check the application logs look for errors flagged in red post the event ID numbers

 

[imacken]

OK guys, just in case it's of interest, I haven't had any BSODs in the last week, and I haven't had to reinstall.

However, Western Digital informed me that the error when running their diagnostic WinDLG that was mentioned earlier in this thread was due to the software being incompatible with Windows 7!

 

[usasma]

While I favor W-D hard drives over any other brand, I must say that I am greatly disappointed by their software. I have issues with their diagnostics and with the software/formatting of their external drive products.

But I'm glad to hear that you're error free. Thanks for letting us know!

 

[imacken]

OK guys, I'm afraid I'll have to resurrect this thread.
After a week or so of no BSODs, they came back with a vengance - about twice a day!
So, I decided to bite the bullet and reformat and reinstall.
Well, that all went fine yesterday. Then today I got the BSOD!!!!
I'm getting stuff like 'BAD_POOL_HEADER', 'SYSTEM_SERVICE_EXCEPTION' and the old fave 'IRQL_NOT_LESS_THAN_OR_EQUAL'.
It seems to me like a hardware issue, but I've tested the RAM in memtest and MS Memory Diagnostics. I've scanned the HDDs using Scandisk and I've run Prime95 without any problems to test the CPU/RAM combo.
Any ideas?

 

[imacken]

click on the start orb and in the search box type event viewer click on the link provided in the search results when it opens look at the Windows logs on the left then in the center window look at system events that's usually where the serious errors will be also check the application logs look for errors flagged in red post the event ID numbers

OK, the BSODs are back. 2 today.

Event viewer shows red Event ID 7000, and text 'The PDIHWCTL service failed to start due to the following error: The system cannot find the file specified.'

It also shows Event ID 11, and text 'The driver detected a controller error on \Device\Harddisk4\DR4.'

How do I tell what is Harddisk4? In Computer Management, Disk4 shows up as my external drive. Would that be it?

Any ideas on that?