Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

This occurs just after I log into Windows 7 Home Premium.

Does any body what this means and how to resolve the issue?

share|improve this question
2  
This program may help...nirsoft.net/utils/blue_screen_view.html –  Moab Apr 8 '11 at 14:55
1  
Journeyman - I suggest it's not a duplicate since ben950's circumstances are different. He says bluescreen happens immediately after login, where as the linked-to question bluescreens happen randomly. –  Joshua Apr 8 '11 at 15:02
add comment

2 Answers

up vote 1 down vote accepted

This is likely a malfunctioning driver activated as it occurs after login, or do you experience randomness?

Please read this article to troubleshoot your BSOD, try to see if Safe Mode works and check the Event Log.

If you can get there, please upload the dump file so we can analyze for you which driver did this.


Edit:

Not checking the crash dump is trying to fix a problem without knowing what the problem is.

So, you can try to remotely obtain the crash dump file, it is located at one of these two paths:

  1. C:\Windows\MEMORY.DMP

  2. C:\Windows\Minidump\*.DMP

The best way would be to connect the hard drive to another computer...


Edit 2:

The driver that is crashing your computer multiple times is mfehidk.sys, from McAfee, your virus scanner.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.

Probably caused by : mfehidk.sys ( mfehidk+188e9 )

If we list the module, we get:

fffff880`03ab2000 fffff880`03afba00   mfehidk  T (no symbols)           
    Loaded symbol image file: mfehidk.sys
    Image path: \SystemRoot\system32\drivers\mfehidk.sys
    Image name: mfehidk.sys
    Timestamp:        Fri Jul 31 23:59:58 2009 (4A73695E)
    CheckSum:         0004F637
    ImageSize:        00049A00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It's April 2011 and that driver dates back to July 2009, that's horribly out of date for a virus scanner.

If you can get into safe mode you can try to remove the virus scanner, if not you could attempt to rename C:\Windows\System32\drivers\mfehidk.sys so that the operating system should not load it anymore.

There are ony two dumps mentioning the iastor.sys driver, which is related to your hard disk. This makes sense as either the virus scanner driver or the hard disk driver is accessing memory in such way that the other one can't write to it, as a virus scanner scans files but this one seems to do it too early...

See how both dumps have problems reading or writing the memory:

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx.
The memory could not be %s.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arg1: 00000000000007e1, memory referenced
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800112a4ff, address which referenced memory

So, the steps to take are:

  • Prevent the virus scanner from loading, with either safe mode or by renaming the driver.

    This will verify if the virus scanner is the culprit.

  • If it's not the virus scanner, do a error scan on your memory and hard disk.


Edit 3:

As you are crashing on the iastor.sys only now, I've looked at its date.

fffff880`010ba000 fffff880`011d6000   iaStor    Fri Jun 05 03:53:40 2009 (4A287AA4)

If I look at mine I see this:

enter image description here

So, updating your Intel Rapid Storage Technology drivers might fix your issue.

Uninstall any Intel Matrix RAID and Intel Rapid Storage Technology drivers first if possible...

share|improve this answer
1  
Or try Last known good config. Better bug check page here...msdn.microsoft.com/en-us/library/ff560129(v=VS.85).aspx... main page ...msdn.microsoft.com/en-gb/library/ff542347.aspx –  Moab Apr 8 '11 at 14:59
1  
@ben950: I can't open the MEMORY.DMP, but it's not necessary as the minidumps show the issue. –  Tom Wijsman Apr 11 '11 at 13:47
1  
Thank you very much it was to do with mcaffee which i am in the process of geting rid of i dont no why i actualy left it there. once again thankyou –  ben950 Apr 11 '11 at 13:57
1  
WinDbg, from the Debugging Tools for Windows, I use !analyze -v to get a lot of information and lm t to get the timestamps for the drivers, lm v gvies a lot more information but takes a long time. Make sure that you set your symbols right. –  Tom Wijsman Apr 12 '11 at 13:14
1  
Thanks My laptop seems to now be functioning without any blue screen once again thanks you –  ben950 Apr 13 '11 at 8:35
show 23 more comments

This is likely a hardware problem. It is very difficult to determine because it is a generic-enough message that it could be any number of subsystem components - graphics, CPU, memory failure, hard disk or controller, etc.

My first suggestion is to run Memtest, which will test the stability of the memory subsystem. Usually if you're able to get through this your CPU has a good chance of survival as well.

Next would be to see if Windows boots into Safe Mode, by hitting F8 before Windows starts up (just before the "Loading Microsoft Windows" appears on bootup). If you are able to successfully get into Safe Mode, you can start trouble-shooting other hardware components by enabling / disabling or uninstalling / reinstalling drivers.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.