BSOD becoming more frequent please help

Well, this is doing my head in. I am usually good at solving a problem by narrowing down the issue but this one is giving me a headache.

My setup is in my sig underneath. (Asus P8P67M, Intel 2500k , 8GB Corsair XMS, 128GB Crucial M4 SSD and 500GB Samsung F3, Sapphire Vapour X 7950 3GB)

• Basically I can be browsing internet, playing games etc and I will get a BSOD.
• I/O Error comes up.
• When the computer reboots it says BOOTMGR Cannot be found and won't load windows.
• If I go into BIOS it does not list my SSD in the boot priority list. But rather, lists my WD secondary drive (holds my files of music etc) instead.
• If I turn off computer and unplug WD drive the computer boots into the SSD as normal.
• I can then reboot computer and recconnect WD drive and all works again until I get another random BSOD.

I have tried running with just the SSD but still got a BSOD last night.

I have ran CrystalDiskInfo and it detects no issues at all. I have ran Memtest and it also detects no issues at all.

So, I don't know what the issue is? I thought it was my SSD which was faulty but now I don't know!

Any help is appreciated.

Mark

Does sound like a issue with the SSD personally, what firmware version are you currently running on it?

I have absolutely no idea. Let me check haha.

According to Crystal it is '0001'

Just crashed again. Before it happened. Everything became non respondent. Trying to use internet it said 'waiting for cache' then i got the BSOD.

I( should say that this setup has been working perfectly for a few years. It is only in the past few months it has been messing me about!

Their have been a lot of firmware updates since then lol, might be worth updating it fixes a lot of issues with the drive itself.

http://uk.crucial.com/gbr/en/support-ssd-firmware

Other options being the sata cable itself, only seen that a few times or try changing the sata port the drive is running from.

Change sata cable on ssd.
Different sata socket
As above firmware
Which memtest? The older versions apparently don't work anymore.
Recent thing due to it being hotter?

Clutching at straws if you haven't guessed already :/

Already changed lead and slot to no avail. I have not done the firmware update but as it has only started recently I think it is more hardware related. I have owned the system for about 3 1/2 years with no problems? If anything ym new house is cooler than my old flat :P

I will get a new version of memtest now and check that.

I have also ordered a Crucial 256gb MX100.

I run 1 full pass of Memtest 5.01 and it found no errors.

Is there any software which checks an ssd for errors?

Did you try sfc/scannow from a command prompt with admin privileges.?
Edit: I had very similar issues on an ASUS P67 board. Ended up having to RMA it as the SATA was dieing on me.

it has to be SSD and/or motherboard related. No other reason why the SSD would be missing after the first reboot.

I've seen many SSDs do this. Some have been fixed with drive firmware, some with updates to the system ROM (if you use EFI, you can inject all the latest firmwares using "UEFI BIOS Updater" (UBU)....others have been RMAed or thrown away.

There have been a number of SSD firmwares with bugs that don't show util a certain amount of writes or uptime.....so firmware is still potentially on the cards even if the problem has just started happening.

Just update the SSD firmware or it'll crash within an hour of boot up forever. Once done, the M4 will be as good as new (the bug triggers after a set number of hours on: ~6 months up time).

EDIT: http://forum.crucial.com/t5/Solid-St...ur/ta-p/130218

I need to look up how to update firmware on an ssd first :P

Ok drive updated. Will see if that fixes it!

Unfortunately it crashed again.

BSOD win32k.sys

I tried using 'WhoCrashed' but "Crash dumps are enabled on your computer.

No valid crash dumps have been found on your computer"

Win32k.sys might be a red herring, best to cut back on the need to guess and get some logs to analyse first - please carefully read and follow the topic here: http://www.sysnative.com/forums/bsod...a.html#post303

If you can't attach the zipped folder(s) back here, upload them to a site that's publicly accessible (Skydrive/Live/ ... ) and post the URL here.

Think I did this right?

http://www.filedropper.com/windows7vistajcgriff2

Everything is pointing to the SSD, but I personally like to be 100% and will do the following to be certain and also to rule out a dodgy driver or O/S issue.

A quick and bare bones O/S re installation on a spare drive or your F3 500GB if you have space.

Then while the SSD is unplugged id do every task I can that replicates the issue fastest, just to be certain its now the SSD!

Once confident its not reoccurring, try a re-installation of the O/S on the SSD to rule out dodgy software/driver bugs.

Then continue with firmware updates for SSD/Mobo and searches for other exotic fixes..

Faulty SATA cable?

Already changed it. I have compiled the crash dumps in the previous page

Ah fair enough, definitely not overheating in this heat?

Which driver version does the drive display now? IIRC I had trouble flashing a drive over AHCI so had to set IDE mode in BIOS before it would work properly. As others have said, it sounds exactly like the known firmware issue with the drive, but the new versions should fix it.

It is the latest version: 070H

Close ... ;)

