BSOD Help Please

Discussion in 'Windows 10 Blue Screen of Death (BSOD)' started by Haggisdog, Nov 28, 2015.

  1. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    I'm a new member of the forums but was really impressed with the quality of assistance provided in troubleshooting BSODs.

    I've been getting a number of BSODs daily over the last few weeks and although I've attempted to troubleshoot the issues including a fresh install of Windows 10 I'm still not able to pinpoint the issue. I've attached the W7F diagnostic file from my last crash.

    Thanks for any assistance anyone can provide.
     

    Attached Files:

  2. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    As a quick update on the above. I ran MemTest86 successfully with no errors. However, I downloaded Prime95 as I saw it was mentioned in some other posts and while it has been running successfully for the last 30 minutes, one of the workers stopped with the following error:

    [Nov 28 20:14] Worker starting
    [Nov 28 20:14] Setting affinity to run worker on logical CPU #2
    [Nov 28 20:14] Beginning a continuous self-test on your computer.
    [Nov 28 20:14] Please read stress.txt. Choose Test/Stop to end this test.
    [Nov 28 20:14] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
    [Nov 28 20:15] FATAL ERROR: Rounding was 0.5, expected less than 0.4
    [Nov 28 20:15] Hardware failure detected, consult stress.txt file.
    [Nov 28 20:15] Torture Test completed 0 tests in 0 minutes - 1 errors, 0 warnings.
    [Nov 28 20:15] Worker stopped.
     
  3. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    So after a little more time several of the CPU cores failed in the Prime95 test. I'm not sure if this means I have a faulty processor which might be contributing to my BSODs.
    Code:
    [Nov 28 20:14] Worker starting
    [Nov 28 20:14] Setting affinity to run worker on logical CPU #1
    [Nov 28 20:14] Beginning a continuous self-test on your computer.
    [Nov 28 20:14] Please read stress.txt.  Choose Test/Stop to end this test.
    [Nov 28 20:14] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
    [Nov 28 20:17] Test 2, 6500 Lucas-Lehmer iterations of M12451839 using AMD K10 FFT length 640K, Pass1=640, Pass2=1K.
    [Nov 28 20:19] Self-test 640K passed!
    [Nov 28 20:19] Test 1, 800000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
    [Nov 28 20:21] Test 2, 800000 Lucas-Lehmer iterations of M163839 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
    [Nov 28 20:23] Self-test 8K passed!
    [Nov 28 20:23] Test 1, 5300 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
    [Nov 28 20:26] Test 2, 5300 Lucas-Lehmer iterations of M14155775 using AMD K10 FFT length 720K, Pass1=320, Pass2=2304.
    [Nov 28 20:27] Self-test 720K passed!
    [Nov 28 20:27] Test 1, 460000 Lucas-Lehmer iterations of M250519 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
    [Nov 28 20:29] Test 2, 460000 Lucas-Lehmer iterations of M245759 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
    [Nov 28 20:31] Self-test 12K passed!
    [Nov 28 20:31] Test 1, 4500 Lucas-Lehmer iterations of M15597569 using AMD K10 type-2 FFT length 800K, Pass1=640, Pass2=1280.
    [Nov 28 20:33] Test 2, 4500 Lucas-Lehmer iterations of M15597567 using AMD K10 FFT length 800K, Pass1=640, Pass2=1280.
    [Nov 28 20:35] Self-test 800K passed!
    [Nov 28 20:35] Test 1, 270000 Lucas-Lehmer iterations of M420217 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
    [Nov 28 20:37] Test 2, 270000 Lucas-Lehmer iterations of M409601 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
    [Nov 28 20:39] Self-test 20K passed!
    [Nov 28 20:39] Test 1, 4500 Lucas-Lehmer iterations of M17432577 using AMD K10 type-2 FFT length 896K, Pass1=896, Pass2=1K.
    [Nov 28 20:41] FATAL ERROR: Rounding was 0.5, expected less than 0.4
    [Nov 28 20:41] Hardware failure detected, consult stress.txt file.
    [Nov 28 20:41] Torture Test completed 12 tests in 26 minutes - 1 errors, 0 warnings.
    [Nov 28 20:41] Worker stopped.
    
    [Nov 28 20:14] Worker starting
    [Nov 28 20:14] Setting affinity to run worker on logical CPU #4
    [Nov 28 20:14] Beginning a continuous self-test on your computer.
    [Nov 28 20:14] Please read stress.txt.  Choose Test/Stop to end this test.
    [Nov 28 20:14] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using AMD K10 type-2 FFT length 640K, Pass1=640, Pass2=1K.
    [Nov 28 20:17] Test 2, 6500 Lucas-Lehmer iterations of M12451839 using AMD K10 FFT length 640K, Pass1=640, Pass2=1K.
    [Nov 28 20:19] Self-test 640K passed!
    [Nov 28 20:19] Test 1, 800000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
    [Nov 28 20:21] Test 2, 800000 Lucas-Lehmer iterations of M163839 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
    [Nov 28 20:23] Self-test 8K passed!
    [Nov 28 20:23] Test 1, 5300 Lucas-Lehmer iterations of M14155777 using AMD K10 type-2 FFT length 720K, Pass1=320, Pass2=2304.
    [Nov 28 20:25] Test 2, 5300 Lucas-Lehmer iterations of M14155775 using AMD K10 FFT length 720K, Pass1=320, Pass2=2304.
    [Nov 28 20:27] Self-test 720K passed!
    [Nov 28 20:27] Test 1, 460000 Lucas-Lehmer iterations of M250519 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
    [Nov 28 20:29] Test 2, 460000 Lucas-Lehmer iterations of M245759 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
    [Nov 28 20:31] Self-test 12K passed!
    [Nov 28 20:31] Test 1, 4500 Lucas-Lehmer iterations of M15597569 using AMD K10 type-2 FFT length 800K, Pass1=640, Pass2=1280.
    [Nov 28 20:33] Test 2, 4500 Lucas-Lehmer iterations of M15597567 using AMD K10 FFT length 800K, Pass1=640, Pass2=1280.
    [Nov 28 20:34] Self-test 800K passed!
    [Nov 28 20:34] Test 1, 270000 Lucas-Lehmer iterations of M420217 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
    [Nov 28 20:36] Test 2, 270000 Lucas-Lehmer iterations of M409601 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
    [Nov 28 20:38] Self-test 20K passed!
    [Nov 28 20:38] Test 1, 4500 Lucas-Lehmer iterations of M17432577 using AMD K10 type-2 FFT length 896K, Pass1=896, Pass2=1K.
    [Nov 28 20:40] FATAL ERROR: Rounding was 0.5, expected less than 0.4
    [Nov 28 20:40] Hardware failure detected, consult stress.txt file.
    [Nov 28 20:40] Torture Test completed 12 tests in 25 minutes - 1 errors, 0 warnings.
    [Nov 28 20:40] Worker stopped.
    
     
    #3 Haggisdog, Nov 28, 2015
    Last edited by a moderator: Dec 11, 2015
  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {8, 2, 0, fffff8001fcda9af}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+54f )
    
    Followup: MachineOwner
    
    Hi,
    you have many different bugchecks with some blaming memory, system kernel and one driver. The only driver I saw mentioned was this one:
    SAlpham64.sys Tue May 27 17:46:34 2014: SteelSeries Engine HID Driver. I think this relates to a mouse? See if you can update the driver:
    SteelSeries Engine Downloads & Drivers | SteelSeries

    Regarding your Prime95 test above, is the cpu overclocked at all? If so please disable until source of bsod is found. When you ran the above test did you monitor the temperatures? If not please run the test again and watch those temps. This application will help:
    HWiNFO, HWiNFO32/64 - Download

    Re your running of Memtest86, can you post how long you ran it for please. I normally recommend at least 12hrs.

    Please run the system file checker. Open an admin command prompt and type:
    sfc /scannow
    Press enter and await results.

    Can you post the make and model of your PSU please.

    Also can you post when the bsod's mainly occur, during gaming or are they random?

    Post any new dump files.
     
  5. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Thanks for the response. Comments below:
    • I ran MemTest86 all night so about 12 hours.
    • I updated the mouse/keyboard driver from Steelseries
    • I ran SFC /scannow and while it completed it did have a message saying errors were found that it could not correct (CBS.log attached)
    • PSU is a Corsair CX500
    • CPU and GPU are not overclocked
    • There was another BSOD and dump files attached.
    • Errors are random occurring both during gaming and just random webpage viewing.
    • I'll run some temp tests using Prime95 and Furmark and post results.
     

    Attached Files:

  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffe0002f21e778, 2, 0, fffff803ad0d797b}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiRetireDpcList+51b )
    
    Followup: MachineOwner
    
    Hi,
    causes for this bugcheck are usually driver related although there are others:
    https://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

    Hmm date is still the same as the previous driver so i guess thats the latest version?

    Open another admin command propmt. Type or copy and paste:
    dism /online /cleanup-image /restorehealth
    Press enter and await results. If the scan is successful then in the same command prompt run the system file check again.

    When you upgraded to windows 10 did you check on compatibility? The reason I ask is because your support page doesn't carry any win 10 drivers only win 8.

    Make sure everything is updated like browsers etc. Also can you create a recovery USB/disk?
    Creating a recovery drive - Windows Help -
    The reason i ask is because I want you to run the driver verifier. There is a chance that this will cause a bsod on start up so you need the recovery media so you can boot into safe mode and turn the verifier off.
    Oh can you clear the minidump folder too as I only need to see the new dumps, thanks. This guide will show you how to use the verifier:
    How do I fix a Blue Screen in Windows using Driver Verifier?

    Post any new dump files.
     
  7. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Ok I just finished running Furmark at 6048 x 1080 and it had no problem finishing the burn-in test and held steady at a top end temperature of 80C. I have a Thermaltake liquid cooler for the CPU so I dont think temperatures are going to be a big issue but I'll run the Prime95 test next.
     
  8. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Thanks for the quick recview. Comments below:

    Yes, that appears to be the latest driver from Steelseries. I'll check again and confirm though.
    No I didn't. Any guidance on checking would be appreciated. Is there a tool that is available?
    The DISM command worked and I'm in the process of re-running SFC.
    I made a recovery disk and will run Driver Verifier in a few minutes.
     
  9. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    OK SFC now completed with no errors.

    I'll run the driver verifier next.
     
  10. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    Sounds good HaggisDog, thanks for updating too. Don't forget about testing the cpu for temps.
     
  11. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    OK. I ran the driver verifier and it immediately led to a BSOD. In fact Windows couldn't get past its start screen. I rebooted into Safe mode and turned off Verifier. The dump is attached, it looked like it might be related to my Samsung 840 EVO Drive. I'm running Samsung Magician magic and the firmware is up to date.

    I reran the Prime96 CPU test and also the CPU temperature from Passmark and there were no issues.
     

    Attached Files:

  12. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    Hmm... well the only dump files I found were the ones sent post #5. You'll notice it's exactly the same file. There should be two dump files dated 29-11-15 but there's only one. I think because the folders had the same file name it (the forum) has somehow posted your old upload. Can you please clear out the minidump (found in the main windows folder) folder apart from your last dump file (save them to another location if need be) and when you next post please call it something different to the date.
     
  13. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    I noticed that it was updating the same directory but I thought it had over-written the files. I can resend later when I get home. Should I re-run the Driver Verifier to catch the BSOD it caused?
     
  14. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    You could always try it but as i said please clear out those old dump files first. Thanks for the update.
     
  15. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Attached is the latest dump from a BSOD. Let me know what you would suggest based on this.
     

    Attached Files:

  16. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {ffffe002601822e1, 2, 8, ffffe002601822e1}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+248 )
    
    Followup: MachineOwner
    
    Hi,
    I checked the dump files dated 30-11-2015 and one was a bugcheck 1A which is memory management error and D1 which means a driver accessed invalid memory.
    I don't think you have bad memory but could be wrong. I know you have tested already so we will leave the memory side of things but may come back to look at this area again if my next suggestions prove fruitless.
    Please update these drivers:
    I need you to update your chipset drivers. Now with AMD you have to go along to the gpu driver page and then click 'optional downloads' to find the chipset drivers. I've got a link to the windows 10 version but if it doesn't work try the version for win 8:
    Desktop
    snip.JPG

    rt640x64.sys Thu Jul 23 09:53:50 2015: Realtek Network driver. Please replace with this driver:
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

    Your also missing a sound driver:
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

    As your using an SSD is the system set to AHCI?

    Also you never got back to me regarding Prime95 and temperatures.

    Post any new dump files after updating the above.
     
  17. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Thanks for the review. I'll update the drivers when I get home.
    Yes, it is running AHCI.

    I re-ran the Prime95 and didn't encounter any temperature issues. I ran some PassMark stress tests on the CPU and it passed without problem. I checked my Thermaltake cooling system too and made sure it was topped up and cleaned out any dust that accumulated, I have 5 additional fans in my case and generally airflow is pretty good.
     
  18. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Installed

    Installed (although since I primarily use my Logitech g930 I rarely use my external speakers).

    The only challenge I had was with the chipset drivers. I tried installing the Win10 drivers but the application kept hanging at 2% and I had to kill the process through Task manager (I ran the app as Admin). So instead I installed the Sata controller driver manually (I presume that was what you were suggesting).

    I'm a little concerned that this might indeed be a memory issue though. Any suggestions on testing memory outside of Memtest86?
     
  19. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,803
    Likes Received:
    1,563
    I have dealt with similar issues where memtest86 refused to find an issue (could be down to simply not being run for long enough, even longer than 12hrs). So the other way you could test and I've found successful is to run the system one or two sticks at a time. If you get a bsod, make a note which stick or sticks and then swap (assuming you have four sticks of course). If you find a pair or a stick which doesn't bsod but the others do then you know which are are the bad sticks.

    And yes i was referring to the sata/ahci driver.. :)
     
  20. Haggisdog

    Haggisdog New Member

    Joined:
    Nov 28, 2015
    Messages:
    18
    Likes Received:
    0
    Just an FYI, I was travelling a little this week so haven't had a chance to really use my computer. I'll have more opportunity this weekend and will let you know what the status is. I can say that the number of BSODs has dropped substantially so that's obviously encouraging.
     

Share This Page

Loading...