also @ TechSpot: Samsung to debut 3200x1800, 298 PPI 13.3" LCD panel (and more)

Other BSOD problem

Discussion in 'Windows BSOD, Freezing, Restarting Help' started by AFCB, Nov 11, 2006.

  1. cpc2004 Newcomer, in training 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.
  2. AFCB Newcomer, in training 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?
  3. cpc2004 Newcomer, in training 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.
  4. AFCB Newcomer, in training 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
  5. AFCB Newcomer, in training Posts: 29

    Two more.. What shall i do?

    EDIT: I can't go in safe mode...
  6. AFCB Newcomer, in training Posts: 29

    Shall i change HDD?
     
  7. cpc2004 Newcomer, in training 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)?
  8. AFCB Newcomer, in training 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
  9. cpc2004 Newcomer, in training 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.