Slowdowns, crashes, BSODs

[Narf the Mouse]

Shortly after starting, my computer will usually either glitch and hang, or eventually BSOD. Previously, I found my PSU was over-volting. Replacing the PSU did not solve the problem.

The last crash dump file is attached; all of them can be attached, if needed. System specs can be provided; however, I am hesitant to start my computer again, due to the possibility of further damage. If the information provided is insufficient to diagnose a problem, however, I am willing to do so.

 

[peebee]

Multiple crash dumps is always preferred as trends are sometimes what bring coherency to a case.

The crash dump you provided doesn't really give any clues. A critical system thread (wininit.exe) terminated, which triggered a breakpoint and crashed the system.

If you can provide kernel dumps that would be even better.

 

[Narf the Mouse]

Ok, all the crash dumps in Windows\Minidumps are attached.

Where would I find kernel dumps? Google says they're in the %systemroot% folder, but Windows\ doesn't have any .dmp files.

I have the windows drive attached to the computer I'm borrowing as an external drive.

 

[peebee]

For kernel dumps you have to enable the option first. Then when the system crashes you'll find %systemroot%\memory.dmp.

I'll take a look at the other crash dumps in a little bit here (slightly distracted).

 

[Narf the Mouse]

Bumping for lack of response/update.

 

[peebee]

Sorry Narf, I got so distracted I forgot I'd even replied to you.

I looked at additional crash dumps that you provided and they reinforce my previous comment, except they're mostly due to csrss.exe (the win32 subsystem for usermode interaction). Specifically, it looks like a usermode process is hooking into csrss.exe and causing it to page fault, which triggers a break point. The machine then bug checks.

Something with this behavior really screams VIRUS, but without full dumps I'm not going to be able to tell you the exact process that was hooking into csrss.exe.

So in the meantime, I would suggest scanning your system with both a good antivirus and antimalware product. I believe many on here recommend Microsoft Security Essentials and Malware Bytes. I've used neither (I don't run AV), but I will trust the advice of other professionals on this forum.

If you would like more conclusive evidence of my suspicions then you'll need to provide a full dump (you can dropbox it or upload it to any file hosting site).

Hope this helps and please keep us informed on any progress.

 

[Arc]

Hi Narf the Mouse.

Search for any possible updates to your SSD's firmware: http://www.patriotmemory.com/support/driversp.jsp#

Post screenshots of both the HDD and SSD using CrystalDiskInfo - Software - Crystal Dew World

And ....

Additional information is required.

1. Download the Designer Media Log Collector application to your desktop by clicking the icon below

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

 

[peebee]

Hi Narf the Mouse.

Search for any possible updates to your SSD's firmware: http://www.patriotmemory.com/support/driversp.jsp#

Post screenshots of both the HDD and SSD using CrystalDiskInfo - Software - Crystal Dew World

And ....

Additional information is required.

1. Download the Designer Media Log Collector application to your desktop by clicking the icon below

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

Arc,

Thanks for offering additional advice. I'm curious, what's telling you that this is an SSD firmware issue? Is it a known issue with that particular make/model?

 

[Arc]

Arc,

Thanks for offering additional advice. I'm curious, what's telling you that this is an SSD firmware issue? Is it a known issue with that particular make/model?

It is not certainly a SSD firmware issue, but it is some storage related issue. May be the firmware is up-to-date; and in that case it will be something else with the storage. And that is why additional information is required, to see what is going on with the storage environment.

And, a minidump is enough in this case. Even, in most of the cases, a dump is also not required, the bugcheck code is enough information here. You need not to pay any attention to csrss.exe and/or wininit.exe.

But, it may be VIRUS too, as you suggested. Though it is not looking like that, apparently; but the possibility cannot be nullified at all.

See, in the supplied link, the "probably caused by" is saying neither csrss not wininit. It is a very rare case.

 

[Narf the Mouse]

Running virus and malware scans; will report back the results and try a firmware update afterwards. After that, I'll run the crash dump program.

So, expect a report back in about 24-48 hours, I guess.

 

[Narf the Mouse]

AVG reported a few problems, which is cleared.
Malwarebytes Anti-malware reported no problems.

Proceeding with firmware update.

 

[Narf the Mouse]

Apologies for the lack of deadline update; the plan is to leave it on overnight, so expect a report in 24-36 hours (depending on possible crash(es)).

 

[Narf the Mouse]

Ok, so finding the Memory.DMP file in %SystemRoot% works a lot better if I show protected operating files. D'oh. It's now transferring; should be available in 35-50 minutes.

I take it the entire 947 MB file is not needed, and the program referred to will extract the stuff that actually says what caused the crash?

I'm on a borrowed computer, currently.

Oh, and Firmware update: It already had the latest firmware, but I re-updated it to make sure. So, virus-scan, malware scan and firmware update done. The slowdowns/crashes still occur; possibly hasn't been enough time for a BSOD, yet.

 

[Narf the Mouse]

And the Designer Media Log Collection file it created from my computer.

 

[Arc]

Post screenshots of both the HDD and SSD using CrystalDiskInfo - Software - Crystal Dew World

Uninstall MagicDisc.

Re-seat the sata and power cables.

• 

If possible, change the SATA cables, and apply them to other unused ports to the motherboard.



Let us know for any further issue.

 

[Narf the Mouse]

Post screenshots of both the HDD and SSD using CrystalDiskInfo - Software - Crystal Dew World

Uninstall MagicDisc.

Re-seat the sata and power cables.

• 

If possible, change the SATA cables, and apply them to other unused ports to the motherboard.



Let us know for any further issue.

Both rate as good, and between your post and something that I noticed plugging the SSD in, I believe the problem has been found. The problem itself is why I don't want to plug it back in again...

Ah. Checking "Is MagicDisc safe" on Google sure gets some alarming reviews.

...Namely, the power and data plug-ins on the SSD wiggle if you put a little bit of pressure on them.

I'll be taking it into the shop I bought it from for either warranty replacement, or if it's out of warranty or out of stock, hopefully some solder and glue. (They do repairs as well as sales)

If not, some shop in the area should be able to solder and glue it.

Pending no further problems in the immediate future after that, I think we can call this one solved.

Thanks.