Help Please

CarlTR6 · Jun 28, 2010

Very good, Joker. Please post back and let us know how your system is doing one way or another. If you don't get another BSOD in a couple of days, let us know and we will mark this thread as solved. If you get another BSOD, post back ASAP.

Fingers crossed!

joker007 · Jun 30, 2010

Thought it was too good to be true! Back to The freezing screens with horizontal lines which don't create mini dumps or if Im lucky a BSOD. I'll attach the latest mini dump if you guys would be kind enough to have a look at. I never had all these problems when using my nvidia gpu. Only started happening since HD 5850. I'm tempted to RMA but the card is superb in 3d and you don't see the reference design cards about anymore!

Lordbob75 · Jun 30, 2010

Again caused by memory corruption, with bugcheck 3b. This is likely to be your video card drivers, which sounds right on the mark with what you were saying.

You might try removing and reinstalling your video drivers, as admin.

Code:

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


Loading Dump File [C:\Users\DavidLap\AppData\Local\Temp\7zO2606.tmp\063010-26171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Wed Jun 30 12:49:02.697 2010 (UTC - 7:00)
System Uptime: 0 days 0:03:31.462
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff80002d7ca26, fffff88006f2cf70, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80002d7ca26, Address of the instruction which caused the bugcheck
Arg3: fffff88006f2cf70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nt!AlpcpReceiveSynchronousReply+36
fffff800`02d7ca26 44              ???

CONTEXT:  fffff88006f2cf70 -- (.cxr 0xfffff88006f2cf70)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88006f2da48
rdx=fffff88002f67701 rsi=fffff8a002d4b030 rdi=0000000000000000
rip=fffff80002d7ca26 rsp=fffff88006f2d940 rbp=fffffa80062a8060
 r8=fffff88006f2d9f0  r9=0000000000000000 r10=fffff80002a05000
r11=fffff88006f2d810 r12=fffff88006f2d9f0 r13=0000000000000000
r14=0000000000000018 r15=fffffa8006b94620
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!AlpcpReceiveSynchronousReply+0x36:
fffff800`02d7ca26 44              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002d7ca26

STACK_TEXT:  
fffff880`06f2d940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!AlpcpReceiveSynchronousReply+0x36


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002d7ca28 - nt!AlpcpReceiveSynchronousReply+38
    [ b6:b4 ]
1 error : !nt (fffff80002d7ca28)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff88006f2cf70 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

~Lordbob

Jonathan_King · Jul 1, 2010

I suggest RMAing the card.

joker007 · Jul 1, 2010

I will try a reinstall of the drivers yet again. I have been using driver sweeper to clear out all traces of the old drivers. This seems to work for a bit then its back to the crashing again. If its a no go again then its RMA time which is a shame. I think if I disabled powerplay things would be fine but I don't want to be running 3d speeds constantly. Just out of interest, after the last crash I had problems even booting into safe mode. After a mobo battery change finally got it to boot and had another mini dump. Is this still pointing to faulty video card? If so would It mean that AVG wasn't the culprit earlier in the thread? Thanks again guys.

CarlTR6 · Jul 1, 2010

This one is a bugcheck 50. It does not point to anything specifically. It is a hardware error.

joker007 · Jul 1, 2010

PC has been stable since the last install of 10.6 drivers but it did this last time and then started crashing again so not too hopeful. I have contacted MSI and given them all the details and will see what they say. Will probably involve flashing the gpu bios. Would love that to work as really love this card in 3d just not 2D. I have attached a pic of the screen when PC would lock-up and require a reboot. It would do this if I didn't get to the BSOD. Not the best of pics but shows the screen corruption.

CarlTR6 · Jul 1, 2010

That is definitely some screen corruption! Let us know what MSI has to say. I agree with Jonathan, I think it is time for a new card.

Lordbob75 · Jul 1, 2010

I agree as well. That is the second worst artefacting I have ever seen.

~Lordbob

joker007 · Jul 3, 2010

Hi guys. All seemed to be going very well until now. Just checked on PC and it had restarted and was left with the message;

File:\Boot\BCD
status: 0x000000f
Info: An error occurred while attempting to read the boot configuration data.

Befor I RMA the card was just wondering if it could be my motherboard or hard drive at fault and its just a coincidence things started to go wrong when I swapped GPU? I have run dskchk and everything was fine. I have also had a look at mobo and things look fine. No swollen or leaking caps. I'm gonna see if I can get hold of an nvidia card to see if things improve before I RMA ATI card. What do you guys think? Would it be worth formatting again? Tried this before and it was fine for a couple of days before it started playing up. Can you recommend some decent software to test hard drives? I have attached latest mini dump file to see if points to anything. Thanks again.

CarlTR6 · Jul 3, 2010

STOP 0x00000018: REFERENCE_BY_POINTER

Usual causes: Device driver, kernel, hardware

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\070310-24343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[url=http://msdl.microsoft.com/download/symbols]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Sat Jul  3 15:23:04.856 2010 (GMT-4)
System Uptime: 0 days 0:14:33.684
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa8005f52900, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46451 )

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

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa8005f52900, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This bugcheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object’s reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x18

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c52fac to fffff80002cbb600

STACK_TEXT:  
fffff880`02bfc428 fffff800`02c52fac : 00000000`00000018 00000000`00000000 fffffa80`05f52900 00000000`00000002 : nt!KeBugCheckEx
fffff880`02bfc430 fffff800`02fb7f09 : fffff880`02bfcca0 fffff880`02bfc7d8 00000000`00000017 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x46451
fffff880`02bfc490 fffff800`02fb87d6 : 00000000`00000001 00001f80`00000000 fffff8a0`00000001 00000000`00000001 : nt!ObpWaitForMultipleObjects+0x2d3
fffff880`02bfc960 fffff800`02cba853 : fffffa80`05f45060 00000000`004efb38 fffff880`02bfcbc8 fffff880`02bfcc00 : nt!NtWaitForMultipleObjects+0xe5
fffff880`02bfcbb0 00000000`7747046a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`004efb18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7747046a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46451
fffff800`02c52fac cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46451

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46451

BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+46451

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

This dump doesn't tell us much except that it points to hardware or drivers.

To answer your question, yes, it could be the motherboard; but I would have expected some different error codes if it were the motherboard. I am still leaning toward the video card based on what I have seen.

joker007 · Jul 3, 2010

Thanks Carl. I think I'll see if I can swap graphics cards with a mate and see what happens. PC does seem to be much more stable with catalyst 10.6s' but i want it 100% stable. MSI have asked me to try another card before they send me a new bios. I will let you know what happens.

CarlTR6 · Jul 3, 2010

Thanks for the update. Let us know how another video card does.

joker007 · Jul 4, 2010

I've put in an old 1900xt for the time being so will see how that goes. Could the sort of artifacting I've been getting be caused by a faulty power supply? Just want to rule everything else out before I go down the RMA route. I bought the PSU at the same time as the card. It's an Antec Truepower New 650 watt. Would be strange as the PC runs 3d perfectly fine though.

Jonathan_King · Jul 4, 2010

Antec is a reputable brand, but every product has a certain risk of failure.

If the PSU is faulty, it can result in random errors difficult to diagnose. BSODs are a possibility.

If you have another PSU to test, for it.

joker007 · Jul 4, 2010

Well it doesn't look like its the graphics card. I haven't had the artifacts again but computer has been locking up in windows and even in bios. I won't be able to test power supply until I bring my volt meter back from work Tuesday. Is there any software which can monitor voltages accurately? The CPU is fairly new so I don't think it could be that. I have run memtest overnight and it found no problems but I am running with just one stick of RAM to see what happens. which component do you think is the chief suspect?

CarlTR6 · Jul 4, 2010

Do you have any new dmp files? I have to suspect hardware since you are having problems in BIOS.

joker007 · Jul 5, 2010

Hi Carl. Unfortunately the crash didn't create a dmp file. Since I have only been running with one stick of RAM so far the system has been stable. I ran memtest overnight and no errors were found. I will run it with the other stick tonight. Could the system be struggling to run 800mhz dual channel mode with ATI cards? If so could it cause crashes like I have been experiencing? It ran 800mhz fine with nvidia. Would it be worth running 667mhz and see if its stable? I noticed in BIOS that my motherboard won't allow me to enter the correct timings either. My memory is CM2X2048-6400C5DHX which should run at 5-5-5-18. I can only set 5-5-5-15. Was never a problem previously but I am wondering whether The ATI cards are fussier. I can rule out the power supply tomorrow when I can pick my volt meter up. Could intel speedstep cause issues like this? Sort of plucking at straws now!

CarlTR6 · Jul 5, 2010

I would say that since you are stable with one stick, the indication is definitely a RAM problem. We will know more when you test the other stick.

When you start asking about the capabilities of your board and its effect, you are out of my area of limited expertise. I am not a hardware guy. If your system is struggling to run your RAM, yes it can definitely trigger crashes. I have never delved into RAM voltages, overclocking, under clock, etc. But there are some good hardware folks here. I will post a call for help with your questions. Stay tuned.

theog · Jul 5, 2010

1) Check your PSU.

2) Clear your BIOS. Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS

Help Please

Antique Senior Member

My Computer

New member

My Computer

Computer Voodooist

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Computer Voodooist

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer