TechSpot

Other BSOD problem

By AFCB
Nov 11, 2006
  1. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Hi

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

    CrashVector TS Rookie

    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.
     
  3. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    Sorry cpc2004.. CrashVector is correct..

    Another..
    Thank's
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Hi AFCB,

    The culprit is faulty ram and Kaspery Anti-Virus.
     
  5. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

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

    AFCB TS Rookie Topic Starter Posts: 29

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

    BSOD.. Any advices?
     
  7. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Attach the latest minidump.
     
  8. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    Here it is
     
  9. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

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

    Another BSOD..
     
  10. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    Help plz..
     
  11. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    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
     
     
  12. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    I'm formatting now..
     
  13. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    Another BSOD..
     
  14. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    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)
     
  15. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    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?
     
  16. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    After you re-install windows, is your windows more stable than before? Bugcheck 44 may be related to hardware or software. Without the minidump, I can't help you.
     
  17. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    I thing it is in the same..
    I'll try to have a minidump

    EDIT: BSOD today

    EDIT2: I can't run the "check errors on hard drive".. Is the HD the culpit?

    EDIT3: Other..

    EDIT4:haha: :Sometimes i play CS and the game is like this: http://img113.imageshack.us/my.php?image=semttulocm2.jpg
    Is the graphic card the culpit?
     
  18. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Hi AFCB,

    I think your windows is more stable as if you only 4 system crashes between 14 to 19. Three windows crashes are related to bdfsdrv.sys and it is BitDefender Internet Security software. You install this software recently. If you keep on installing new software, you have to make sure that they are stable. The CPU_CALL_ERROR is still unresolved . Probably the problem maybe related to motherboard as the crash instruction is consistent. Upgrade the BIOS of your motherboard. If your windows is still crashed with CPU_CALL_ERROR, replace the motherboard.

    Debug report
    Mini121406-01.dmp BugCheck 44, {855f5648, d62, 0, 0}
    Probably caused by : bdfsdrv.sys ( bdfsdrv+ff2 )

    Mini121606-01.dmp BugCheck 10000050, {e3f0b000, 1, ac993ddb, 1}
    Probably caused by : kmixer.sys ( kmixer!Convert16+db )

    Mini121906-01.dmp BugCheck 44, {863e9e28, d62, 0, 0}
    Probably caused by : bdfsdrv.sys ( bdfsdrv+ff2 )

    Mini121906-02.dmp BugCheck FC, {b97a57d8, 1d564963, b97a572c, 1}
    Probably caused by : hardware (probably it is related to faulty m/b or bdfsdrv.sys)

    Edit: Your nVidia Display Card Driver may have software problem as I have several opened cases relating to this version of nVidia Display Card Driver. Their symptom looks like memory corruption. If your windows does not crash at safe mode, probably video card driver is the culprit as safe mode uses MS graphical driver.
     
  19. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    I install new software because i have to have a anti-virus and a firewall..
    The motherboard is the third, and isnt the same model before..
    What shall i do?

    Thank's for all help
     
  20. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    Two more.. What shall i do?

    EDIT: I can't go in safe mode...
     
  21. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    Shall i change HDD?
     
  22. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Hi AFCB,

    Can you give me a summary what software and hardware change of your PC at this month (ie RAM, motherboard and etc)?
     
  23. AFCB

    AFCB TS Rookie Topic Starter Posts: 29

    This mouth? Nothing, i think..
    But in the past i've changed RAM, PSU, Motherboard..
    Software i think it was only internet securitys..
    Thank's for the help
     
  24. cpc2004

    cpc2004 TS Evangelist Posts: 2,044

    Hi,

    Your windows are still crashed with hardware error. Probably your motherboard is incompatible with the ram or BIOS is not up-to-date.
    Your windows have two device drivers with unstable version which causes blue screen. They are nVidia Display Card Driver and nVidia network resource manager. Upgrade or downlevel the above modules.

    According to the stack trace of the minidumps, your windows crashes after deleting files. I am not sure whether your version of Internet Security is stable or not. Maybe the crash is related to internet security.

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    bab3f504 80582832 858fae68 858fae50 00000000 0xbab3f540
    bab3f504 80582832 858fae68 858fae50 00000000 nt!IopDeleteFile+0x1b0
    bab3f540 805b9e25 008fae68 00000000 858fae50 nt!IopDeleteFile+0x1b0
    bab3f55c 805257b8 858fae68 00000000 00000490 nt!ObpRemoveObjectRoutine+0xdf
    bab3f574 805bacfb 858d11d0 e18d5c88 864c6860 nt!ObfDereferenceObject+0x4c
    bab3f58c 805bad91 e18d5c88 858fae68 00000490 nt!ObpCloseHandleTableEntry+0x155
    bab3f5d4 805baec9 00000490 00000001 00000000 nt!ObpCloseHandle+0x87
    bab3f5e8 ba2b89d7 00000490 bab3f604 0118ea34 nt!NtClose+0x1d
    bab3f638 80535171 bab3f6a4 00000000 bab3f7cc bdrsdrv+0x9d7
    bab3f6c0 8054060c bab3f7f0 bf986924 bf98fe00 nt!ExAcquireResourceExclusiveLite+0x67
    bab3f6c0 ffffffff bab3f7f0 bf986924 bf98fe00 nt!KiFastCallEntry+0xfc
    bf986924 00000000 ff909090 98b35825 909090bf 0xffffffff

    Boot into safe mode and run it for a whole day . If your windows does not crash at safe mode, the culprit is device driver. Otherwise it is hardware error.

    If your windows is still crashed at normal mode, report the problem to Microsoft.
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.