Applies to

bsod on pc, minidump files are given on skydrive and html code for skydrive below

manpreetsamrao asked on
<iframe src="" width="98" height="120" frameborder="0" scrolling="no"></iframe>

pls tell as fast as possible

pc specs:

amd athlon 270 dual core processor
2 gb ddr3 ram
digilite 960gsm series motherboard
320gb hdd

skydrive link for dmp files
1 person had this question

Abuse history

The answered status icon Answer
Patrick Barker replied on

We have various different bug checks:


This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

If we take a look at the call stack:

1: kd> kb
*** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr  Args to Child             
WARNING: Frame IP not in any known module. Following frames may be wrong.
89156a7c 8e2324e7 00000000 828216ee 89156af0 0x7a26c0ed
89156a94 8e678e50 8599c980 89156af0 860998d8 atikmdag+0xf4e7
89156abc 8e679018 89156af0 89156ad8 8e72f0d5 dxgkrnl!DXGADAPTER::DdiSubmitCommand+0x49
89156ac8 8e72f0d5 86096000 89156af0 89156b64 dxgkrnl!DXGADAPTER_DdiSubmitCommand+0x10
89156ad8 8e7384ea 89156af0 86099c10 86099000 dxgmms1!DXGADAPTER::DdiSubmitCommand+0x11
89156b64 8e75f617 0000000d 86291ca0 86099c10 dxgmms1!VidSchiSendToExecutionQueue+0x7d6
89156bdc 8e75ff87 860b5788 00000001 86291ca0 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x115
89156d18 8e76022f 00291ca0 862a5008 89156d3c dxgmms1!VidSchiSubmitRenderCommand+0x809
89156d28 8e7604cc 86291ca0 8288f3f1 860b5788 dxgmms1!VidSchiSubmitQueueCommand+0x61
89156d3c 8e760573 860b5788 00000000 860a0d48 dxgmms1!VidSchiRun_PriorityTable+0x24
89156d50 82a6166d 860b5788 a0567f53 00000000 dxgmms1!VidSchiWorkerThread+0x7f
89156d90 829130d9 8e7604f4 860b5788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


Various Direct X MMS routines and then an atikmdag.sys call right before the bug check (AMD/ATI video driver).


This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

BugCheck 7F, {d, 0, 0, 0}

The 1st parameter of the bug check is D or 0x0000000D -- An exception not covered by some other exception; a protection fault that pertains to access violations for applications.


This is issued if a driver attempts to write to a read-only memory segment.

-- PROCESS_NAME:  avgcsrvx.exe

^^ Process in relation to AVG.


This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.


1. Remove and replace AVG with Microsoft Security Essentials for temporary troubleshooting purposes:

AVG removal -


2. Ensure you have the latest video card drivers via the manufacturers website. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

3. Update to Service Pack 1 ASAP:


Debugger/Reverse Engineer.
Be the first person to mark this helpful

Abuse history

The answered status icon Answer
Patrick Barker replied on

Great, please do so and keep me updated. For reference your RAM and Motherboard don't look like they currently have anything to do with the crashes, but we shall see.


Debugger/Reverse Engineer.
Be the first person to mark this helpful

Abuse history