locked
Win7 64 bit crashing RRS feed

  • Question

  • Its crashing quite a bit now, several times a day. It will even crash when I dont clear the previous crash. The upload to skydrive can be found here.

    https://skydrive.live.com/#cid=E9D8AD5D2BFEC770&id=E9D8AD5D2BFEC770!109

    Thank you very much in advance for your help. I had the bug when I first built the machine, it seemed to go away and then it looks like it popped right back up after the last windows update but for some reason I cant roll back to a previous install.

    Friday, January 11, 2013 11:30 PM

Answers

  • Ruuster

    These are related to memory management

     These crashes were caused by memory management (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

    *Dont forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!   If you dont know what this means you probably arent


    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org 
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.


    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    *But sometimes it'll crash and won't tell you the driver.
    *Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    *I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    *Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    *In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    *Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.
    *Reboot the system and wait for it to crash to the Blue Screen.
    *Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    *If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    *If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.


    *Further Reading
    http://support.microsoft.com/kb/244617

    Old drivers needing updating

    Protype.sys                 Tue Nov 28 20:55:18 2006 (456CE886)
    Razer ProType USB Keyboard driver by WayTech
    http://www.carrona.org/drivers/driver.php?id=Protype.sys
     
    LVUSBS64.sys                Sat Feb  3 13:05:16 2007 (45C4CEDC)
    Logitech Camera driver
    http://www.carrona.org/drivers/driver.php?id=LVUSBS64.sys
     
    CamDrL64.sys                Sat Feb  3 13:17:27 2007 (45C4D1B7)
    Logitech QuickCam Pro 3000
    http://www.carrona.org/drivers/driver.php?id=CamDrL64.sys
     
    lmimirr.sys                 Tue Apr 10 18:32:45 2007 (461C108D)
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    http://www.carrona.org/drivers/driver.php?id=lmimirr.sys
     
    RaInfo.sys                  Fri Jan  4 13:57:14 2008 (477E818A)
    LogMeIn/RemotelyAnywhere Kernel Information Provider
    http://www.carrona.org/drivers/driver.php?id=RaInfo.sys
     
    LMIRfsDriver.sys            Mon Jul 14 12:26:56 2008 (487B7E50)
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Saturday, January 12, 2013 3:28 AM
  • Hi,


    After checking the latest dump file, I found this requires hardware testing and driver verifier to troubleshoot. In addition to ZigZag3143x, please also test in Safe Mode to see how it works.


    Regards,


    Vincent Wang
    TechNet Community Support

    Tuesday, January 15, 2013 6:51 AM
  • Its crashing quite a bit now, several times a day. It will even crash when I dont clear the previous crash. The upload to skydrive can be found here.

    https://skydrive.live.com/#cid=E9D8AD5D2BFEC770&id=E9D8AD5D2BFEC770!109

    Thank you very much in advance for your help. I had the bug when I first built the machine, it seemed to go away and then it looks like it popped right back up after the last windows update but for some reason I cant roll back to a previous install.

    Hi Ruuster,

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 00000000007f1001
    Arg3: 000000000000a598
    Arg4: fffff70001080000
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x1a_41284
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  realplay.exe ##########
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002cdaa37 to fffff80002c83fc0
    STACK_TEXT:  
    fffff880`0b4c17d8 fffff800`02cdaa37 : 00000000`0000001a 00000000`00041284 00000000`007f1001 00000000`0000a598 : nt!KeBugCheckEx
    fffff880`0b4c17e0 fffff800`02cb5280 : fffff700`01080000 00000000`00e40201 00000000`007f0000 00000000`73a32554 : nt! ?? ::FNODOBFM::`string'+0x4ac3
    fffff880`0b4c1820 fffff800`02c7081f : fffffa80`00000000 00000000`0089ffff 00000000`00000000 fffff800`02f76ae4 : nt!MiDeleteVirtualAddresses+0x4e8
    fffff880`0b4c19e0 fffff800`02c83253 : ffffffff`ffffffff 00000000`0023e120 00000000`0023e118 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
    fffff880`0b4c1ae0 00000000`775714fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0023e0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775714fa
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4ac3
    fffff800`02cdaa37 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
    BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
    Followup: MachineOwner
    -----------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x1a: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

    the Blue Caused by realplay.exe process which mean a Real Player Software, so you can uninstall it it solve your BSOD, or update it to the latest version.

    Regards,



    MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA

    Tuesday, January 15, 2013 1:38 PM

All replies

  • Ruuster

    These are related to memory management

     These crashes were caused by memory management (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

    *Dont forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!   If you dont know what this means you probably arent


    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org 
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.


    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    *But sometimes it'll crash and won't tell you the driver.
    *Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    *I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    *Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    *In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    *Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.
    *Reboot the system and wait for it to crash to the Blue Screen.
    *Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    *If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    *If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.


    *Further Reading
    http://support.microsoft.com/kb/244617

    Old drivers needing updating

    Protype.sys                 Tue Nov 28 20:55:18 2006 (456CE886)
    Razer ProType USB Keyboard driver by WayTech
    http://www.carrona.org/drivers/driver.php?id=Protype.sys
     
    LVUSBS64.sys                Sat Feb  3 13:05:16 2007 (45C4CEDC)
    Logitech Camera driver
    http://www.carrona.org/drivers/driver.php?id=LVUSBS64.sys
     
    CamDrL64.sys                Sat Feb  3 13:17:27 2007 (45C4D1B7)
    Logitech QuickCam Pro 3000
    http://www.carrona.org/drivers/driver.php?id=CamDrL64.sys
     
    lmimirr.sys                 Tue Apr 10 18:32:45 2007 (461C108D)
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    http://www.carrona.org/drivers/driver.php?id=lmimirr.sys
     
    RaInfo.sys                  Fri Jan  4 13:57:14 2008 (477E818A)
    LogMeIn/RemotelyAnywhere Kernel Information Provider
    http://www.carrona.org/drivers/driver.php?id=RaInfo.sys
     
    LMIRfsDriver.sys            Mon Jul 14 12:26:56 2008 (487B7E50)
    RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
    http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Saturday, January 12, 2013 3:28 AM
  • Hi,


    After checking the latest dump file, I found this requires hardware testing and driver verifier to troubleshoot. In addition to ZigZag3143x, please also test in Safe Mode to see how it works.


    Regards,


    Vincent Wang
    TechNet Community Support

    Tuesday, January 15, 2013 6:51 AM
  • Its crashing quite a bit now, several times a day. It will even crash when I dont clear the previous crash. The upload to skydrive can be found here.

    https://skydrive.live.com/#cid=E9D8AD5D2BFEC770&id=E9D8AD5D2BFEC770!109

    Thank you very much in advance for your help. I had the bug when I first built the machine, it seemed to go away and then it looks like it popped right back up after the last windows update but for some reason I cant roll back to a previous install.

    Hi Ruuster,

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 00000000007f1001
    Arg3: 000000000000a598
    Arg4: fffff70001080000
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x1a_41284
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  realplay.exe ##########
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002cdaa37 to fffff80002c83fc0
    STACK_TEXT:  
    fffff880`0b4c17d8 fffff800`02cdaa37 : 00000000`0000001a 00000000`00041284 00000000`007f1001 00000000`0000a598 : nt!KeBugCheckEx
    fffff880`0b4c17e0 fffff800`02cb5280 : fffff700`01080000 00000000`00e40201 00000000`007f0000 00000000`73a32554 : nt! ?? ::FNODOBFM::`string'+0x4ac3
    fffff880`0b4c1820 fffff800`02c7081f : fffffa80`00000000 00000000`0089ffff 00000000`00000000 fffff800`02f76ae4 : nt!MiDeleteVirtualAddresses+0x4e8
    fffff880`0b4c19e0 fffff800`02c83253 : ffffffff`ffffffff 00000000`0023e120 00000000`0023e118 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
    fffff880`0b4c1ae0 00000000`775714fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0023e0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775714fa
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4ac3
    fffff800`02cdaa37 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
    BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
    Followup: MachineOwner
    -----------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x1a: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

    the Blue Caused by realplay.exe process which mean a Real Player Software, so you can uninstall it it solve your BSOD, or update it to the latest version.

    Regards,



    MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA

    Tuesday, January 15, 2013 1:38 PM