Vista 32bit BSOD - Yet another one..

[Lichterflug]

I have run all the possible tests by now and it passes everything. Not a single error to be found..

 

[Lichterflug]

Here also my newest data. I already had three BSODs in one hour today. I really hope that anyone can help me out here.

 

[koolkat77]

I hope you don't mind posting on this thread.

Could you please upload a screenshot of your hard disk using crystal disk info:

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Forums

 

[Lichterflug]

OK, I can do that.

A friend adviced me to also use WhoCrashed. I did and got the following report. According to WhoCrashed it's more likely to be non-hardware related. I will post the report of the BSODs of this morning:

On Mon 29-10-2012 8:07:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102912-03.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x16EDE)
Bugcheck code: 0xC1 (0xFFFFFFFFC364CEE8, 0x0, 0x118, 0x22)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 29-10-2012 8:01:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102912-02.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCB473)
Bugcheck code: 0xC1 (0xFFFFFFFFFA092B70, 0x0, 0x490, 0x22)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 29-10-2012 7:56:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102912-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA74EF)
Bugcheck code: 0xC1 (0xFFFFFFFFFAB38F48, 0x0, 0xB8, 0x22)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Lichterflug]

This is its conclusion:

--------------------------------------------------------------------------------

40 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

mfehidk.sys
mfefirek.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

 

[koolkat77]

Who crashed is not as good as Windbg

I'm waiting for the screen shots.

 

[koolkat77]

Yes, McAfee causes BSODs very often. I've seen those in your dumps.

 

[Lichterflug]

But McAfee is already gone from my computer and the BSODs were also there before installing it, they were just called differently. Since about the time that I installed McAfee, I have with one exception only got the BSOD SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.

Those two drivers mfehidk.sys and mfefirek.sys do not seem to be "updateable". Do I need these at all or would it be a solution to delete/uninstall them?

Yes, I will make the screenshot as well.

 

[koolkat77]

Do you mean you still have its drivers in C:/Windows?

 

[Lichterflug]

When I search for them, I don't find anything..

By the way, I installed CrystalDiskInfo now. What exactly should I make a screeshot of?

 

[richc46]

Take a shot of the results. It will show if HD is good or bad. You will know it when you see it.

 

[koolkat77]

"Launch crystal disk info" and just post the screen shot of what shows up.
It should look something like the attached picture.



Check for motherboard/chipset drivers/onboard VGA drivers from the Intel Download Center.
Also look for a BIOS update for your PC.

Intel® Driver Update Utility

 

[Lichterflug]

Alright, I figured that I had to start some tests like with most other programs. Here it goes. It seems to be good.

 

[richc46]

As I thought it is probably not your HD. Those results are not too accurate however. If need be we will go to the website of the HD manufactuer and take a more definitive test, but I dont think that is necessary now. Let me look at your file and see what you have done so far.

 

[richc46]

We have to rely on the consistent results given initially, which says memory. Do you have a dual channel memory. Sometimes those results are not accurate when it says pass.

 

[Lichterflug]

It said Dual Channel when running Memtest86+, yes. But I don't really know what that means.

This WhoCrashed however points at driver conflicts as you might have read above.

 

[richc46]

Who crashed shows ntfs, which meas bad hard drive and it shows memory. NTFS is probably why KK asked for the crystal test.

 

[richc46]

How many ram sticks do you have?

 

[Lichterflug]

OK, but when it apparently points both at bad hard disk and bad memory and when testing them everything is said to be working fine, then this doesn't make much sense to me.

 

[Lichterflug]

How many ram sticks do you have?

Well, as I said before, when opening the memory part of my computer, I only found one part that I could take out, though it should be two, right?