BSOD - Running out of ideas

[Jonathan_King]

I seem to be forgetting when these crashes happen.

What is the make/model of your PSU?

 

[Sirik]

The crashes happen randomly... this morning my pc had not long been on, it wasnt doing anything just being idle on the desktop when it happened.

my PSU is not that old, its a Corsair 1000w Modular PSU

 

[Sirik]

Hi Again,

I have another random Bluescreen again when my computer was idle.
any idea's what piece of hardware is causing this so i can replace it...this is really annoying.

 

[Jonathan_King]

Do you have another video card you can try? Try borrowing one from a friend or another computer.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 16:34:31.003 2010 (UTC - 4:00)
System Uptime: 0 days 4:03:49.986
BugCheck A, {15d0e1, 2, 1, fffff80002ee0880}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+250 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  sidebar.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Sirik]

I'm afraid I dont have access to another video card. Is that what you think the problem is?

 

[Jonathan_King]

I have to suspect some sort of video memory corruption. Try taking the computer to the local PC shop and having them test your card.

 

[Dave76]

Did your computer have the BSoDs since you built it?

If not, what software and/or hardware was installed before the blue screens started?
List everything, even if it seems un-related.

Did it start out as very seldom and slowly increased or start all of a sudden?

When you updated the BIOS, was this around the time the blue screens started?

Check your graphics card manufacturer site for FW (FirmWare) updates.
This has to be done separately, it does not come with MOBO BIOS or any drivers.
What is the brand and exact model numbers of your graphic cards?

When you ran memtest86+ was this with all the RAM cards installed?
How many runs did you do?

Do you have 6GB RAM?
What size are the cards? (3X2GB, 2X2GB and 2X1GB?)
How many cards are installed? (3 or 4?)
Did you buy these all at the same time? Same brand and P/N?
Have you ever bumped the north bridge voltage?

Check everything in the case for loose connections, possible grounding points.
Re-seat all cables.
This could be a grounding issue.

Check your MOBO for bulging or leaking capacitors.

What version is your MOBO?
P5E3 Deluxe?
Version E3468 or Version E3366?

If anything here doesn't help then you should do a bench test, take everything out of the case and set it up on a table.
PSU, motherboard, one RAM card, one graphics card and one monitor.
Take everything else out, no sound card etc.
Test if it will load BIOS.
Add HDD, see if it will run, test for BSoD.
Then add one component at a time until you get the blue screen.

Edit:

Just noticed this:

I have now uninstalled Rainmeter and disabled driver verifier.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.

You should resolve this issue before doing any hardware tests.
Try a restore point, run sfc /scannow, if you get the same message, choose an earlier restore point.
If this fails to resolve the problem, try a Repair Install.

 

[CarlTR6]

Originally Posted by Sirik
I have now uninstalled Rainmeter and disabled driver verifier.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.

You should resolve this issue before doing any hardware tests.
Try a restore point, run sfc /scannow, if you get the same message, choose an earlier restore point.
If this fails to resolve the problem, try a Repair Install.

Sirik, Dave's advice is spot on. You must get your system files properly working.

 

[Sirik]

I think i narrowed down the SFC problem...It was misreading the system files due to the "change" created by Windows 7 Universal Theme Patcher. When i reboot after doing an SFC it restores the theme files back to system default and SFC completes ok.. of course then i patch again.

My Computer did not bluescreen when i first built it 2 years ago. It started this year first only when i first turned it on, it would get to the desktop bluescreen, reboot, and then it would be fine for the rest of the day. then it start to progress to several random times a day.

I have not updated my BIOS, it came with the latest firmware and there are no updates available. it is a P5E3 Standard.

I have 2 Graphics Cards: 1x ATi 4870X2 PowerColor 1GB GDDR5, and 1x ATi 4870 Saphire 1GB GDDR5. Linked by Crossfire Cable, but Crossfire disabled most of the time in CCC. Drivers and CCC is the latest version, I dont know where to find Firmware on ATi's website so I've never done that.

