IRQL_NOT_LESS_OR_EQUAL blue screen

Anonymous

i just got 2 blue screens again... they just pop up every time i play 3D Games :\

But i just updated my Video Drivers :S

and these codes don't help me at all

i also checked the dump files with BS View

red are: portcls.sys, p17.sys, ntkrnlpa.exe, halmacpi.dll,

and on the other dump: ntkrnlpa.exe, win32k.sys

even got a dump with: dxgmms1.sys but that was before installing new video drivers, didn't get that one since :\ also cdd.dll

i hope anyone can help me

OS: Windows 7 86x

BCCode: 1000008e

BCP1: C0000005

BCP2: 9E4E6F00

BCP3: A1D2F724

BCP4: 00000000

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

BCCode: d1

BCP1: B4F05950

BCP2: 00000007

BCP3: 00000001

BCP4: 91DC475D

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Hi,

I'll reply in English here.

the PAGE_FAULT_IN_NONPAGED_AREA (50) is caused by the AVG driver:

Image path: \SystemRoot\system32\DRIVERS\avgntflt.sys

Image name: avgntflt.sys

Timestamp: Fri May 07 14:28:31 2010

Try to get an Update for AVG.

the KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) happens while GDI operations, so update the graphic card driver:

ChildEBP RetAddr Args to Child

a1d2f7b8 9e4fa20e a1d2fcfc a1d2fb50 000004e8 win32k!ESTROBJ::vCharPos_H1+0x99

a1d2f7f0 9e4facfa ffbbe050 0000000b a1d2fcfc win32k!ESTROBJ::vInit+0x1d8

a1d2fb38 9e46af67 a1d2fcfc 0000004e 0000006a win32k!GreExtTextOutWLocked+0x62f

a1d2fbb4 9e4cfb07 02cccccc ffbbe068 00001004 win32k!GreBatchTextOut+0x1e6

a1d2fd24 82c4f3ec 000000c9 01ee8b70 01ee8b80 win32k!NtGdiFlushUserBatch+0x123

a1d2fd34 776c64f4 badb0d00 01ee8b70 00000000 nt!KiFastCallEntry+0xcc

Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys

Image name: atikmdag.sys

Timestamp: Wed Sep 29 03:37:54 2010

the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) crash is caused by this driver:

Image path: \SystemRoot\system32\drivers\P17.sys

Image name: P17.sys

Timestamp: Fri Oct 16 04:11:53 2009

So update the soundblaster live card driver.

The other crashes are too old. They should be fixed with the newer drivers.

André

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

0 comments

46 additional answers

Anonymous

2010-11-18T00:18:04+00:00

This is not good. If you do OC, undo it. If you run at stock level, get a new CPU.

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
Was this answer helpful?

0 comments No comments
Anonymous

2010-11-17T11:51:30+00:00

Well.. seems like i didn't have to run it for a few hours =(

Result after 15 SECONDS...

http://www.imagebanana.com/view/2ap3ptqc/prime95.png

doesn't look too good huh? =(

tho i chosed a different test now ( with L2 check etc.. ) :\

argh.. does that mean it could by my CPU, RAM or Power Supply? :|

okay.. it sure is my RAM, CPU or Power Supply :|

Final Result:

http://img5.imagebanana.com/img/t5cno1zf/result.png

oh sh**t...

tho i wonder why my pc doesn't crash on 2D Games.. :| even if there's much stuff going one .. sure it's less work for the CPU but 3D games are more GPU intensive than CPU intensive :\ argh... it's getting so confusing and i don't want to buy new parts that are actually still working >_< like i buy a new CPU and then still get BSoD's because that wasn't the problem and something else caused the cpu calculating problems ;_; argh..

waiting for a new advice : <

[Wed Nov 17 11:27:52 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 11:40:34 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 12:48:13 2010]

FATAL ERROR: Rounding was 0.484375, expected less than 0.4

Hardware failure detected, consult stress.txt file.

[Wed Nov 17 12:58:26 2010]

FATAL ERROR: Rounding was 0.5, expected less than 0.4

Hardware failure detected, consult stress.txt file.

edit:\

Error on both CPU cores now :|

http://img5.imagebanana.com/img/45eth68d/omg.png

omg.. :\
Was this answer helpful?

0 comments No comments

Anonymous

use memtest86+. The Windows tool is not very good.

the latest crash has this exception:

//

// MessageId: STATUS_ILLEGAL_INSTRUCTION

//

// MessageText:

//

// {EXCEPTION}

// Illegal Instruction

// An attempt was made to execute an illegal instruction.

//

#define STATUS_ILLEGAL_INSTRUCTION ((NTSTATUS)0xC000001D L)

So also run Prime95 to test your CPU for errors.

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

[Wed Nov 17 11:27:52 2010] FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file.

Worker #1 ( CPU 0 ) stopped working pretty quick ( after like 5 minutes )

worker #2 ( CPU 1 ) is still running

edit:\ bluescreen again because of my soundblaster drivers.. omg =..

been playing a game to test the stability for like... 2 1/2 hours now - no crash no lag ( usualy its 10-15min max! ) then i thought fine - let's tab out :| - i wrote 3 lines of text and tada blue screen =..

not a new one tho - already had this before it's a d1 again:

i'll let the CPU test run for a few hours now and see what happens.

Crash List Created by using BlueScreenView

Dump File	Crash Time	Bug Check String	Bug Check Code	Parameter 1	Parameter 2	Parameter 3	Parameter 4	Caused By Driver	Caused By Address	File Description	Product Name	Company	File Version	Processor	Full Path	Processors Count	Major Version	Minor Version
111710-19936-01.dmp	17.11.2010 12:37:52	DRIVER_IRQL_NOT_LESS_OR_EQUAL	0x000000d1	0x0000ce8d	0x00000007	0x00000001	0x91c0fe75	P17.sys	P17.sys+d74a	WDM Audio Miniport (Basic) Driver		Creative Technology Ltd.	5.12.01.2016	32-bit	C:\Windows\Minidump\111710-19936-01.dmp	2	15	7600

0 comments

Anonymous

2010-11-17T01:24:55+00:00

use memtest86+. The Windows tool is not very good.

the latest crash has this exception:

//

// MessageId: STATUS_ILLEGAL_INSTRUCTION

//

// MessageText:

//

// {EXCEPTION}

// Illegal Instruction

// An attempt was made to execute an illegal instruction.

//

#define STATUS_ILLEGAL_INSTRUCTION ((NTSTATUS)0xC000001D L)

So also run Prime95 to test your CPU for errors.

"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
Was this answer helpful?

0 comments No comments