recovered from serious error

[7up7up]

hey guys, could any of you check what went wrong with my laptop?

twice it had blue screen within hours

the first one happened after updating my firefox to the latest, it was 2.0.0.18 if i'm not mistaken, then it went to blue screen and firefox can't be run. Replacing it with firefox 3.0 solves the firefox problem, but not the blue screen.

then while playing flash game in firefox, it went blue screen again

minidump files are attached, could someone check it and let me know what the problem might be?

thanks in advanced.

minidump.zip

[CoffeeFiend]

Looks like a problem with your hard disk. Could be the disk itself, the cable/connection or a number of other issues (bad drivers, etc). It would be a good idea to look at the SMART status, and perhaps running scandisk. Lots of possibilities, and it's hard for us to just guess.

[cluberti]

Unfortunately this is not a kernel or complete memory dump, so the IRP structure that would show the driver path is missing. However, most mountmgr crashes are either (as crahak pointed out) a faulty hard disk, or, more commonly in this case, a faulty chipset or disk driver. I would update whatever chipset drivers you have installed, or any RAID controller drivers (if that's what's in use).

Also, in some occasions, I have seen Symantec Antivirus' symtdi.sys driver cause this bugcheck as well (again, if I had the IRP stack, I would be able to gather more info than just a minidump), so if you have Symantec Antivirus or Norton Antivirus installed, removal as a test would also be a good thing to try.

kd> !thread
GetPointerFromAddress: unable to read from 8055f534
THREAD 82bc58b8  Cid 0004.0018  Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
IRP List:
	Unable to read nt!_IRP @ 823453b8
Not impersonating
GetUlongFromAddress: unable to read from 8055f544
Owning Process			82bc87c0	   Image:		 System
Attached Process		  N/A			Image:		 N/A
ffdf0000: Unable to get shared data
Wait Start TickCount	  22479709	 
Context Switch Count	  338060			 
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime				  00:00:00.000
KernelTime				00:00:00.000
Start Address nt!ExpWorkerThread (0x804e4729)
Stack Init f7c09000 Current f7c08990 Base f7c09000 Limit f7c06000 Call 0
Priority 13 BasePriority 13 PriorityDecrement 0 DecrementCount 16
ChildEBP RetAddr  Args to Child			  
f7c08860 80522325 0000007a c03de008 c000000e nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f7c08888 804fae18 8149f010 c03de008 f7802000 nt!MiWaitForInPageComplete+0x1c5 (FPO: [Non-Fpo])
f7c08900 804ec48a 2dd56860 f7802000 c03de008 nt!MiDispatchFault+0x2a3 (FPO: [Non-Fpo])
f7c08950 804e1ff1 00000000 f7802000 00000000 nt!MmAccessFault+0x5bc (FPO: [Non-Fpo])
f7c08950 f7801fff 00000000 f7802000 00000000 nt!KiTrap0E+0xcc (FPO: [0,0] TrapFrame @ f7c08968)
f7c089dc f7805de7 82b52f40 823453b8 00000103 MountMgr!MountMgrQueryDosVolumePath+0x3 (FPO: [Non-Fpo])
f7c089fc 804e3d77 82345428 82b52f5c 00000200 MountMgr!MountMgrDeviceControl+0xb7 (FPO: [Non-Fpo])
f7c08a0c 8052e753 000000c8 81ee7430 e2cd05e8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f7c08c5c 805e7940 82b77e30 e2cd05e8 6e446f49 nt!IoVolumeDeviceToDosName+0x155 (FPO: [Non-Fpo])
f7c08cc0 80615429 81ee7430 00000001 00000001 nt!IopQueryNameInternal+0x92 (FPO: [Non-Fpo])
f7c08cf0 80519af7 81ee7430 f7c08d28 80556d10 nt!IoQueryFileDosDeviceName+0x2e (FPO: [Non-Fpo])
f7c08d2c 804e54ad 82bc81f0 80561b40 82bc58b8 nt!CcWriteBehind+0x12e (FPO: [Non-Fpo])
f7c08d74 804e47fe 82bc81f0 00000000 82bc58b8 nt!CcWorkerThread+0x126 (FPO: [Non-Fpo])
f7c08dac 8057dfed 82bc81f0 00000000 00000000 nt!ExpWorkerThread+0x100 (FPO: [Non-Fpo])
f7c08ddc 804fa477 804e4729 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16