Randomly having BSOD & sometimes freezes

[Kiwi1990]

Hi there,

I am working on a laptop, which is from a friend of mine.
The system is a Toshiba L660D-10J with Windows 7 HP x64.
It is a clean install with a normal Windows 7 DVD, instead of Toshiba's own.
(this because I changed harddrive and no DVD's were present sadly)
The harddrive was broken, so I replaced it with an newer SSD.
The system is around 1 - 1,5 years old. The Windows on it is 6 weeks old.

After having 2 brandnew OCZ AGT3-25SAT3-60G in it,
(which have been giving the same BSOD-problem I am having now)
I thought of incompatability, and tried a different one: Patriot PP60GS25SSDR.
Sadly the problem is still existent, so my guess it's not the harddrive.
I am thinking it is something with the HDD-controller, rather than something else.

I hope you guys can shine some light on my situation here,
as I am clueless about what to do.

Thanks for any help and advice you guys can give me.

PS: I've read some of the posts in your section with the same error code(s),
What I already did is:
- Scandisk (no errors, did it during startup)
- Enabled Driver verifier (which gave me some random freezes, so disabled it again)
- SFC /Scannow (which also gave me no errors)
- perfmonlog (reported no Antivirus, while AVG 2012 Free is installed/working)

 

[zigzag3143]

The status codes on all of these reflect this

0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

 

[Kiwi1990]

That's what I've already found out myself (I should have mentioned it, sorry!). I want to narrow down the problem, so that's what I could use help with..
Thanks for any help possible

 

[zigzag3143]

That's what I've already found out myself (I should have mentioned it, sorry!). I want to narrow down the problem, so that's what I could use help with..
Thanks for any help possible

\

Yell if you need help

 

[Kiwi1990]

I NEED HELP (like this?)


I am not very familiar with BSOD reports,
I know it is usaually bad, and most of the time solvable..
But I don't know what means what in the report..

Can someone help me with that?

 

[zigzag3143]

You have given us very little to go on. If the machine is still crashing please upload the DMP files.

 

[Kiwi1990]

Could you please check the attached ZIP-file..

everything you guys need is in there

(just as the guidelines are for posting about BSOD's on this forum!)

 

[zigzag3143]

All 7A' errors, all at the same memory address. We still need both memtest AND driver verifier.

There is a disk hardware error.

 

[Kiwi1990]

I'll do that as soon as I get off Fridays from work.

Thanks for your support!

 

[Kiwi1990]

I am currently running the memtests, how do I get a log-file from this program?
Also how do I get a log-file from Driver Verifier?

 

[writhziden]

You do not get log files from the memtest86+ diagnostics. Just let us know if you see any red error messages.

Driver Verifier will cause crashes. After at least 24 hours and up to 36 hours, upload your crash reports by following the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to let us analyze any new crashes. If you do not get new crashes, also let us know.

 

[Kiwi1990]

Okay thanks for the info.
I'll let memtest run this weekend,
when I get home I'll report if there are errors..

btw I did had freezes when I had driver verifier on last week,
but nothing showed up about that in the logs..
The freeze was a total freeze, only solution was manually turn off the pc..
I don't know if this is of some value to you guys?

 

[writhziden]

Freezes typically mean hardware. Prior to the Windows XP release, freezes were often software, but since then, they are usually hardware related. That is not to say that it cannot be software; I have helped a few users on here that did experience some software related freezes.

Let us know how the Memtest86+ diagnostics turn out.

 

[Kiwi1990]

Freezes typically mean hardware. Prior to the Windows XP release, freezes were often software, but since then, they are usually hardware related. That is not to say that it cannot be software; I have helped a few users on here that did experience some software related freezes.

Let us know how the Memtest86+ diagnostics turn out.

Thanks for your reply,
I just came home and saw that memtest runned for 47 passes (lol)
but with a total of 0 errors, so the memory is without doubt okay IMO.
I will enable the driver verifier once more now,
and hope I get something else than a freeze with no log/info !

 

[writhziden]

Alright, I wish you the best/worst of luck (blue screen wise, that is)!

 

[Kiwi1990]

Hmm, the system is running 2 days now, without any problems.
Isn't Driver Verifier supposed to force the system to crash?
Or did I misunderstand it's purpose?

 

[writhziden]

It is supposed to cause the system to crash if it is a driver issue. If it is hardware or even software (other than a driver), the behavior can be erratic and Verifier sometimes actually improves stability. I've seen this on two occasions: one when helping someone else on here who ended up finding the issue was USB port power related, and two when my own system was having some problems with a piece of software maxing out my RAM.

Also, make sure verifier is enabled. Start a command prompt (Start Menu -> All Program -> Accessories -> Command Prompt) and type

verifier /query

You may see a quick list of items scroll past in a separate or in the same command prompt. If it flashes too quickly to see if anything was listed, chances are, Verifier was not properly enabled.

 

[Kiwi1990]

Hmm the computer was working fine beffore it had to restart because of some updates..
Now it hangs at the windowslogo loading screen, and tries to make it work all failed..
Tried from windows-dvd, tried with startup recovery, trough safe mode and then recovery
(there it says no recoverypoints strangely, as there have been made plenty as I recall!)

Do you have any idea what the hell is going on here?
And the worst thing is.. Still no BSOD! so no log/further information on the original problem..

 

[writhziden]

If you can get into Safe Mode, disable Verifier through an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html.

verifier /reset

Also, make sure with http://www.sevenforums.com/tutorials/700-system-restore.html to use OPTION ONE, step 8. and the NOTE: in that step.

 

[Kiwi1990]

I've tried a lot to recover the system, including all your ideas.
Sadly none of them worked (and I do have a lot of experience recovering etc..).
Anyways, I reinstalled windows completely (clean install),
did all the updates and stuff, now running with driver verifier, so I hope I'll book some progress soon