One more.. Can you see it.. Sorry..

Attached Files

Mini112006-01.dmp (88.0 KB, 3 views)

Hi,

You install KAV recently. Your latest maybe related to KAV as KAV can corrupt windows kernel memory. Refer this document and it may cause CPU_CALL_ERROR.






ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: b98322e4, Virtual address for the attempted execute.
Arg2: 0bcea963, PTE contents.
Arg3: b9832238, (reserved)
Arg4: 00000001, (reserved)

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: reader_sl.exe

TRAP_FRAME: b9832238 -- (.trap ffffffffb9832238)
.trap ffffffffb9832238
ErrCode = 00000011
eax=000000c0 ebx=8627fdd8 ecx=28640003 edx=28630002 esi=8651ac08 edi=00000000
eip=b98322e4 esp=b98322ac ebp=b98322a8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
b98322e4 0023 add byte ptr [ebx],ah ds:0023:8627fdd8=??
.trap
Resetting default scope

LAST_CONTROL_TRANSFER: from 80582832 to b98322e4
POSSIBLE_INVALID_CONTROL_TRANSFER: from 8058282d to 805b9e3a

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b98322a8 80582832 8627fdd8 8627fdc0 00000000 0xb98322e4
b98322a8 80582832 8627fdd8 8627fdc0 00000000 nt!IopDeleteFile+0x1b0
b98322e4 805b9e25 0027fdd8 00000000 8627fdc0 nt!IopDeleteFile+0x1b0
b9832300 805257b8 8627fdd8 00000000 00000044 nt!ObpRemoveObjectRoutine+0xdf
b9832318 805bacfb 86294da0 e1ebc3d0 8566bda8 nt!ObfDereferenceObject+0x4c
b9832330 805bad91 e1ebc3d0 8627fdd8 00000044 nt!ObpCloseHandleTableEntry+0x155
b9832378 805baec9 00000044 00000001 00000000 nt!ObpCloseHandle+0x87
b983238c f44b85cc 00000044 0012f110 8054060c nt!NtClose+0x1d
b98323b4 804e9b83 f7213ac8 e27b39e8 00000023 klif+0x195cc
b9832438 f72ef2ff 864fe918 f72eef3e 00001f80 nt!FsRtlLookupLargeMcbEntry+0xe1
b9832470 f7707d28 8657f030 00000000 b98324a4 atapi!CallIdeStartIoSynchronized+0x31
b9832480 806e7c4f 86536348 00000000 86543100 PCIIDEX!BmReceiveScatterGatherList+0x24
b98324a4 806e7e14 00000000 86536348 8654fad0 hal!HalBuildScatterGatherList+0x191
b98324d4 f7707ddb 865ab148 86536348 f721003c hal!HalGetScatterGatherList+0x26
b9832508 b98329b0 e27b3910 00000023 b983252c PCIIDEX!BmSetup+0x5f
b9832538 f72ed0f0 865349a0 86279048 f72ed187 0xb98329b0
b9832560 f72efcad 865349f8 00279008 09d85aa7 atapi!IdePortInsertByKeyDeviceQueue+0x42
b983258c 804eeeb1 8657f030 01279008 f735d5fc atapi!IdePortDispatch+0x4f9
b983259c f735d626 f7361e03 00000103 b98325d8 nt!IopfCallDriver+0x31
b98325a8 b98325d8 f735de1c 865e2008 862790c0 ACPI!ACPIDispatchForwardIrp+0x2a
b98325d8 804eeeb1 86553f18 f7372f8c 8627a220 0xb98325d8
b98325e0 f7372f8c 8627a220 f74c8061 00000000 nt!IopfCallDriver+0x31
b98325fc f74c7d58 8627a220 86543b70 85668d40 ACPI!AcpiFilterIrpDispatch
b983262c b98326d4 806e5427 badb0d00 00000000 CLASSPNP!ServiceTransferRequest+0xe4
b9832664 805a0771 b983271c b9832718 b9832964 0xb98326d4
b98326c0 bf85bcdf 00000042 b983272c 00000068 nt!KeUserModeCallback+0x87
b9832948 bf85bdea b9832964 0000af15 00000000 win32k!ClientLoadLibrary+0xb2
b9832b78 bf80d10c 00000000 00000000 e1fc3ab8 win32k!xxxLoadHmodIndex+0x86
b9832b94 bf840e69 b9832ce0 e1fc3ab8 b9832ce0 win32k!xxxLoadUserApiHook+0xa6
b9832c6c bf83ef0d 00000100 00000000 bc674610 win32k!xxxCreateWindowEx+0x461
b9832d20 8054060c 80000000 b9832cec b9832ce0 win32k!NtUserCreateWindowEx+0x1c1
b9832d20 7c91eb94 80000000 b9832cec b9832ce0 nt!KiFastCallEntry+0xfc
0012fd88 00000000 00000000 00000000 00000000 0x7c91eb94

