BSOD Memory mangement.

Page 1 of 3 123 LastLast

  1. Posts : 19
    7 64 bit
       #1

    BSOD Memory mangement.


    Hi
    Im a small oem builder. Recently built a system for a customer. Everything working fine during pre delivery testing. When set up at customers business I installed his hp office jet 4500 printer and all [bleep] broke loose. Repeated bsod with memory mangement. Some times on boot other times after pc ran for 30 minutes. Have since taken pc back to my workshop but am unable to reproduce the error.
    Have run memtest for 24 hours and passes with no errors.


    Have also run check disk


    The printer is usb 2 and was connected to a usb 3 port. Could this be the cause?


    System Specs

    Corsair 8gb ram value select ddr3 1333mhz
    450 wat corsair vs450 psu
    Liteon dvd writer
    Western digital 1tb hdd
    Amd a4 6300 cpu
    Gigabyte GA f2a78m-hd2 mobo


    Blue screen view

    Dump File : 061914-17581-01.dmp
    Crash Time : 19/06/2014 11:56:54 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`04017f90
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-17581-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 11:58:35 AM
    ==================================================

    ==================================================
    Dump File : 061914-16364-01.dmp
    Crash Time : 19/06/2014 11:55:30 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00005002
    Parameter 2 : fffff780`c0000000
    Parameter 3 : 00000000`000045f9
    Parameter 4 : 080045fa`fffffffe
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-16364-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 11:56:30 AM
    ==================================================

    ==================================================
    Dump File : 061914-17986-01.dmp
    Crash Time : 19/06/2014 11:14:35 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`0400f0b0
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-17986-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 11:15:52 AM
    ==================================================

    ==================================================
    Dump File : 061914-17362-01.dmp
    Crash Time : 19/06/2014 10:16:45 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`0400f050
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-17362-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 10:17:54 AM
    ==================================================

    ==================================================
    Dump File : 061914-26878-01.dmp
    Crash Time : 19/06/2014 10:12:41 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`03ef67f0
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-26878-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 10:14:08 AM
    ==================================================

    ==================================================
    Dump File : 061914-26442-01.dmp
    Crash Time : 19/06/2014 10:11:38 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00041790
    Parameter 2 : fffffa80`03ed0f90
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-26442-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 10:12:38 AM
    ==================================================

    ==================================================
    Dump File : 061914-26364-01.dmp
    Crash Time : 19/06/2014 10:10:32 AM
    Bug Check String : MEMORY_MANAGEMENT
    Bug Check Code : 0x0000001a
    Parameter 1 : 00000000`00005005
    Parameter 2 : fffff700`01080000
    Parameter 3 : 00000000`000000d1
    Parameter 4 : 00000000`000000d2
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\061914-26364-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 276,368
    Dump File Time : 19/06/2014 10:11:33 AM
    ==================================================
      My Computer


  2. Posts : 19
    7 64 bit
    Thread Starter
       #2

    SF diagnostic tool
      My Computer


  3. Posts : 19
    7 64 bit
    Thread Starter
       #3

    At this stage I'm thinking its either an issue relating to customers printer and drivers for same or I buggered something up during the windows install and should just do a clean install. Any ideas guys and girls??
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #4

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005002, The subtype of the bugcheck.
    Arg2: fffff780c0000000
    Arg3: 00000000000045f9
    Arg4: 080045fafffffffe
    Download and run MemTest86+ to test your RAM.

       Note
    Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.
      My Computer


  5. Posts : 19
    7 64 bit
    Thread Starter
       #5

    Had already done this over 12 hours and no errors.
      My Computer


  6. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #6

    Apologies, I missed that in your first post.

    We need to see if any of your drivers are causing the issue, as none are showing in your logs we'll try DriverVerifier.

    Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable

    Enable Driver Verifier but only enable these options:
    Standard settings and IRP logging step 3.
    Don't enable Force Pending I/O Requests

       Warning
    Make a System Restore point before enabling Driver Verifier.


       Note
    Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computer


  7. Posts : 19
    7 64 bit
    Thread Starter
       #7

    Thanks for the prompt response. Sorry about the delay getting back to you. Had to go to my day job.
    Have enable driver verifier now and waiting for bsod. What do I do next?
      My Computer


  8. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #8

    Upload the logs that result from DV. That's what we're looking for it to do, cause a BSOD.
      My Computer


  9. Posts : 19
    7 64 bit
    Thread Starter
       #9

    Been running for an hour now and no bsod as yet. How long does it usually take?
    Strange as it was bsod city when I set up the system at customers place. The only difference here is its connected to a different printer and two different monitors. Plus different mouse and keyboard.
      My Computer


  10. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #10

    Give it a few hours. If nothing shakes loose you'll need to add the customer's peripherals one by one and test each one to see if they recreate the BSOD. Ideally you'd be running DV in the conditions the PC crashed.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:32.
Find Us