SP1 needed, this provides a number of fixes and System improvements.

No crash dumps saved, let's try to free up some boot time resources, use MSConfig and uncheck the below Startups:

SpybotSD <-- TeaTimer stop this from running, it can be a real hog and cause problems.

uTorrent<-- resource hog, stop it from auto starting.

Steam <-- start it manually ...

EADM <-- as above

kiespdlr <-- not likely to need to update the firmware on a Samsung 'phone each time you boot Windows

Gyazo <-- Not sure what this is, not needed during troubleshooting

There are multiples of the below error logged (?Internet Connection Sharing?):

Code:

---

Event[2]:
  Log Name: System
  Source: Microsoft-Windows-SharedAccess_NAT
  Date: 2014-07-22T16:08:32.000
  Event ID: 31004
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Mark-PC
  Description:
The DNS proxy agent was unable to allocate 0 bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.

---

Also several of the below (?possibly malware -related?):

Code:

---

Event[622]:
  Log Name: System
  Source: Microsoft-Windows-Wininit
  Date: 2014-07-22T12:15:43.859
  Event ID: 11
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Mark-PC
  Description:
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

---

I've scanned through several shutdown/crash points and don't see a reason logged, no obvious crash trigger/Service/driver failure.

After trimming the boot load with MSConfig, use Driver Verifier to try to flush out any bad driver, read and follow this carefully: http://www.sysnative.com/forums/show...r-BSOD-related

Also check that the PC is set to create minidumps: http://www.techsupportforum.com/foru...ps-655633.html

I think I will do a fresh install and see how I get on. That will help trim the system down. Unfortunately. The only OS I could buy at an OKish price was Windows 8.1 Pro :P

Why not just reinstall 7?

Unfortunately I can't remember my serial. I got the Windows through the MSDN Alliance while at uni. Now that I've left I no longer have access. Also if I change ssd I am quite sure it won't work either.

Quote:

---

Originally Posted by neonplanet40

Unfortunately I can't remember my serial. I got the Windows through the MSDN Alliance while at uni. Now that I've left I no longer have access. Also if I change ssd I am quite sure it won't work either.

---

http://www.magicaljellybean.com/keyfinder/

A SSD change is well within the EULA of a windows install.

Scrap all that anyway - you don't need a serial to install Windows 7 for testing. You get 30 days grace for activation. You can skip the key input (legitimately) as part of a standard install.

The MSDNAA license is still valid after you graduate (unlike a HUP key), so as Agent says you're breaking no rules.

I will see if I can locate the key then. May have saved it on my server. Will check tomorrow. Thanks!

The utility linked by Agent can extract it from the registry for you.

It gets me this: CD Key: BBBBB-BBBBB-BBBBB-BBBBB-BBBBB

Somehow I don't think thats the right key :P

Try running it as admin. If that doesn't work, it might be a volume license you've been issued, so it's not stored. In which case backing up the activation files might work, but no guarantees, and there's also a possibility it will break activation so only attempt it if you can't find your key.

http://forums.mydigitallife.info/thr...eys-and-retail
http://forums.mydigitallife.info/thr...s-8-activation

Here's another link with a non-register download. http://www.w7forums.com/threads/how-...indows-7.5711/

Edit: NVM, this one isn't for MAK installations so probably won't work here.

Edit2: Non-register links on this page: http://forums.mydigitallife.info/thr...-retail/page19

OK I think I'm done editing now. xD

Quote:

---

Originally Posted by neonplanet40

It gets me this: CD Key: BBBBB-BBBBB-BBBBB-BBBBB-BBBBB

Somehow I don't think thats the right key :P

---

Yup that's a MAK. No way of reading it out afaik. You needed to keep a copy of the key :( Although by now there is a chance that the amount of activations for it has been breached anyway.

I do now have Windows 8.1. Surely it\'s not that bad is it?

There\'s no way of extracting the key, but it is possible to back up the activation files and restore them to the new system. I did something similar successfully on an OEM-install laptop with a failing HDD where the owner had also peeled off the COA sticker. With this method though, I think activation will fail if hardware is changed before restoring.

Edit: Well I personally can\'t stand 8, but some don\'t mind it so it might be worth a try. The idea behind backing up the activation was to avoid spending money; if it\'s not the install causing the BSOD, this might not fix it anyway. You could try a trial from MS before breaking the seal on the CD if you\'re unsure about either.

Quote:

---

Originally Posted by neonplanet40

I do now have Windows 8.1. Surely it's not that bad is it?

---

Some of us really like it :)

Well I installed a new 256gb Crucial MX100 and Windows 8.1. So far, no problems . . . .

Glad to hear it. :)