We had a big talk re this issue today and our tech also had a long talk with the developers . Unfortunately they cannot find a cause as yet. I and ex_brit use both versions of win 7 and to date have not seen it on installations. There must be some common cause. They are still digging deeper into the issue sorry.
I am hitting this issue. please help. please find minidump file attached.
Brad can you post your operating system details as well as PC details please
brad_moreland wrote:
I am hitting this issue. please help. please find minidump file attached.
For information purposes only...
Attached Dump: 072410-31387-01.dmp
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02856000 PsLoadedModuleList = 0xfffff800`02a93e50
Debug session time: Sat Jul 24 11:40:29.807 2010 (UTC - 4:00)
System Uptime: 0 days 1:08:07.034
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8a0079b5000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88007ac3220, address which referenced memory
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afe0e0
fffff8a0079b5000
CURRENT_IRQL: 2
!thread
GetPointerFromAddress: unable to read from fffff80002afe000
THREAD fffffa8003b57680 Cid 0004.0030 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 1
Not impersonating
GetUlongFromAddress: unable to read from fffff80002a3cb74
Owning Process fffffa8003b45740 Image: System
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 261987
Context Switch Count 9093
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0xfffff800028d3750)
Stack Init fffff88002fdadb0 Current fffff88002fda690
Base fffff88002fdb000 Limit fffff88002fd5000 Call 0
Priority 12 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffff880`02fd9b48 fffff800`028c5b69 : 00000000`0000000a fffff8a0`079b5000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fd9b50 fffff800`028c47e0 : 00000000`00000000 fffff8a0`079b5000 00000000`00000000 00000000`000f0001 : nt!KiBugCheckDispatch+0x69
fffff880`02fd9c90 fffff880`07ac3220 : fffff880`07ab5315 00000000`00000000 fffff880`02fd9e70 fffffa80`03b57680 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`02fd9c90)
fffff880`02fd9e28 fffff880`07ab5315 : 00000000`00000000 fffff880`02fd9e70 fffffa80`03b57680 fffff800`02ba7e12 : mfehidk+0x50220
fffff880`02fd9e30 00000000`00000000 : fffff880`02fd9e70 fffffa80`03b57680 fffff800`02ba7e12 fffff880`02fda0c0 : mfehidk+0x42315
Loaded symbol image file: mfehidk.sys
Image path: \SystemRoot\system32\drivers\mfehidk.sys
Image name: mfehidk.sys
Timestamp: Fri Apr 23 13:33:40 2010 (4BD1D9F4)
CheckSum: 000877A2
ImageSize: 0007EA80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Passed link onto our techs for update, whoops sorry mark did not see you there passed onto Doug as well
Message was edited by: Peacekeeper on 25/07/10 8:54:34 AMhi, this issue has not been resolved yet. it's not a problem with windows 7 64 bit. It gives the same error even on 32 bit. seems the issue between toshiba and mcafee. this following thread has discussion about the situation: https://community.mcafee.com/message/142363#142363
Wasn't this descided to be an issue between Mcafee and the toshiba bios? Ok haven't been full on on this thread but I seem to remember something about that.
What version of mcafee are you on at the moment?
Latest that has a patch for a bsod (unsure so checking if it is this one) is 10.5.194 for security centre
prodipx wrote:
hi, this issue has not been resolved yet. it's not a problem with windows 7 64 bit. It gives the same error even on 32 bit. seems the issue between toshiba and mcafee. this following thread has discussion about the situation: https://community.mcafee.com/message/142363#142363
I posted on your other thread.
I have the same issue on a Packard bell laptop and Compaq both 64-bit win 7 both 6 months old it goes blue screen after a while as if the background scan has hit something? its fine on the basic AV package not the total protection product , which does it without fail. Its disgusting its not been fixed and still sold as 64-bit compatible, I wont be buying anymore mcafee products.
BUT its NOT just a Toshiba issue.
HTH
Well it works fine on my 64-bit systems, 2 Windows 7 and 2 Vista. Did you try Technical Support Chat?
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: