Other BSOD problem

By AFCB
Nov 11, 2006
Topic Status:
Not open for further replies.
  1. Hello..
    I’m new in here..
    I have several problems in my pc.. I got many BSOD’s, never the same and never in the same time..

    I have a:
    AMD 3800+
    Asus A8N SLI SE
    Asus 6800GT
    Philips 190s6
    I have 1Gb, kingston..
    I have formatted my disk 7/8 times..
    And i change my psu to a LC POWER 550W DUAL RAIL 24P REV2 PCIe

    I've run memtest and passed..
    I got many BSOD's, one's i don't have a file, others refers to nv4_disp.dll, others to win32k.sys, ones are page fault, others irql..
    This problem have started 6 mouths ago..

    I install the all drivers of my mobo and graphics drivers..
    What should I do? Help me please


    P.S.: I’m Portuguese, sorry about the mistakes..

    Attached Files:

  2. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    Anyone can help me?
  3. sultan_emerr

    sultan_emerr Newcomer, in training Posts: 61

    Random restarts/reboots/resets/crashes/freezes could be due to several reasons, including overheating, RAM, hardware issues, etc., just do the following and post back with the info so that we can narrow it down some.

    Try rebooting(restarting) in safe mode, then go to control panel/ system / advanced Tab/ startup and recovery box/ settings button/ sytem failure and uncheck "restart on system failure" ( take the check out of automatically restart box ) , and check the Write a system event, and the Admin alert boxes (check "send admin alert"). This will force a BSOD on the next crash (freezes/restarts = crashing) that posts the Stop Error Code. On the next crash write down the exact Stop Error Code and post that exact error here back on this thread. (While you're waiting for a reply, you can put that error code in Google search, and in the MS Support Knowledge Base (KB) = to check it out.-
    http://support.microsoft.com/search/?adv=1 ).


    Also go to your device manager (devmgmt.msc) and check the properties and look for anything suspicious and check that the settings are where they should be.

    Check:
    1. Overheating(Open the case and check to see how much dust has collected inside it, and if there is alot of dust get a can of compressed air and blow the dust out and clean out all dust bunnies, etc. on the heatsink/;fan combo,etc.; and be sure all the fans are spinning and properly functioning ). Install diagonstic tools like MotherboardMonitor= http://mbm.livewiredev.com or Everest = http://www.majorgeeks.com/download4181.html , and check the tempurature.

    2. Poor power supply (weak power supply or noisey / dirty electricity). If possible, swap the RAM and Power Supply (PSU) around with another computer.

    3. Bad driver or drivers not updated, or a device conflict. Pull the connectors and push them back on. Reseat all of the cards. RightClick - my comp/properties/select the hardware tab/click device manager/see if there are any "!" next to anything. Try updating the drivers from the manufacturers' websites.


    4. Not enough memory or bad Ram. You might need to add more Ram. Missmatched ram or a bad stick of ram will cause this also. Try reseating and or swaping the ram sticks. Make sure they are seated/snaped in firmly.
    Run Memtest86: = http://www.memtest.org
    and
    FREE RAM Diagnostic Tool. - CST Inc.s DOS based DocMemory = http://bucarotechelp.com/computers/default.asp .


    5. Could be IRQ conflict

    6. Perhaps the CMOS battery on the motherboard is going bad and needs to be replaced. Check it to be sure.
    Also check your pc clock's time and day, to be sure it is set correctly.

    7. Hard drive could be failing.

    8 Right click desktop/properties/screen saver/Power/Hibernate tab ,and make sure hibernation is not enabled, and cleann out your Cache & Cookies & Temporary Internet Files and Folder: = http://www.coloarts.state.co.us/cleanFiles.asp[/L]

    9. Make sure you have updated all programs and hadrdware.

    10. Motheboard short (loose screw, misplaced mounting standoff , etc.?)
  4. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Fauty Ram

    Hi,

    One minidump is crashed with 7F and exception code d. This is the sign of the faulty ram.
    Mini110906-01.dmp BugCheck 1000007F, {d, 0, 0, 0}

    Another mindump is crashed bugcheck C2 and it is also the symptom of faulty ram.
    Mini111006-01.dmp BugCheck C2, {7, cd4, 86100740, 84d7f3e0}

    Pull over memory module one by one and diagnostic which memory module is bad. Some faulty ram can pass memtest.
  5. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    I've already do that cpc2004.. And in the two times BSOD's appear's.. But i will do again to have sure.. I'll post anything after..
    Thank's for the help.. (and sorry about the PM's cpc2004)
  6. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    BSOD with the two memory's.. I have the BSOD's when: turn off and next when i turn on - BSOD, when windows is starting..
    What to do?
  7. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Hi AFCB,

    I don't understand what you mean. Can you explain more clearly?
  8. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    Sorry.. I'm portuguese..
    I have tried with one memory separated and i got BSOD in the two times.. I have the BSOD's when i turn on my computer.. On the windows start..
  9. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Replace the ram.
  10. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    How can the two memory's are "broken"?
    Are you sure if i change the memory's i'll have the computer fix?
    Thank's for all your help..
  11. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Hi,

    >>>
    I have tried with one memory separated and i got BSOD in the two times.
    >>>

    I assume that you try memory module A alone, it crashed. You try memory module B alone, it also crashed. Hence both both memory module are bad. Try downclocking the ram.
  12. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    Ok..
    I'll do that..
    I write something when i have a BSOD or in one week..
    Thank's
  13. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    I've downclock the memory, without success.. You recommend me to buy a new memory?
     
  14. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Hi,

    You only attach 2 minidumps and the crashes are related to faulty memory. As you know, the fautly memory may be ram, video memory or L2 cache memory of the CPU. According to my experince, most of the faulty memoy are related to RAM. Attach 4 to 5 minidumps here if you want me to confirm it is ram problem.
  15. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    One more..
  16. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Zip more minidumps

    Hi AFCB,

    One minidump is insufficient to confirm your problem. This forum accepts zip files and the size limit is 100K. Can you zip 5 to 6 minidumps?
  17. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    I can if i have it.. I formatted the computer, so i don't have minidumps.. When i have suficcient i'll post..
    Thank's and sorry about the language
  18. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    So far no more BSOD's.. But i have a question.. The errors "send error report" might be relation with the BSOD's? Now i have many..
  19. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

    So far 2 BSOD's..
    Can you analyse, please?
  20. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

    Crash at nVidia Display Card Driver

    Hi,

    Two minidumps are crashed at nVidia Display Card Driver. It may be caused by faulty ram or software error of nVidia Display Card.

    Mini111606-01.dmp BugCheck 10000050, {89000004, 1, bfb54fc5, 0}
    Owning Process 862237a8 Image: FEARXP.exe
    Probably caused by : nv4_disp.dll ( nv4_disp+141fc5 )

    Mini111906-01.dmp BugCheck 10000050, {e7e83b84, 0, bfac2f81, 2}
    Owning Process 853f4a70 Image: Condemned.exe
    Probably caused by : nv4_disp.dll ( nv4_disp+aff81 )
  21. AFCB

    AFCB Newcomer, in training Topic Starter Posts: 29

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

    cpc2004 Newcomer, in training Posts: 2,044

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

    AFCB Newcomer, in training Topic Starter Posts: 29

    Another..
    Thank's
  24. cpc2004

    cpc2004 Newcomer, in training Posts: 2,044

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

    AFCB Newcomer, in training Topic Starter Posts: 29

    I've changed the memory's with one friend and i don't had BSOD.. Today a put my and i have two..
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.