Windows 7 - Win7 64, random crash, posible SSD problem?

My system is cca 2-3 years old, self buid, I was running Vista 32 bit without problems (without BSOD) all this time (exeption was Corel PaintShop Photo Pro X3, this one kept crushing, but just program, not OS), curently I add SSD and installed Win 7 Pro 64 bit, system looks stabe, fast, even Corel now runs perfectly, no crashing in Windows 7. I can choose OS at Boot with Acronis OS Selector.

Problems before BSOD:

I noticed particular problem with USB MASS STORAGE DEVICE, it keept coming up/down and windows couldn't find apropriate driver for this this device (Vista or Win 7) (there were no yellow "!" anywhere. Anyway, it seems that ALLinONE card reader crashed, I don't need it anyway so I unpluged it from the matherboard and problem is gone.

Second thing that I noticed is that SSD is not as fast as it should be at all, 125/122 MBs/s read/write. Googled, I found out the problem is in Marvell SATA III controler, I pluged SSD into Intel SATA II (yes, II) and gained almost 50% speed: 218/168. I ordered PCI slot for SATA III, I am waiting for it. AHCI is not on.

BSOD appeared twice in 2 days on Windows 7, when browsing internet, totaly random, when reading forum. It started with Firefox freezing, all aplications freezing, like there would be a cut-off from HD, mouse was still working and I could drag it arround, but no button worked. BSOD. I took screen shoot both time.

Question: Is it posible to find out from the attached screen shots (there is error raported) what caused BSOD?

Unfortunately all we can tell you without the DMP is;

The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.

Can you boot into safe mode (F8) and upload the DMP files to us?

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Hmmm, there is no Minidump folder or file in Windows. I went to sysdm.cpl and did all you said. I reboted into safe mode, but no Minidimp folder under Windows. Did I delete it with Registry booster? Will minidump appear next time on BSOD?

Edit: I saw you wrote on another thread:
"We dont recommend registry cleaners specifically for this reason. Win 7 doesnt usually need it."

So I should not use Registry booster? Whenever I run it after boot it finds something to delete. We should just let it be?

Today BSOD again after 3 hours. I was checking mail, reading news, waching a movie, then I read some forums for 30 minutes. Nothing special. PC frooze, BSOD. I went to Safe mode, no minidump folder in Windows. Dump files just don't get generated. Or don't get recorded (maybe HD controler crashes so they can not get written to HD??) Anyway, I found on another forum some posible reasons, why dump files are not recorded:

"There are many different reasons for not having memory dumps:
- Crash reporting not setup correctly.
- Disabled services
- Pagefile too small
- crash happens before the crash reporting mechanism has loaded.
- crash occurs below the level that Windows is able to recognize.
- other stuff (read the Windows Internals books for more info)"

Any idea what to do is greatly appreaciated!

Registry cleaners (and there two schools of thought on this) may do more harm than good, especially in non expert hands. I would not recommend its use.

Regarding DMP files:

They may be created elsewhere than minidump.Please search for *.dmp and upload them if found.

I uninstalled the Registr Booster. No *.dmp files on C drive. I did find some on E drive, but those being made under old OS (Vista 32), they are of older time and most of them are in firefox folder, one in OpenOffice folder, they do not relate to the current situation.

No crash today. I am waiting for the PCI/SATA III controler and more memory so all slots will be full. Then I'll do testing. What tough tests could I do? Memtest86+? How will Prime95 and PassMark BurnInTest affect SSD? What about Driver Verifier? Could I use that one now already?

Verifier doesn't test hardware so yes use it now.

When Verifier is running and BSOD occures, the message from Verifier will be in dmp file? I got one BSOD after 12+ hours using PC, still no *.dmp files on C. After reset HD (SSD) stuck (light for HD was shining), I got a message "No boot partition found". I turned it off/on and it booted normaly. I get PCI SATA III controler tomorow, should I uninstall Marvel SATA III controler (I don't use it anyway as SSD is on Intel SATA II?

DMP files are stored in memory then written to page file. If you have no page file (or it is on another drive) it may not be written.

RE: the marvel controller, if you arent using it you can either un-install it or disable it.

That's what I am saying, it is like SSD (or controller) would shut down and would not be able to save .dmp file. So Now I have just put in USB memory stick, 2Gb (I hope this would be enough), and I changed stings for the Small Dump Directory to record .dmp file there and caused BSOD with Bang to see if this is going to work. It does. Now I need to wait for the real BSOD and I hope that it will get written down. Also, after reset, I never got this screen before: