locked
BSOD - tried loads of stuff RRS feed

  • Question

  • I am getting BSOD 's on a my main windows machines. It seems quite random but i have attached 3 minidump files, i have gone through them but to be honest i'm not great at interpreting them so i am probably missing something. Any help would be greatly appreciated.

     Link :

    https://www.dropbox.com/sh/akpiuwtt0pjc3py/zpwQ9ppNPi

    I have tried reinstalling drivers even re installed the whole operating system and still the same issue.

    Friday, January 17, 2014 4:37 PM

Answers

  • So looking at the last minidmp


    Stop Code is 0x50

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff6a4ae866ca8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cf5401, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000005, (reserved)

    Debugging Details:
    ------------------


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f10100
    GetUlongFromAddress: unable to read from fffff80002f101c0
     fffff6a4ae866ca8 Nonpaged pool

    FAULTING_IP:
    nt!MiDispatchFault+d1
    fffff800`02cf5401 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

    MM_INTERNAL_CODE:  5
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  ekrn.exe


    That exe that is called out points at Eset Antivirus - I would start by removing that software first. Minidmps are hard to analyze because there is not enough information to truly say that is the issue but does give us some hints.

    On a side note - you have a Vostro 430 which has a BIOS version of 2.1.0 a quick check on support.dell.com shows that there is an update to 2.4.0, you may want to check on other drivers as well to see if there are any updates.

    http://www.dell.com/support/my-support/us/en/555/product-support/product/vostro-430

    Friday, January 17, 2014 5:01 PM
  • These crashes were related to memory managment (probably caused by a driver). 

    Please run these tests to verify your memory and find which driver is causing the problem.  I would run driver verifier first as i suspect it is a driver.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    1-Memtest. (You can read more about running memtest here)
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
    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.

    If a known good stick fails in one motherboard slot but not another it is probably the slot.


    2-Driver verifier (for complete directions see our wiki here)

    Using Driver Verifier is an iffy proposition.
    Most times it will crash and it will tell you what the driver is, but sometimes it will 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).

    Here is 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" 
    For Win 8 dont check Concurrency stress test, and DDI compliance checking 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.
    Co-Authored by  JMH3143

    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by kelvin_hsu Wednesday, January 29, 2014 1:43 AM
    Friday, January 17, 2014 5:23 PM

All replies

  • So looking at the last minidmp


    Stop Code is 0x50

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff6a4ae866ca8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cf5401, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000005, (reserved)

    Debugging Details:
    ------------------


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f10100
    GetUlongFromAddress: unable to read from fffff80002f101c0
     fffff6a4ae866ca8 Nonpaged pool

    FAULTING_IP:
    nt!MiDispatchFault+d1
    fffff800`02cf5401 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

    MM_INTERNAL_CODE:  5
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  ekrn.exe


    That exe that is called out points at Eset Antivirus - I would start by removing that software first. Minidmps are hard to analyze because there is not enough information to truly say that is the issue but does give us some hints.

    On a side note - you have a Vostro 430 which has a BIOS version of 2.1.0 a quick check on support.dell.com shows that there is an update to 2.4.0, you may want to check on other drivers as well to see if there are any updates.

    http://www.dell.com/support/my-support/us/en/555/product-support/product/vostro-430

    Friday, January 17, 2014 5:01 PM
  • These crashes were related to memory managment (probably caused by a driver). 

    Please run these tests to verify your memory and find which driver is causing the problem.  I would run driver verifier first as i suspect it is a driver.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    1-Memtest. (You can read more about running memtest here)
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Get it here
    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.

    If a known good stick fails in one motherboard slot but not another it is probably the slot.


    2-Driver verifier (for complete directions see our wiki here)

    Using Driver Verifier is an iffy proposition.
    Most times it will crash and it will tell you what the driver is, but sometimes it will 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).

    Here is 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" 
    For Win 8 dont check Concurrency stress test, and DDI compliance checking 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.
    Co-Authored by  JMH3143

    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by kelvin_hsu Wednesday, January 29, 2014 1:43 AM
    Friday, January 17, 2014 5:23 PM
  • Thats great, thanks for all your help everyone, i will give the above suggestions a go and let you know the results in a few days
    Friday, January 17, 2014 7:06 PM
  • Hi,

    Have you taken time to check above suggestions?

    Any update, please come back here.

    Wait for your reply.


    Kate Li
    TechNet Community Support

    Wednesday, January 22, 2014 2:33 PM