Is my BSOD related to SSD or memory?How should I approach analysing this Windows crash dump?How can I resolve...
Should I take out a loan for a friend to invest on my behalf?
How to secure an aircraft at a transient parking space?
Does the nature of the Apocalypse in The Umbrella Academy change from the first to the last episode?
Do f-stop and exposure time perfectly cancel?
List elements digit difference sort
Can one live in the U.S. and not use a credit card?
PTIJ: wiping amalek’s memory?
PTIJ: Should I kill my computer after installing software?
How can The Temple of Elementary Evil reliably protect itself against kinetic bombardment?
Do I really need to have a scientific explanation for my premise?
Virginia employer terminated employee and wants signing bonus returned
What wound would be of little consequence to a biped but terrible for a quadruped?
Should I tell my boss the work he did was worthless
Shifting between bemols (flats) and diesis (sharps)in the key signature
How did Alan Turing break the enigma code using the hint given by the lady in the bar?
Bash script should only kill those instances of another script's that it has launched
How strictly should I take "Candidates must be local"?
Intuition behind counterexample of Euler's sum of powers conjecture
Can I pump my MTB tire to max (55 psi / 380 kPa) without the tube inside bursting?
Why doesn't this Google Translate ad use the word "Translation" instead of "Translate"?
Latex does not go to next line
Is "history" a male-biased word ("his+story")?
When traveling to Europe from North America, do I need to purchase a different power strip?
How many characters using PHB rules does it take to be able to have access to any PHB spell at the start of an adventuring day?
Is my BSOD related to SSD or memory?
How should I approach analysing this Windows crash dump?How can I resolve the BSOD BAD_POOL_CALLER 0x000000C2?Windows 7 BSOD after using 'volume shrink' on SSD C:Processor hanging and causing computer crash whilst playing gamesBSOD BCCode 124, request for analysis of my WinDGB logIntel SSD setting all files to read onlyanalyzing Windows 7 minidump2 years of memory corruption and BSOD… but no bad RAM?BSOD - WIN8_DRIVER_FAULTLaptop is crashing DRIVER_POWER_STATE_FAILURE (9f) and DPC_WATCHDOG_VIOLATION (133) The DPC
So I've been having a TON of BSOD's lately, and finally have been able to get dump files to save when my PC crashes. Previously, the system restarted too fast for me to read the stop code, and would reboot with something along the lines of: "NO BOOT DEVICE DETECTED. SELECT BOOT DEVICE OR PRESS A KEY TO CONTINUE". So I'd reboot, and everything works absolutely fine, no problems whatsoever, it always resolves after the first reboot. This cycle repeats, causing some hair pulling and many hours spent on google, in addition to some lost work files.
This has occurred about 40 times over the last 3 month(according to reliability history) , and the frequency just jumped from 1 per week to around 4-5 a DAY. I thought the problem was my HDD so I bought a new samsung SSD, which did not solve the problem (but it sure is nice and quick ;) ) I’ve also noticed in reliability history that my wireless adapter will occasionally stop working, possibly related?
The most recent BSOD (MEM_MANAGEMENT) produced a dump file, and analysing it finds the following:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000006001, The subtype of the bugcheck.
Arg2: ffffffffc000000e
Arg3: 0000000001a10000
Arg4: ffffad8d76960010
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:dump_analysisprogramtriagemodclass.ini, error 2
BUGCHECK_STR: 0x1a_6001
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: a8ae
LAST_CONTROL_TRANSFER: from fffff80169e0d473 to fffff80169dc80c0
The laptop I’m on is an Asus X556L, Intel i5-5200@2.20 gHz, 6 GB ram, 64-bit windows 10. Any suggestions how to resolve this particular problem? If I’ve missed any information let me know and I’ll update it.
Edit:
Could this be the physical connection of the SSD to the motherboard? Since replacing the drive made no difference, maybe the drive connections are preventing proper interfacing. This seems somewhat plausible except for that fact that the drive has no trouble during use, easily reaching read/write speeds of 400MBps (there is no cable, it plugs directly into a small chip that then connects to the MB)
Comments
-Yes, this is the only SSD in the system. It's a few months old, and has no problems indicated in either Samsung's built in SMART test or the diskcheckup utility.
Bluescreenview - this looks useful, will use later today
- Performed a memtest with windows memory test, no problems there either. I'll do an indepth test later tonight with memtest86 and post any interesting results. It may be of note that I can use essentially all 6 GB of ram with no issues, such as when Fortnite and Microsoft Edge are running simultaneously(uses 5.8 GB ram for hours on end, performance is fine)
windows memory ssd bsod minidumps
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 1 more comment
So I've been having a TON of BSOD's lately, and finally have been able to get dump files to save when my PC crashes. Previously, the system restarted too fast for me to read the stop code, and would reboot with something along the lines of: "NO BOOT DEVICE DETECTED. SELECT BOOT DEVICE OR PRESS A KEY TO CONTINUE". So I'd reboot, and everything works absolutely fine, no problems whatsoever, it always resolves after the first reboot. This cycle repeats, causing some hair pulling and many hours spent on google, in addition to some lost work files.
This has occurred about 40 times over the last 3 month(according to reliability history) , and the frequency just jumped from 1 per week to around 4-5 a DAY. I thought the problem was my HDD so I bought a new samsung SSD, which did not solve the problem (but it sure is nice and quick ;) ) I’ve also noticed in reliability history that my wireless adapter will occasionally stop working, possibly related?
The most recent BSOD (MEM_MANAGEMENT) produced a dump file, and analysing it finds the following:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000006001, The subtype of the bugcheck.
Arg2: ffffffffc000000e
Arg3: 0000000001a10000
Arg4: ffffad8d76960010
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:dump_analysisprogramtriagemodclass.ini, error 2
BUGCHECK_STR: 0x1a_6001
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: a8ae
LAST_CONTROL_TRANSFER: from fffff80169e0d473 to fffff80169dc80c0
The laptop I’m on is an Asus X556L, Intel i5-5200@2.20 gHz, 6 GB ram, 64-bit windows 10. Any suggestions how to resolve this particular problem? If I’ve missed any information let me know and I’ll update it.
Edit:
Could this be the physical connection of the SSD to the motherboard? Since replacing the drive made no difference, maybe the drive connections are preventing proper interfacing. This seems somewhat plausible except for that fact that the drive has no trouble during use, easily reaching read/write speeds of 400MBps (there is no cable, it plugs directly into a small chip that then connects to the MB)
Comments
-Yes, this is the only SSD in the system. It's a few months old, and has no problems indicated in either Samsung's built in SMART test or the diskcheckup utility.
Bluescreenview - this looks useful, will use later today
- Performed a memtest with windows memory test, no problems there either. I'll do an indepth test later tonight with memtest86 and post any interesting results. It may be of note that I can use essentially all 6 GB of ram with no issues, such as when Fortnite and Microsoft Edge are running simultaneously(uses 5.8 GB ram for hours on end, performance is fine)
windows memory ssd bsod minidumps
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is this the only HDD/SDD in the system?
– BillDOe
2 hours ago
1
Use bluescreenview to see all of your BSODs: nirsoft.net/utils/blue_screen_view.html
– HackSlash
2 hours ago
1
Use memtest86 to test your memory: memtest86.com
– HackSlash
2 hours ago
Look for S.M.A.R.T. errors with this: passmark.com/products/diskcheckup.htm
– HackSlash
2 hours ago
1
If you suspect your memory you need to test your memory with the appropriate tool. If you encounter no errors then you know it's not the memory.
– Ramhound
2 hours ago
|
show 1 more comment
So I've been having a TON of BSOD's lately, and finally have been able to get dump files to save when my PC crashes. Previously, the system restarted too fast for me to read the stop code, and would reboot with something along the lines of: "NO BOOT DEVICE DETECTED. SELECT BOOT DEVICE OR PRESS A KEY TO CONTINUE". So I'd reboot, and everything works absolutely fine, no problems whatsoever, it always resolves after the first reboot. This cycle repeats, causing some hair pulling and many hours spent on google, in addition to some lost work files.
This has occurred about 40 times over the last 3 month(according to reliability history) , and the frequency just jumped from 1 per week to around 4-5 a DAY. I thought the problem was my HDD so I bought a new samsung SSD, which did not solve the problem (but it sure is nice and quick ;) ) I’ve also noticed in reliability history that my wireless adapter will occasionally stop working, possibly related?
The most recent BSOD (MEM_MANAGEMENT) produced a dump file, and analysing it finds the following:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000006001, The subtype of the bugcheck.
Arg2: ffffffffc000000e
Arg3: 0000000001a10000
Arg4: ffffad8d76960010
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:dump_analysisprogramtriagemodclass.ini, error 2
BUGCHECK_STR: 0x1a_6001
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: a8ae
LAST_CONTROL_TRANSFER: from fffff80169e0d473 to fffff80169dc80c0
The laptop I’m on is an Asus X556L, Intel i5-5200@2.20 gHz, 6 GB ram, 64-bit windows 10. Any suggestions how to resolve this particular problem? If I’ve missed any information let me know and I’ll update it.
Edit:
Could this be the physical connection of the SSD to the motherboard? Since replacing the drive made no difference, maybe the drive connections are preventing proper interfacing. This seems somewhat plausible except for that fact that the drive has no trouble during use, easily reaching read/write speeds of 400MBps (there is no cable, it plugs directly into a small chip that then connects to the MB)
Comments
-Yes, this is the only SSD in the system. It's a few months old, and has no problems indicated in either Samsung's built in SMART test or the diskcheckup utility.
Bluescreenview - this looks useful, will use later today
- Performed a memtest with windows memory test, no problems there either. I'll do an indepth test later tonight with memtest86 and post any interesting results. It may be of note that I can use essentially all 6 GB of ram with no issues, such as when Fortnite and Microsoft Edge are running simultaneously(uses 5.8 GB ram for hours on end, performance is fine)
windows memory ssd bsod minidumps
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
So I've been having a TON of BSOD's lately, and finally have been able to get dump files to save when my PC crashes. Previously, the system restarted too fast for me to read the stop code, and would reboot with something along the lines of: "NO BOOT DEVICE DETECTED. SELECT BOOT DEVICE OR PRESS A KEY TO CONTINUE". So I'd reboot, and everything works absolutely fine, no problems whatsoever, it always resolves after the first reboot. This cycle repeats, causing some hair pulling and many hours spent on google, in addition to some lost work files.
This has occurred about 40 times over the last 3 month(according to reliability history) , and the frequency just jumped from 1 per week to around 4-5 a DAY. I thought the problem was my HDD so I bought a new samsung SSD, which did not solve the problem (but it sure is nice and quick ;) ) I’ve also noticed in reliability history that my wireless adapter will occasionally stop working, possibly related?
The most recent BSOD (MEM_MANAGEMENT) produced a dump file, and analysing it finds the following:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000006001, The subtype of the bugcheck.
Arg2: ffffffffc000000e
Arg3: 0000000001a10000
Arg4: ffffad8d76960010
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:dump_analysisprogramtriagemodclass.ini, error 2
BUGCHECK_STR: 0x1a_6001
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: MemCompression
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: a8ae
LAST_CONTROL_TRANSFER: from fffff80169e0d473 to fffff80169dc80c0
The laptop I’m on is an Asus X556L, Intel i5-5200@2.20 gHz, 6 GB ram, 64-bit windows 10. Any suggestions how to resolve this particular problem? If I’ve missed any information let me know and I’ll update it.
Edit:
Could this be the physical connection of the SSD to the motherboard? Since replacing the drive made no difference, maybe the drive connections are preventing proper interfacing. This seems somewhat plausible except for that fact that the drive has no trouble during use, easily reaching read/write speeds of 400MBps (there is no cable, it plugs directly into a small chip that then connects to the MB)
Comments
-Yes, this is the only SSD in the system. It's a few months old, and has no problems indicated in either Samsung's built in SMART test or the diskcheckup utility.
Bluescreenview - this looks useful, will use later today
- Performed a memtest with windows memory test, no problems there either. I'll do an indepth test later tonight with memtest86 and post any interesting results. It may be of note that I can use essentially all 6 GB of ram with no issues, such as when Fortnite and Microsoft Edge are running simultaneously(uses 5.8 GB ram for hours on end, performance is fine)
windows memory ssd bsod minidumps
windows memory ssd bsod minidumps
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 35 mins ago
Joel
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
JoelJoel
63
63
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Joel is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Is this the only HDD/SDD in the system?
– BillDOe
2 hours ago
1
Use bluescreenview to see all of your BSODs: nirsoft.net/utils/blue_screen_view.html
– HackSlash
2 hours ago
1
Use memtest86 to test your memory: memtest86.com
– HackSlash
2 hours ago
Look for S.M.A.R.T. errors with this: passmark.com/products/diskcheckup.htm
– HackSlash
2 hours ago
1
If you suspect your memory you need to test your memory with the appropriate tool. If you encounter no errors then you know it's not the memory.
– Ramhound
2 hours ago
|
show 1 more comment
Is this the only HDD/SDD in the system?
– BillDOe
2 hours ago
1
Use bluescreenview to see all of your BSODs: nirsoft.net/utils/blue_screen_view.html
– HackSlash
2 hours ago
1
Use memtest86 to test your memory: memtest86.com
– HackSlash
2 hours ago
Look for S.M.A.R.T. errors with this: passmark.com/products/diskcheckup.htm
– HackSlash
2 hours ago
1
If you suspect your memory you need to test your memory with the appropriate tool. If you encounter no errors then you know it's not the memory.
– Ramhound
2 hours ago
Is this the only HDD/SDD in the system?
– BillDOe
2 hours ago
Is this the only HDD/SDD in the system?
– BillDOe
2 hours ago
1
1
Use bluescreenview to see all of your BSODs: nirsoft.net/utils/blue_screen_view.html
– HackSlash
2 hours ago
Use bluescreenview to see all of your BSODs: nirsoft.net/utils/blue_screen_view.html
– HackSlash
2 hours ago
1
1
Use memtest86 to test your memory: memtest86.com
– HackSlash
2 hours ago
Use memtest86 to test your memory: memtest86.com
– HackSlash
2 hours ago
Look for S.M.A.R.T. errors with this: passmark.com/products/diskcheckup.htm
– HackSlash
2 hours ago
Look for S.M.A.R.T. errors with this: passmark.com/products/diskcheckup.htm
– HackSlash
2 hours ago
1
1
If you suspect your memory you need to test your memory with the appropriate tool. If you encounter no errors then you know it's not the memory.
– Ramhound
2 hours ago
If you suspect your memory you need to test your memory with the appropriate tool. If you encounter no errors then you know it's not the memory.
– Ramhound
2 hours ago
|
show 1 more comment
1 Answer
1
active
oldest
votes
Look at this.
You can see that, depending on "Parameter 1" (which is Arg 1 in the output you've included in your question) provides a lot of information.
- Microsoft says some of these are strong indications of hardware errors.
- Page files and therefore your SSD are involved in memory management, bui nothing in the above reference seems to suggest it could be triggered by an I/O error.
- The rest are errors that can happen in drivers or other kernel-level services.
MemCompression would certainly be a kernel-level thing, but it's not going to be something writing to disk.
Especially since you've already tried a different SSD, the two things left to eliminate are drivers/kernel-level software and then the hardware itself (motherboard or RAM).
- Make sure UEFI is at latest version.
- Make sure system is not overheating.
- Make sure power supply can handle all components in your system (search for a PSU calculator).
- Ensure all latest Windows and driver updates are installed. Driver updates can be obtained from manufacturer. If you have a discrete graphics card, ensure that driver is the latest.
- Replace RAM, PSU, motherboard in that order.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Joel is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1413232%2fis-my-bsod-related-to-ssd-or-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Look at this.
You can see that, depending on "Parameter 1" (which is Arg 1 in the output you've included in your question) provides a lot of information.
- Microsoft says some of these are strong indications of hardware errors.
- Page files and therefore your SSD are involved in memory management, bui nothing in the above reference seems to suggest it could be triggered by an I/O error.
- The rest are errors that can happen in drivers or other kernel-level services.
MemCompression would certainly be a kernel-level thing, but it's not going to be something writing to disk.
Especially since you've already tried a different SSD, the two things left to eliminate are drivers/kernel-level software and then the hardware itself (motherboard or RAM).
- Make sure UEFI is at latest version.
- Make sure system is not overheating.
- Make sure power supply can handle all components in your system (search for a PSU calculator).
- Ensure all latest Windows and driver updates are installed. Driver updates can be obtained from manufacturer. If you have a discrete graphics card, ensure that driver is the latest.
- Replace RAM, PSU, motherboard in that order.
add a comment |
Look at this.
You can see that, depending on "Parameter 1" (which is Arg 1 in the output you've included in your question) provides a lot of information.
- Microsoft says some of these are strong indications of hardware errors.
- Page files and therefore your SSD are involved in memory management, bui nothing in the above reference seems to suggest it could be triggered by an I/O error.
- The rest are errors that can happen in drivers or other kernel-level services.
MemCompression would certainly be a kernel-level thing, but it's not going to be something writing to disk.
Especially since you've already tried a different SSD, the two things left to eliminate are drivers/kernel-level software and then the hardware itself (motherboard or RAM).
- Make sure UEFI is at latest version.
- Make sure system is not overheating.
- Make sure power supply can handle all components in your system (search for a PSU calculator).
- Ensure all latest Windows and driver updates are installed. Driver updates can be obtained from manufacturer. If you have a discrete graphics card, ensure that driver is the latest.
- Replace RAM, PSU, motherboard in that order.
add a comment |
Look at this.
You can see that, depending on "Parameter 1" (which is Arg 1 in the output you've included in your question) provides a lot of information.
- Microsoft says some of these are strong indications of hardware errors.
- Page files and therefore your SSD are involved in memory management, bui nothing in the above reference seems to suggest it could be triggered by an I/O error.
- The rest are errors that can happen in drivers or other kernel-level services.
MemCompression would certainly be a kernel-level thing, but it's not going to be something writing to disk.
Especially since you've already tried a different SSD, the two things left to eliminate are drivers/kernel-level software and then the hardware itself (motherboard or RAM).
- Make sure UEFI is at latest version.
- Make sure system is not overheating.
- Make sure power supply can handle all components in your system (search for a PSU calculator).
- Ensure all latest Windows and driver updates are installed. Driver updates can be obtained from manufacturer. If you have a discrete graphics card, ensure that driver is the latest.
- Replace RAM, PSU, motherboard in that order.
Look at this.
You can see that, depending on "Parameter 1" (which is Arg 1 in the output you've included in your question) provides a lot of information.
- Microsoft says some of these are strong indications of hardware errors.
- Page files and therefore your SSD are involved in memory management, bui nothing in the above reference seems to suggest it could be triggered by an I/O error.
- The rest are errors that can happen in drivers or other kernel-level services.
MemCompression would certainly be a kernel-level thing, but it's not going to be something writing to disk.
Especially since you've already tried a different SSD, the two things left to eliminate are drivers/kernel-level software and then the hardware itself (motherboard or RAM).
- Make sure UEFI is at latest version.
- Make sure system is not overheating.
- Make sure power supply can handle all components in your system (search for a PSU calculator).
- Ensure all latest Windows and driver updates are installed. Driver updates can be obtained from manufacturer. If you have a discrete graphics card, ensure that driver is the latest.
- Replace RAM, PSU, motherboard in that order.
answered 29 mins ago
LawrenceCLawrenceC
59.5k11103181
59.5k11103181
add a comment |
add a comment |
Joel is a new contributor. Be nice, and check out our Code of Conduct.
Joel is a new contributor. Be nice, and check out our Code of Conduct.
Joel is a new contributor. Be nice, and check out our Code of Conduct.
Joel is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1413232%2fis-my-bsod-related-to-ssd-or-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is this the only HDD/SDD in the system?
– BillDOe
2 hours ago
1
Use bluescreenview to see all of your BSODs: nirsoft.net/utils/blue_screen_view.html
– HackSlash
2 hours ago
1
Use memtest86 to test your memory: memtest86.com
– HackSlash
2 hours ago
Look for S.M.A.R.T. errors with this: passmark.com/products/diskcheckup.htm
– HackSlash
2 hours ago
1
If you suspect your memory you need to test your memory with the appropriate tool. If you encounter no errors then you know it's not the memory.
– Ramhound
2 hours ago