1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

Occasional BSODs, computer has rebooted from a bugcheck, bugcheck was: 0x000000d1

By icet
Nov 11, 2010
Post New Reply
  1. The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xfffff880017c43d0, 0x0000000000000002, 0x0000000000000008, 0xfffff880017c43d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111110-36535-01.

    I got a blue screen on a fairly new machine, I've seen them for a little while, but they don't stay open long enough for me to read them. The specs that I built were:

    Motherboard: ASUS P7P55D-E Pro
    CPU: Intel Core i7-860 Lynnfield 2.8GHz $289.99
    Video Card: EVGA 01G-P3-1372-TR GeForce GTX 460 Superclocked (Fermi)
    Ram: OCZ Reaper HPC 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model OCZ3RPR1600LV4GK
    Case: COOLER MASTER RC-690
    Power Supply: SeaSonic X650 Gold 650W ATX12V V2.3/EPS 12V V2.91 SLI Ready 80 PLUS GOLD Certified Modular Active PFC Power Supply
    DVD Rom Drive: Sony Optiarc Black 24X DVD Burner
    CPU Cooler: Cooler Master Hyper N520
    Hard Drive: Western Digital Caviar Black WD1002FAEX 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive -Bare Drive

    I additionally added an old wifi adapter and two hard drives.

    I'm not sure if the attached log is useful (one that appears to have been created when this blue screen happened, and another a couple weeks ago). Anyone know what might be going on or what I should try? It doesn't happen often enough for me to test fixes very easily, so all help is appreciated.


    Attached Files:

    • dmp.zip
      File size:
      50.8 KB
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,979   +71

    Your issue is with memory corruption. Therefore you’ll need to run memtest on your RAM.

    See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

    Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

    There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced.

    Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.

    Link: https://www.techspot.com/vb/topic62524.html

    * Get back to us with the results.

    *** If Memtest shows no errors then find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?

    * Also, check to see if your RAM makes Asus' Qualified Vendors List of memory for your motherboard. It will be on your motherboard's website page.
  3. Jonathan King

    Jonathan King TS Rookie Posts: 128

    In addition to Route44's excellent advice:

    Update or remove your Logitech QuickCam software, as it was blamed by the October 30 dump.
    lvrs64.sys   Tue Jul 27 04:00:02 2010 (4C4E9202)
    lvsels64.sys Tue Jul 27 03:59:23 2010 (4C4E91DB)
    lvuvc64.sys  Tue Jul 27 04:00:43 2010 (4C4E922B)
    Also to-do:

    Rt64win7.sys Thu Nov 05 09:15:41 2009 (4AF2DE0D)
    nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
    nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
    .....Summary of the dumps
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Thu Nov 11 15:03:55.229 2010 (UTC - 5:00)
    System Uptime: 1 days 8:45:22.370
    Probably caused by : memory_corruption
    PROCESS_NAME:  svchost.exe
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sat Oct 30 20:18:32.740 2010 (UTC - 5:00)
    System Uptime: 0 days 8:47:16.880
    *** WARNING: Unable to verify timestamp for lvrs64.sys
    *** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
    Probably caused by : lvrs64.sys ( lvrs64+101fc )
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+101fc

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...