I have run memtest86+ for 8 hours with all sticks in with no errors.
I have 4 Sticks of DDR3-PC10660 Geil RAM. All bought at the same time.
I have 2x2GB and 2x1GB all running at 1.5v default in the bios.

Motherboard does not appear damaged in any way.

I could try taking everything out as you suggest, but unfortunatly i need at least 1 of my ATi cards installed as my motherboard doesnt have an onboard graphics. This makes it tricky to test if its the motherboard causing the problem or the graphics card.

 

[Dave76]

Among other things, the bench test will eliminate any grounding issues, you can save this step until you have checked everything else.

You should follow Jonathan_King's advice and find a way to test with a different graphics card.

If you get another crash, uninstall Windows 7 Universal Theme Patcher, check if you still have crashes.
Have you checked for an updated version of this program?

You need to eliminate any possible causes of the crashes.

 

[Sirik]

Hi Dave,

I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.

 

[CarlTR6]

Hi Dave,

I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.

There is your clue. It runs fine with only one card, either card. With two, it crashes. I conclude that there is something wrong with, conflicting in your dual setup. Setting up dual cards is outside of my realm of experience.

I will leave this to the graphics card gurus and wish you the best in figuring out the problem.

 

[Sirik]

I decided to take my single 4870 out of my system so i could test for crashes using my 4870x2. Windows 7 Universal Theme Patcher is uninstalled also.

today shortly after turning my pc on i recieved the attached crash. again NTFS.sys.

 

[CarlTR6]

BugCheck 24 NTFS_FILE_SYSTEM - Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

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

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

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.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800124ce95 to fffff80002e7f740

STACK_TEXT:  
fffff880`096196b8 fffff880`0124ce95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`096196c0 fffff880`0124cae8 : 00000001`00000000 00000000`00000000 00000000`00000000 000001fb`00001000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`096197c0 fffff880`0109623f : fffffa80`094428d0 fffffa80`09442530 fffffa80`05acec30 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89
fffff880`09619870 fffff880`010946df : fffffa80`064de950 fffffa80`09442530 fffffa80`064de900 fffffa80`09442530 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`09619900 fffff800`02e711f2 : fffffa80`09442550 fffffa80`0645f9a0 00000000`00000043 fffff683`ff7b48c0 : fltmgr!FltpDispatch+0xcf
fffff880`09619960 fffff800`02e714f5 : fffffa80`09d97601 fffffa80`09d97601 fffff880`09619a60 00000000`00000000 : nt!IoPageRead+0x252
fffff880`096199f0 fffff800`02e9a8bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`09ba92a8 : nt!MiIssueHardFault+0x255
fffff880`09619ac0 fffff800`02e7d82e : 00000000`00000008 00000000`00000051 ffffffff`ffb3b401 00000000`000001f4 : nt!MmAccessFault+0x14bb
fffff880`09619c20 000007fe`f6918d60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`1bb3f938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f6918d60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsPagingFileIo+155
fffff880`0124ce95 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsPagingFileIo+155

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155

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

The dump does not tell us very much. I have to admit to admit that I am baffled by this. You have run chkdsk and well as Memtest. And you have run Driver Verifier. At the moment, the only thing I can suggest is to make sure your RAM is seated properly and that your connections to your hard drive are good.

 

[Sirik]

yeah i have tried all of that.... i think i will just replace it all when i get enough free cash together.

 

[CarlTR6]

I believe it is a hardware issue; I just can't put my finger on it.

 

[Dave76]

You need to test with another graphics card to be able to rule this out or confirm it's the cause.

If you need to find a shop that can do this for you, it will confirm the cause instead of guessing, then you'll know if it's the graphics cards and not RAM related or motherboard faults.

 

[Sirik]

I just thought I would post a bit of a closing post in this thread.
I replaced my motherboard and CPU and since then I have not had a single Blue Screen.
The replacements where made last saturday, so should have had at least 1 by now.

Thank you for all your efforts.

 

[Dave76]

Glad to hear that it's running stable.

Let us know if there are any other issues.

 

[CarlTR6]

That is good news! Thank you for posting back with the solution. Happy computing. Don't be a starnger to the forum.