Weird behavior after blue screen

Chrmdthm

Honorable
Feb 2, 2014
8
0
10,510
Hello. My computer is acting weird after a BSOD. It takes a very long time to run some programs at startup. I notice that programs that have the UAC popup take forever to appear. For example, if I click on MSI Afterburner, I have to wait over a minute before the UAC popup appears (the program starts instantly after I press yes). I will refer to this wait time as "busy wait" for the rest of this post. To strengthen my observation, my antivirus does not have a UAC popup and it starts instantly. Also, my internet has the "busy connecting" symbol during the busy wait and I have internet access. My control panel has the same issue. It does not load any of the actions (uninstall, add or remove accounts, etc.) until the busy wait is over. I believe the busy wait is because the CPU is doing something very heavy during startup. However, task manager (which opens automatically) shows my CPU barely breaking 50% most of the time. After this busy wait, everything is normal except for occasional freezes and blue screens (every two days or so).

Here is some background information that might be useful. Here are the parts:

  • -FX 6300
    -PNY XLR8 120GB
    -Seagate Barracuda 1TB
    -ASUS M5A78L-M LX PLUS AM3+ mATX
    -Cooler Master Hyper 212 Plus
    -Antec Truepower Classic 650C
    -G.SKILL Ripjaw X (4GB x 2)
    -MSi AMD Radeon HD 7790
    -Corsair Graphite Series 230T Mid Tower
My computer is a year and a half old. I have Windows 7 installed on my SSD and my leftover stuff on my HDD. I RMA'd my SSD for a new one about half a year ago because my old one was faulty (except I doubt that now). The temps on my computer are fine (according to HWMonitor and observation). I ran Prime95 and Furmark a while back and it was below 60 and 70 for the CPU and GPU respectively. No components are overclocked. I looked up issues like this and I found so many different reasons. I am positive it is not a driver issue. I read some things about RAM and I don't think it is a RAM issue except I haven't tested my RAM yet (I never had an issue with my computer until recently). I also heard about the PSU except I don't think that this is the mostly likely cause because it is a reliable unit from Seasonic. CrystalDiskInfo says both of SSD and HDD are in good condition so those should be good. Personally, I think it is my (SATA II) mobo that is bad, which is why I doubt all those things above.

Sometimes, I would freeze and my computer would restart and boot Ubuntu on my HDD. That is strange because I have my SSD is the primary boot drive. I would have to go into the BIOS and change my SSD to be the primary drive. This first time this issue happened was around three months ago. It was pretty rare and I thought nothing of it. However, the past month saw a huge spike in problems. First, I notice my computer does not wake up from sleep sometimes. My monitor is on with a black screen, my keyboard and mouse lights are off, and the hardware on my computer are running. There are also cases where the computer automatically restarts because of a problem like a BSOD but without the blue screen. During the restart, it is stuck or takes a very long time on the BIOS screen. I have to manually turn off my computer by pressing the power button. Now comes this problem above. I had the BSOD described at the top of the post maybe five days ago. I saw a glimpse of words that said hardware problem or something similar when Ubuntu was booting. Then the issue at the top of the post happened when I restarted to Windows. I thought it would go away, but it did not. Today, my SSD disconnected while my computer was running. I checked the cables and everything was good. I moved the SATA connection to another slot and my SSD was back. I remember tripping the anti surge protection on my mobo a few times a while back (before this issue). The thing is I don't know how this is possible. I have a Tripp-Lite surge protector and my PSU claims to have anti-surge protection.

Thank you for your help.


Edit: It could be my SSD (which means this is my second PNY XLR8 to fail in a year) or my ram (never had an issue before I RMA'd the SSD IIRC). I'll run a test for bad sectors and memtest tonight.
 
Solution
update the BIOS to a current version or reset it to defaults, reboot into windows

-change your memory dump to kernel memory dump.
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

-run cmd.exe as an admin, then run
verifier.exe /standard /all

set registry keys to allow you to force a memory dump:
http://blogs.technet.com/b/askpfeplat/archive/2015/04/06/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs.aspx or google "how to force a memory dump in windows" to find a better article

download rammap.exe from https://technet.microsoft.com/en-us/library/ff700229.aspx
run it and find the "empty" menu item, and empty the various lists by selecting each.

exit the program and reboot your system


Now, if your...
update the BIOS to a current version or reset it to defaults, reboot into windows

-change your memory dump to kernel memory dump.
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

-run cmd.exe as an admin, then run
verifier.exe /standard /all

set registry keys to allow you to force a memory dump:
http://blogs.technet.com/b/askpfeplat/archive/2015/04/06/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs.aspx or google "how to force a memory dump in windows" to find a better article

download rammap.exe from https://technet.microsoft.com/en-us/library/ff700229.aspx
run it and find the "empty" menu item, and empty the various lists by selecting each.

exit the program and reboot your system


Now, if your machine hangs you can force a memory dump and it can be looked at with the proper info so the problem can be debugged.
if your machine bugchecks it will have the correct debug info to help figure out the problem or suggest a solution.

if a memory dump file is not saved in c:\windows\memory.dmp then you have a problem in storage (drive, data cables, power cables, the SATA controller or the SATA controller port)

I can also look at a minidump .dmp file that would be in c:\windows\minidump directory and make some guesses as to the cause of the problems. You would just have to put them on a server and post a link.
The kernel memory dump more often has the required info that proves the actual cause of problems, if the cause is a driver.
 
Solution

Chrmdthm

Honorable
Feb 2, 2014
8
0
10,510
Hi johnbl. Thank you for the response. I have the latest firmware for my SSD (600ABBF0) and the latest BIOS version (1701 according to the ASUS website). I will set up the dump procedure tomorrow because it is getting late.

I tested my RAM with memtest86 for 16 hours and there were no errors. I only have one dmp file because the other bsods restarted before the dmp file was created. I took pictures of them though just for those reason. The one dmp file I have has bug check code 124 and is caused by ntoskrnl. The other two, which I took a picture of, have bug check code 7A and F4. I googled up these and they all point to my SSD.

I should also include that my first SSD was slow when I tested it using CrystalDiskMark. My mobo was SATA II, but it didn't even reach SATA II speeds (220/90MB seq read/write). That was the reason I RMA'd it. My second SSD (my current one that I got from the RMA) is also slow, but a little bit faster than the first. This was why I suspected the motherboard, but I don't know anymore.
 

Chrmdthm

Honorable
Feb 2, 2014
8
0
10,510
I figured out what was causing the lag during startup. I checked the event viewer and noticed that an oracle application was performing a lot of tasks during startup. I set those services to manual and that fixed the lag.

I also prevented my SSD from sleeping when the computer hibernates, and I updated some SATA drivers that I found from old posts. I haven't had an issue since. I am guessing my old BSODs (before I installed that oracle software) were caused by driver issues so my SSD is good. I am marking this as solved.

On a side note, do not pair the SSD I have with the mobo I have because it does not have good performance.