STACK_COMMAND: .trap 0xffffffffb9832238 ; kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
---------
*** Possible invalid call from 8058282d ( nt!IopDeleteFile+0x1ab )
*** Expected target 805b9e3a ( nt!ObIsObjectDeletionInline+0x0 )

Another..
Thank's

Attached Files

	Mini112106-01.dmp (88.0 KB, 3 views)
	Mini112106-02.dmp (88.0 KB, 2 views)
	Mini112106-03.dmp (88.0 KB, 2 views)

Hi,

Two minidumps are crashed with bugcheck code FC and they are exactly the same as the previous crash. One minidump is crashed with memory error.

Mini112106-01.dmp BugCheck FC, {bac07ca4, 3aa85963, bac07bf8, 1}
Owning Process 862466f0 Image: avp.exe
Probably caused by : hardware

Mini112106-02.dmp BugCheck 1000008E, {c0000005, bf81439a, 9ecde6e8, 0}
Owning Process 854912e8 Image: Steam.exe
Probably caused by : win32k.sys ( win32k!RGNOBJ::bCopy+1c )

Mini112106-03.dmp BugCheck FC, {b910bca4, 21c77963, b910bbf8, 1}
Owning Process 85c38788 Image: avp.exe
Probably caused by : hardware

I've changed the memory's with one friend and i don't had BSOD.. Today a put my and i have two..

Attached Files

	Mini112506-01.dmp (88.0 KB, 2 views)
	Mini112506-02.dmp (88.0 KB, 2 views)

Hi

I don't understand what you mean
>>>
Today a put my and i have two..
<<<<

looks like he meant that he replaced his RAM with some he got from a friend and he didnt get anymore BSOD's.

Then, he put his own ram back in and got two more BSOD's.

I think its fairly safe to say that the problem is two bad sticks of ram.

You should replace your ram with new sticks.

Sorry cpc2004.. CrashVector is correct..

Another..
Thank's

Attached Files

	Mini112606-01.dmp (88.0 KB, 1 views)
	Mini112606-02.dmp (88.0 KB, 1 views)
	Mini112606-03.dmp (88.0 KB, 1 views)

Hi AFCB,

The culprit is faulty ram and Kaspery Anti-Virus.

Ok.. I'll buy memory's and after i'll reply..
Thank's for everything

I've bought a memorys.. I've instaled yeasterday.. Let's see if are everything allright.

BSOD.. Any advices?

Attach the latest minidump.

Here it is

Attached Files

	Mini120706-01.dmp (88.0 KB, 3 views)
	Mini120906-01.dmp (88.0 KB, 2 views)

KAV isn't the problem.. I've desinstalled and i had another BSOD.. What shall i do?

Another BSOD..

Help plz..

