x BlueRobot
Closed by request
- Local time
- 11:31 AM
- Messages
- 6,784
Code:
[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff8800118d039, fffff880087b29c0, 0}
Probably caused by : fltmgr.sys ( fltmgr!GetContextFromStreamList+99 )
Code:
Usual causes: System service, Device driver, graphics driver, memory
Code:
0: kd> [COLOR="SeaGreen"]!thread[/COLOR]
GetPointerFromAddress: unable to read from fffff80002eb0000
THREAD fffffa8009b63060 Cid 0c64.06ec Teb: 000000007ef8c000 Win32Thread: fffff900c1ebdc20 RUNNING on processor 0
IRP List:
[COLOR="Red"] Unable to read nt!_IRP @ fffffa8007200010[/COLOR] <-- Pending IRP
Not impersonating
GetUlongFromAddress: unable to read from fffff80002defba4
Owning Process fffffa800a6bd710 Image: chrome.exe
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 21947
Context Switch Count 1273 IdealProcessor: 0 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x0000000065cae99d
Stack Init fffff880087b3db0 Current fffff880087b2970
Base fffff880087b4000 Limit fffff880087ab000 Call 0
Priority 12 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Code:
2: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start end module name
fffff880`056a2000 fffff880`061b8000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: [COLOR="Red"]Wed Dec 19 20:38:55 2012[/COLOR] (50D225DF)
CheckSum: 00AC6529
ImageSize: 00B16000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your AMD/ATI graphics card driver seems to be a possible cause in quite a few dump files, have you tried checking for updates from here - AMD Graphics Drivers & Software
Code:
[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]5100[/COLOR], fffff6fc40077a68, 5, 168d56963}
Probably caused by : partmgr.sys ( partmgr!PmGlobalDispatch+9f )
The bugcheck suggests that a virtual address is going to written to while it's already in use, this is also supported by a Stop 0xDA found in one of the crash dumps which indicates incorrect PTE handling by drivers.
My Computer
- Computer type
- Laptop