I've built this computer within the last month, though in the past couple weeks I've been getting weird BSoD errors that have recently been getting more frequent. Yesterday and today I've been getting BSoDs with error code 7a, and I'm thinking that it's a problem with the SSD's flash memory controller, though I'd like to confirm that before I go ahead and act on Samsung's warranty. Any help?
📎 AI Summary:
The thread revolves around a user experiencing frequent Blue Screen of Death (BSOD) errors, specifically code 7A, after building a new computer. The first responder conducts a detailed analysis, suggesting the issue may be related to memory corruption or disk hardware errors, and recommends updating firmware (particularly for the SSD) and BIOS, checking drivers, and running diagnostics like chkdsk and Memtest86. Overall, the response emphasizes troubleshooting hardware and software components to identify the cause, without a definitive diagnosis but leaning toward hardware issues such as SSD or RAM faults.
The thread revolves around a user experiencing frequent Blue Screen of Death (BSOD) errors, specifically code 7A, after building a new computer. The first responder conducts a detailed analysis, suggesting the issue may be related to memory corruption or disk hardware errors, and recommends updating firmware (particularly for the SSD) and BIOS, checking drivers, and running diagnostics like chkdsk and Memtest86. Overall, the response emphasizes troubleshooting hardware and software components to identify the cause, without a definitive diagnosis but leaning toward hardware issues such as SSD or RAM faults.
Solution
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,160
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc4000a960, ffffffffc000000e, 1b0bc860, fffff8800152cdc4}
GetPointerFromAddress: unable to read from fffff80002f0f278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
Code:
DISK_HARDWARE_ERROR: There was error with disk hardwareyou have a number of different dump files which in itself can point to a hardware error although sometimes it can be down to a missing update or suspect driver or process.
Check your Evo 840 is running with the latest firmware EXT0BB6Q.
Run a chkdsk (it's fine to run chkdsk on SSD's as I also own an Evo so checked this out personally):
Link Removed
BiosVersion = V1.6
BiosReleaseDate = 12/02/2013
Your Bios has an update pending:
- Improved RAID card compatibility.
- Improve memory compatibility.
- Updated VBIOS and GOP Driver.
- Supported Haswell-Refresh CPU.
Link Removed
It's critical you ensure I have the correct web page for your motherboard so please double check.
sptd.sys Thu Oct 31 15:26:53 2013: SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7) please uninstall to test.
If the bsod continues after making the above changes please run Memtest86. The latest version can be found here:
http://www.memtest.org/
This guide although a little old will show you how best to use it:
http://www.techspot.com/community/topics/tutorial-how-to-use-memtest.62524/
Post any new dump files.
