BSOD Occurring Randomly in Windows 7, Suspect Hardware...

speaker717 · 23 Aug 2013

1. I ran Memtest previously for 10 passes with no errors. I will run it again though to be sure (does it test on-board system memory as well as the RAM?)

2. I ran the benchmark stress tests, no problems at all.

3. I loaded up DV--as I rebooted I selected my user and it began to load windows. Within 2-3 seconds my screen went haywire. (Black with varied lines throughout--propper frozen and locked up). I had a mouse cursor but i was completely frozen out and had to hard restart. Did it a second time, same effect. I had to go back through Safe Mode and restore from my safe point. I checked and (obviously because It didn't BSOD) I had no minidumps. Is there anything else I can grab to show the processes leading up to the crash(es)? to isolate it?

I was running DV on 'all drivers', should I have changed that selection to be more specific?

Arc · 23 Aug 2013

speaker717 said:

I was running DV on 'all drivers', should I have changed that selection to be more specific?

Run DV on all drivers those are not supplied by either "microsoft" or "unknown".

speaker717 · 23 Aug 2013

I've had two more non-BSOD crashes with DV running. Narrowed it down to only verifying half of the non-MS/Unknown drivers to see if that would help narrow it down at all.

speaker717 · 23 Aug 2013

I've crashed a few times, but most don't give me a dump, I restarted in Safe Mode (after a freeze up after I got back from walking the dog) and immediately had a BSOD, latest dump included.

Attachment 282900

Arc · 24 Aug 2013

Do some Disc checks.

Update your SSD's Firmware: Download SV300S3Toolboxv1, for SV300S3 | Kingston Technology
Reeat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
(Steps 3 and 4 are for the TOSHIBA 1 TB HDD only)

Let us know the results.
________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff88001f953a8, fffff88001f94c00, fffff8000247ae86}

Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueue+2a6 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050853
Arg2: fffff88001f953a8
Arg3: fffff88001f94c00
Arg4: fffff8000247ae86

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88001f9c578, fffff88001f9bdd0, fffff880012b2a53}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.

speaker717 · 24 Aug 2013

From looking at the site I don't see any firmware upgrades for my SSHD available. The Kingston toolbox brings up the serial number, firmware version, etc., but I don't have any options for upgrading the firmware. I looked further on their site, and unless I'm missing something (quite possible), I don't see any available firmware upgrades for my particular SSHD.

products

I'm working through the other steps now on the Toshiba Drive.

speaker717 · 24 Aug 2013

Arc-

I didn't come up with any errors on the Toshiba drive (and didn't have any non-backed up data on it)--so I decided to do a little troubleshooting..

I disconnected the SSHD and installed a fresh copy of windows on the Toshiba HD. Shortly after getting it up and running.. I hit a BSOD! - Attachment 283028

I also had 1-2 more while running off my SSHD: Attachment 283029

I thought the extra data (from the dump when it crashed on the Toshiba) may be useful at this point.

My gut all along has told me that there is a problem with the motherboard (defect?) I'd sent it back to Gigabyte a month ago and 2.5 weeks later they sent it (or one?) back with no note about what they had done, if anything (Not happy with their customer support, but that's not here nor there at this point).

After this last test (testing booting off two completely different HDs with fresh installs and still getting BSOD), and having swapped my RAM with other DIMMS and run memtest, I'm getting close to just thinking that either my processor and/or the motherboard is fuggered up. Thoughts? (Or maybe the most recent dumps will provide some info?)

Arc · 24 Aug 2013

What you have said about the motherboard is all possible. As it is generating versatile error/stopcodes, it is an indication of some drastic error, but we have no way to check a motherboard other than replacing it ... so we cannot say a board as corrupt so easily.

I can say that there is fair possibility, but the final decision is your

speaker717 · 24 Aug 2013

Yeah, I agree. Not the optimal option! But then I'm running out of any other logical option.

From what we're seeing, would you put it as more likely that the mother's messed up? or the processor? (I know it's an impossible to know, best guess?)

Arc · 24 Aug 2013

I dont think that it is the processor. For a failing processor, the indications would have been different. It is either a failing storage, or RAM, or motherboard.

You may test the processor .....
Hardware - Stress Test With Prime95