locked
Computer crashing with blue screens RRS feed

  • Question

  • My Windows 7 premier 64bit desktop computer has started randomly crashing with blue screens.

    The computer has an Asrock N7AD-SLI motherboard(latest drivers installed), Intel core 2 duo E8400 3.0GHz chip, 8 gb OCZ DDR2 800MHz Ram (2 4Gb dual channel kits), GeForce GTS250 Graphics card (with latest driver) and a Creative SB X-Fi Extreme audio PCI-Express sound card (latest drivers).

    Have tested memory with MemTest86, no problems.

    Tested the hard drive with error checking, no problems.

    Mini dump logs are on my Skydrive page

    http://cid-db600de4ab0f2d97.office.live.com/browse.aspx/.Documents?uc=1

    Any help would be appreciated as I don't know if it's a hardware or software problem

    Sunday, November 14, 2010 1:18 PM

Answers

  • Found a bad ram chip and after removing it i've had no crashes for 5 days, so I think problem is solved.

    Thanyou to Andre Ziegler for the help it was appreciated.

    • Marked as answer by dstevied Wednesday, November 24, 2010 5:23 PM
    Wednesday, November 24, 2010 5:23 PM

All replies

  • DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) - An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!KiBugCheckDispatch+0x69
    nt!KiPageFault+0x260
    0x49
    nvlddmkm +0x2d4261
    0xfffffa80`08032000

    BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP _nvlddmkm+2d4261

        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 16 19:12:46 2010 (4CB9DD0E)

    The

    VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
    The video memory manager encountered a condition that it can't recover from. By crashing,
    the video memory manager is attempting to get enough information into the minidump such that
    somebody can pinpoint what lead to this condition.

    STACK_TEXT: 
    nt!KeBugCheckEx
    watchdog!WdLogEvent5+0x11b
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
    dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
    dxgmms1!VidSchiSubmitRenderCommand+0x241
    dxgmms1!VidSchiSubmitQueueCommand+0x50
    dxgmms1!VidSchiWorkerThread+0xd6
    nt!PspSystemThreadStartup+0x5a
    nt!KxStartSystemThread+0x16

    KMODE_EXCEPTION_NOT_HANDLED (1e) - This is a very common bugcheck.

    ExceptionAddress: fffff880017652b4 (NETIO !WfpTimerWheelTimeoutHandler+0x0000000000000134)
       ExceptionCode: c0000005 (Access violation )
      ExceptionFlags: 00000000

    update the network card drivers.


    IRQL_NOT_LESS_OR_EQUAL (a) - An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!KiBugCheckDispatch+0x69
    nt!KiPageFault+0x260
    nt!KiProcessExpiredTimerList+0x103
    nt!KiTimerExpiration+0x1be
    nt!KiRetireDpcList+0x277
    nt!KxRetireDpcList+0x5
    nt!KiDispatchInterruptContinue

    PFN_LIST_CORRUPT (4e) - Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) - An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!KiBugCheckDispatch+0x69
    nt!KiPageFault+0x260
    ha10kx2k +0xba9dc
    0x2c05df
    nvlddmkm+0xb68750
    nvlddmkm+0xb70a40
    ctoss2k +0x6816
    nt!KiInitialPCR+0x180

        Image path: \SystemRoot\system32\drivers\ha10kx2k.sys
        Image name: ha10kx2k.sys
        Timestamp:        Thu Mar 18 13:17:59 2010

        Image path: \SystemRoot\system32\drivers\ctoss2k.sys
        Image name: ctoss2k.sys
        Timestamp:        Thu Mar 18 13:17:56 2010

    update both drivers.

    KMODE_EXCEPTION_NOT_HANDLED (1e) - This is a very common bugcheck. 
    Arg1: ffffffffc0000005, The exception code that was not handled

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Access violation


    You have different crashes. Update all drivers and check your RAM again.


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Wednesday, November 24, 2010 10:20 PM
    Sunday, November 14, 2010 2:06 PM
  • As requested I have updated the soundcard, graphics card and network drivers to the latest I could find.

    Have rerun Memtest86 with no errors on the first pass. ( Not sure how many passes you should do as I heard if it passes the first time it should be ok, may be wrong.)

    Should have also mentioned that when the computer crashes it will not boot up. I have to keep restarting as it hangs at the Asrock welcome screen. If it does boot straight away it will normally restart itself either before or as the window logo appears. Then its back to pressing the restart button untill it finally boots with the system repair option.

    Bios is updated to the latest on the Asrock site for my Motherboard.

    There are some more minidumps in my sky drive folder if its of any help.

    Thanks in advance for any insights into the problem as looking at minidumps confuses me. I can normally sort out my computer myself, but these blue screens are miles to technical for me.

    Tuesday, November 16, 2010 7:36 PM
  • Found a bad ram chip and after removing it i've had no crashes for 5 days, so I think problem is solved.

    Thanyou to Andre Ziegler for the help it was appreciated.

    • Marked as answer by dstevied Wednesday, November 24, 2010 5:23 PM
    Wednesday, November 24, 2010 5:23 PM
  • Thanyou to Andre Ziegler for the help it was appreciated.

    you're welcome

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, November 24, 2010 10:20 PM