several BSOD's

Sleeepy2 · 13 Aug 2010

Ok Malwarebytes run = clean
Updated the graphics driver again just to make sure.
Memtest86 = ?? bad not sure how to read it other than bad
1st image I ran it and got all kinds of errors on tests 3 and 4 (I assume it is just from the ram in slots 1 and 3)

So I thought that 1 and 3 just didn't play nice together. So I swap the chips in slots 1 and 2 and try it again just to see what happened and it runs fine no errors. Boot up and all is good. Get home from work to find a nice new BSOD

Run Memtest86 again and now I have failures all over the place for the chip in slot 3

The strange thing is, take a look at the RAM settings between the 2 pics, First one is 4-4-4-12 and the second one is 5-5-5-18. o_O
What gives, I didn't change anything.

Any suggestions on where I go from here?
TIA

CarlTR6 · 13 Aug 2010

Remove all of your RAM except one stick and test that stick. If it shows no errors, remove it and test the next stick, repeat until you have tested all of the sticks. Post back with the results.

If all of the sticks test good, take a stick and test in each slot to see if you have a bad slot. Post back with the results.

Sleeepy2 · 13 Aug 2010

Will do, how many passes should I let Memtest86 run?
This could take a while :)

Thanks for the quick response.

**Capt.Jack Sparrow** · 13 Aug 2010

Sleeepy2 said:

Will do, how many passes should I let Memtest86 run?
This could take a while :)

Thanks for the quick response.

Hello,

It's recommend to run atleast 6 passes. You can run it over night it might take a while to complete all 6 passes.

- Captain

CarlTR6 · 13 Aug 2010

Sleeepy2 said:

Will do, how many passes should I let Memtest86 run?
This could take a while :)

Thanks for the quick response.

Captain Jack is spot on. Yes, it is a frustrating, time consuming process. :)

**cluberti** · 13 Aug 2010

The thing I usually do in this scenario is declare them all bad, and RMA them all with whomever I purchased them through, for what it's worth.

Sleeepy2 · 18 Aug 2010

GRRR.
OK I ran all the tests win a minimum of 8 passes each.
All 4 chips individually - no errors
All 4 slots in the mother board individually - no errors
2 chips in each of the matching slots (1-3 and 2 -4) - no errors.

PC ran 2 days with no BSOD so I thought yeah, maybe my ram just needed to stretch it legs. lol
This morning I woke up to a wonderful Blue Screen. Aggh. Dumps etc attached.

I wish I just could figure this out for sure what was causing it and uninstall, format, buy new hardware or what ever grrr.
I had this same issue a while ago, I have formated and changed operating systems (Win Xp to Win 7), new mother board, cpu, power supply, this ram is the RMA'd ram, two new hard drives. Damn I would get a new video card also if I just knew that would fix the damn thing.

Thanks to all that have been helping me on this. Any suggestions for the next steps?

ttran · 18 Aug 2010

This time it pointed to your hard drive, have you done hard drive diagnostic so far?
Disk Check
HD Diagnostic

I see you have old driver:

Code:

PxHlpa64 PxHlpa64.sys Thu Oct 18 01:25:02 2007 (4716537E)

Sonic CD/DVD driver (used by many different CD/DVD programs)
Go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK
This will break your CD/DVD program, but can easily be renamed after we've finished.
Please enable driver verifier:
Driver Verifier - Enable and Disable

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.278\081810-21153-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a0e50
Debug session time: Wed Aug 18 15:16:03.061 2010 (UTC + 7:00)
System Uptime: 2 days 17:50:37.937
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880031af7d8, fffff880031af040, fffff880014ed38e}

Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownStructures+18e )

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

Regard,

Tuan

Sleeepy2 · 19 Aug 2010

Thanks for the suggestion.
I ran everything remotely from work so I don't know what the results were however after running the disk check and then turning on Driver Verifier it booted back up so I will see how it goes.

Thanks again

Edit:
Damn scratch that - it booted back up yesterday however I just tried to connect now and I can't. I am guessing that I will have a nice BSOD when I get home from work.