The stack trace of the latest 2 minidumps still have the footprint of KAV.

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
ae6dec68 80582832 85785998 85785980 00000000 0xae6deca4
ae6dec68 80582832 85785998 85785980 00000000 nt!IopDeleteFile+0x1b0
ae6deca4 805b9e25 00785998 00000000 85785980 nt!IopDeleteFile+0x1b0
ae6decc0 805257b8 85785998 00000000 00000f78 nt!ObpRemoveObjectRoutine+0xdf
ae6decd8 805bacfb 861a8250 e2909ce8 8649e020 nt!ObfDereferenceObject+0x4c
ae6decf0 805bad91 e2909ce8 85785998 00000f78 nt!ObpCloseHandleTableEntry+0x155
ae6ded38 805baec9 00000f78 00000001 00000000 nt!ObpCloseHandle+0x87
ae6ded4c f44545cc 00000f78 03b1fe00 8054060c nt!NtClose+0x1d
ae6deddc 805450ce f71ecb85 855ac180 00000000 klif+0x195cc <--- Kav
ae6dede0 f71ecb84 855ac180 00000000 0020027f nt!KiThreadStartup+0x16
ae6dede4 855ac180 00000000 0020027f 7c920000 NDIS!___PchSym_+0xc
ae6dede8 00000000 0020027f 7c920000 00000000 0x855ac180

I'm formatting now..

Another BSOD..

Attached Files

Mini121206-01.dmp (88.0 KB, 2 views)

Your windows does not have KAV and it crashes at win32k.sys. Probably it is related to video card display driver or faulty video card. Your nVidia Video Card Driver is quite current. Maybe it is unstable. Downgrade your nVidia Card Driver to previous level.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e373c000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf8cac70, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: e373c000

FAULTING_IP:
win32k!Misoriented+24b
bf8cac70 8b048a mov eax,dword ptr [edx+ecx*4]

MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
LAST_CONTROL_TRANSFER: from bf8ca505 to bf8cac70

STACK_TEXT:
babcf844 bf8ca505 00000000 000000fa 000010c5 win32k!Misoriented+0x24b
babcf8d0 bf8a548c e37382a8 e37382a8 e37372bc win32k!fsg_CheckOutlineOrientation+0x592
babcf908 bf8a4acc e3737248 e37382b8 e3739a48 win32k!fsg_ExecuteGlyph+0x15f
babcf964 bf8a4989 e3737248 e3739a48 e37382a8 win32k!fsg_CreateGlyphData+0xd5
babcf9a4 bf8a4f37 e3737248 e3739a48 e37372bc win32k!fsg_GridFit+0x4d
babcfa1c bf8a1e96 00000001 babcfa38 bf8a1ec8 win32k!fs__Contour+0x28b
babcfa28 bf8a1ec8 e3737010 e3737074 babcfb44 win32k!fs_ContourGridFit+0x12
babcfa38 bf9796a4 e3737010 e3737074 00000058 win32k!fs_NewContourGridFit+0x10
babcfb44 bf97987b 00000000 00000058 babcfc40 win32k!lGGOBitmap+0x74
babcfb6c bf8a48eb e33e1840 00000058 babcfc40 win32k!ttfdGlyphBitmap+0x60
babcfb94 bf8a46db e10b6d08 00000009 00000058 win32k!ttfdQueryFontData+0xff
babcfbe0 bf8a1664 00000000 e10b6d08 00000009 win32k!ttfdSemQueryFontData+0x45
babcfc10 bf950b48 00000000 e10b6d08 00000009 win32k!PDEVOBJ::QueryFontData+0x3c
babcfcc4 bf9475b7 e10b6d08 00000000 00000006 win32k!GreGetGlyphOutlineInternal+0x474
babcfd3c 8054060c c7010d34 00000075 00000006 win32k!NtGdiGetGlyphOutline+0x85
babcfd3c 7c91eb94 c7010d34 00000075 00000006 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e55c 00000000 00000000 00000000 00000000 0x7c91eb94

nv4_disp.dll Mon Oct 23 05:02:50 2006 (453BDC7A)

It appeard the BSOD "MULTIPLE_IRP_COMPLETE_REQUESTS"..
I don't have a minidump because the error was before starting windows..

EDIT: If the BSOD appear's out of windows, the problem isn't the drivers, right? Or not?