Windows 10: Frequent and Numerous BSOD: Win10 64-bit

Hi! I've been seeing frequent BSOD ever since I upgraded to Windows 10. (Approximately 10-12 occurrences per month since March.) These include IRQL Not Less Than Or Equal; System Service Exception; PFN List Corrupt; Memory Management; Driver Overran Stack Buffer, etc. I suspect a bad driver has caused corruption somewhere, and I'd like to isolate that rather than reimage, if possible. Here are some things I've tried: (probably not in exact order)

• Malwarebytes and Superantispywere scans
• Performed a Windows 10 reset.
• Updated graphics drivers, audio drivers, and network adapter drivers from Lenovo Support.
• Followed WinDBG Debug instructions here. (Isolated suspect drivers with !thread and dps where possible.)
• Tried running DISM /restorehealth (Not successful - corruption and hatch mismatch on corrupted file.)
• DISM: Tried mounting iso from both MediaCreator Tool and also Tech Bench.
• DISM: Tried using Image_Health.cmd referenced here.
• Ran sfc /scannow - "Cannot repair member file."
• I realized that the DISM error (corrupted opencl.dll) was probably just a rabbit hole. Refocused on WinDBG.
• Ran memtest86 - one pass, no errors.

I'm ready to throw in the towel and ask for help - especially since I don't really understand what I'm reading in the crash dumbs. I'm attaching the debug zip file from the log collector. Any guidance would be appreciated!

:)

 

Fresh Win10 Home 64-bit frequent BSOD while using Chrome

Hello Qian,

Thank you for your response.

I appreciate your time.

I would suggest you to refer the following articles and check.

Refer:

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL

Bug Check 0x4E: PFN_LIST_CORRUPT

Bug Check 0x4E PFN_LIST_CORRUPT

Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

Bug Check 0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY

Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS
settings can be solved. Modifications of the settings are at your own risk.

Please keep us updated.

Thank you

 

Fresh Win10 Home 64-bit frequent BSOD while using Chrome

Just update:

1. I scanned my Ram using memtest86 and windows memory diagnostics and there is no ERROR.

2. I have updated all my drivers using SlimDrivers;

3. This is a new PC I received last week and I did a disk format & OS installation. I didn't make any big change on the fresh OS.

 

First problem is you are way behind on updates. You're still at 10240. you should be at 10586.318.

Please apply all updates then see if that has helped. There have been a lot of fixes since 10240 was released.

 

Also, you have a lot of very old drivers left over from the upgrade.

Code: 2008/09/24 02:28:20 PM C:\WINDOWS\system32\drivers\SiSRaid2.sys 2008/10/01 05:56:04 PM C:\WINDOWS\system32\drivers\sisraid4.sys 2009/06/04 09:53:40 PM C:\WINDOWS\system32\drivers\iaStor.sys 2009/06/23 04:28:14 PM C:\WINDOWS\system32\drivers\HECIx64.sys 2011/02/03 10:42:05 AM C:\WINDOWS\system32\Drivers\csrbcx64.sys 2011/04/11 02:48:16 PM C:\WINDOWS\system32\drivers\iaStorV.sys 2011/08/03 08:56:26 AM C:\WINDOWS\system32\DRIVERS\prepdrv.sys 2012/04/14 05:16:13 PM C:\WINDOWS\system32\drivers\iwdbus.sys 2012/11/26 07:02:51 PM C:\WINDOWS\system32\drivers\stexstor.sys 2012/11/27 02:52:34 PM C:\WINDOWS\system32\drivers\ISCTD64.sys 2012/12/11 04:21:44 PM C:\WINDOWS\system32\drivers\amdsbs.sys 2013/01/21 02:00:28 PM C:\WINDOWS\system32\drivers\vstxraid.sys 2013/02/04 02:47:18 PM C:\WINDOWS\system32\drivers\bxvbda.sys 2013/03/15 07:39:38 PM C:\WINDOWS\system32\drivers\lsi_sss.sys 2013/03/26 05:36:54 PM C:\WINDOWS\system32\drivers\HpSAMD.sys 2013/06/03 06:02:39 PM C:\WINDOWS\system32\drivers\megasr.sys 2013/07/15 06:39:01 PM C:\WINDOWS\system32\drivers\netaapl64.sys 2013/07/23 02:53:49 AM C:\WINDOWS\system32\DRIVERS\RtsPer.sys 2013/09/04 11:50:05 AM C:\WINDOWS\system32\DRIVERS\acsock64.sys 2013/11/15 02:59:34 PM C:\WINDOWS\system32\drivers\iaStorA.sys[/quote] If applying all Windows Updates doesn't help you may want to consider doing a Clean Install.
Windows 10 - Clean Install

If you decide to do this, make sure you backup everything you don't want to lose first, incluiding the current installed drivers. See here: Ethernet not working after using recovery drive - Page 2 - Windows 10 Forums

Get an external USB attached hard drive (1TB or so) and use a program like Macrium Reflect Free (or Pro) to make an image backup of your current system. That way no matter what happens you can always get back to where you are at the time the image is created.

 

That's what I was afraid of. Applying Windows updates now. I'll let you know. Thank you!

 

Hi hrn111,

Welcome to the 10forums *Smile

Besides that you're behind with the updates, the most recent build is 10586.318 FYI, I've noticed another problem.
You appear to be using memory of 2 makes & models, this can cause many problems and could be difficult to identify too.
It is highly recommended that you remove either of them, report back your situation in case a BSOD occurs again or if you're convinced the BSODs are gone (I hope it is the last *Smile )
To note, a clean install may help for some time but eventually the risk of BSODs occuring again will still be present while using mixed memory.
Code: [Memory Device (Type 17) - Length 34 - Handle 0006h] Physical Memory Array Handle 0005h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 4096MB Form Factor 05h - Chip Device Set [None] Device Locator ChannelA Bank Locator BANK 0 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer Samsung Serial Number Asset Tag Number Part Number K4B8G1646B-MYK0 [Memory Device (Type 17) - Length 34 - Handle 0007h] Physical Memory Array Handle 0005h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 0dh - SODIMM Device Set [None] Device Locator ChannelB-DIMM0 Bank Locator BANK 2 Memory Type 18h - Specification Reserved Type Detail 0080h - Synchronous Speed 1600MHz Manufacturer 1315 Serial Number Asset Tag Number Part Number CT102464BF186D.M16 [/quote]

 

[/quote] Thank you!! I wish I'd seen this sooner - I think I need to adjust my notification settings for comments. So applied the latest build update - unfortunately blue screens continued. Yesterday I did a clean install of Windows 10 Build 10586 and was in the process of installing the latest updates when I blue screened. I will pull the 4 GB out and see how it goes. This does seem logical though as a lot of the seemingly random BSODs have referred to memory in some way. (Memtest first pass had no errors - I should have let it run longer.) Anyway, I'll follow up with results after pulling memory. Thank you again!

 

I removed the 8 GB stick, as the 4 GB Samsung isn't removable. So far so good - no blue screens yet! (I'm purposely adding a "jinx" here as part of testing...)

Editing this comment to mention that I only just removed memory on Tuesday evening, so I'm on day 2 of testing for blue screens. I'll update this thread again on Tuesday (if all goes well), and mark as solved.

 

Thanks to both of you for your input. It looks like the mixed memory was the culprit. I haven't had a single BSOD since I removed the 2nd stick. Thank you!

 

Glad to hear all is well.