Windows 10: BSOD random times, target is likely to have memory corruption??

I have tried just about everything to figure out why my computer keeps crashing but I cannot seem to find out why. It is never a certain thing I am doing either. I could be on the internet, playing a game, or working on documents. It will give me different error codes as well, never the same. All the minidumps say something about memory corruption on the bottom but I have used memtest and all my ram sticks passed.

I am usually able to figure this stuff out but have no idea where to go from here, any help is greatly appreciated.

:)

 

ntoskrnl.exe+1640e0 BSOD error

So far, with one memory chip no BSOD. But, getting a BSOD would be random and infrequent.

I've went through that article in the past and still have gotten BSOD.

 

Constant Crashing / BSOD

Hey. I've been having issues with my computer crashing or bluescreening. The time inbetween the crashes are random, and the messages in the BSOD's are seemingly random. If you need anything to help ID the problem, please let me know.

Thanks for your time

 

Hi tomGrose4,

Code: BugCheck 1000007E, {ffffffffc0000005, fffff8076b7f139a, ffffc3010d5bf6d8, ffffc3010d5bef20}Probably caused by : bcmwl63a.sys ( bcmwl63a+15139a )[/quote]
BCM43XX TP-LINK 802.11 Network TP-LINK 802.11 Network Kernel Manual Stopped OK FALSE FALSE 4,096 4,235,264 0 12/10/2015 3:32:47 PM C:\Windows\system32\DRIVERS\bcmwl63a.sys 4,096

BCMWL63A Broadcom 802.11 Networ Broadcom 802.11 Networ Kernel Manual Running OK TRUE FALSE 4,096 4,235,264 0 12/10/2015 3:32:47 PM C:\Windows\system32\DRIVERS\bcmwl63a.sys

Code: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: The provider encountered an error while converting the basic disk to a dynamic disk. status=C0380013, Disk number=1[/quote]


Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread



Open device manager > expand network adapters > uninstall the broadcom drivers (bcmwl63a.sys)
Download and install new drivers.

See if you can use the Intel ethernet connection while working on the wireless driver.

 

BCM43XX TP-LINK 802.11 Network TP-LINK 802.11 Network Kernel Manual Stopped OK FALSE FALSE 4,096 4,235,264 0 12/10/2015 3:32:47 PM C:\Windows\system32\DRIVERS\bcmwl63a.sys 4,096

BCMWL63A Broadcom 802.11 Networ Broadcom 802.11 Networ Kernel Manual Running OK TRUE FALSE 4,096 4,235,264 0 12/10/2015 3:32:47 PM C:\Windows\system32\DRIVERS\bcmwl63a.sys

Code: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\config\DRIVERS' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: The provider encountered an error while converting the basic disk to a dynamic disk. status=C0380013, Disk number=1[/quote]


Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread



Open device manager > expand network adapters > uninstall the broadcom drivers (bcmwl63a.sys)
Download and install new drivers.

See if you can use the Intel ethernet connection while working on the wireless driver.[/quote] Thanks for the help, it has been a couple days since I have been able to work at my computer.
Windows Version 1703 (OS build 15063.413)

Windows PowerShellCopyright (C) 2016 Microsoft Corporation. All rights reserved.PS C:\Windows\system32> winverPS C:\Windows\system32> sfc/scannowsfc/scannow : The term 'sfc/scannow' is not recognized as the name of a cmdlet, function, script file, or operableprogram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At line:1 char:1+ sfc/scannow+ ~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (sfc/scannow:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundExceptionPS C:\Windows\system32> sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.PS C:\Windows\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.PS C:\Windows\system32> chkdsk /scanThe type of the file system is NTFS.Volume label is ssd.Stage 1: Examining basic file system structure ... 528384 file records processed.File verification completed. 28165 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 611898 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 41758 data files processed.CHKDSK is verifying Usn Journal... 35825752 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 487912015 KB total disk space. 99661152 KB in 176112 files. 113992 KB in 41759 indexes. 0 KB in bad sectors. 655127 KB in use by the system. 65536 KB occupied by the log file. 387481744 KB available on disk. 4096 bytes in each allocation unit. 121978003 total allocation units on disk. 96870436 allocation units available on disk.PS C:\Windows\system32>

 

Were you able to uninstall and reinstall the driver?
Have there been any recurrent bsod since the driver was uninstalled?

 

I just did it, my system crashed twice within an hour before doing it. Will give an update tomorrow. Thanks for the help.