BSOD (My hardware config or somthing else?)

The Jaded Raver · 31 Jul 2009 at 10:34

Hello.

I have bee getting the old BSOD quite consistently ata, purely at random. So im guessing my pc is not too stable. However, non of my components are over clocked and are running at factory defaults.

I reformatted my computer and installed Both SP1and 2 for vista 64, with chipset, directx and graphics driver updates ect (In the recommended order).

I am starting now to think it may be my hardware configuration.

# Windows Vista Home Premium (x64) Service Pack 2 (build 6002)

# 3.00 gigahertz AMD Athlon 64 X2 Dual Core
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
64-bit ready

# Gigabyte M57SLI-S4 (nForce 570 SLI)
Bus Clock: 200 megahertz
BIOS: Award Software International, Inc. FHh 05/25/2009

# ATI Sapphire 4870, 512mb, core 750Mhz, memory 900Mhz (this bought to replace nVidia 8800 gtx, and may be the issue)

# Ram - 4096 Mb (4 x 1024 DDR2-SDRAM)

# Drives - Western Digital (CFQPQ GHI7WD63WDU SCSI CdRom Device) [CD-ROM drive]
Sony Writemaster - TSSTcorp CD/DVDW SH-S183A SCSI CdRom Device [CD-ROM drive]

I dont think cooling is the issue either. As mine is quite good i think (CPU core 1 = 42, C core 2 = 46, GPU = 50)

Also here is the windows system error report -

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904AA
BCP2: FFFFFA600921A6F8
BCP3: FFFFFA600921A0D0
BCP4: FFFFF80001EC9C6A
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini073109-01.dmp
C:\Users\Scottie\AppData\Local\Temp\WER-156422-0.sysdata.xml
C:\Users\Scottie\AppData\Local\Temp\WER905C.tmp.version.txt

Thats probably enough information before i overload u all.

I just want to get this sorted.

Cheers and feel free to ask for more detailed info

The Jaded Raver · 31 Jul 2009 at 12:11

m4cc45 · 31 Jul 2009 at 12:24

Might be worth running the Memory Diagnostic Tool (or another memory tool) to see if it is that. Most bluescreens are caused by fault memory.

It's a good point to start.

M.

theheyes · 31 Jul 2009 at 15:49

Run chkdsk also.

The Jaded Raver · 5 Aug 2009 at 10:17

m4cc45 said:
Might be worth running the Memory Diagnostic Tool (or another memory tool) to see if it is that. Most bluescreens are caused by fault memory.

It's a good point to start.

M.

Hello M. Cheers for advice, but nothing appeared to be wrong. And i still get the problem. Humm

The Jaded Raver · 5 Aug 2009 at 10:24

theheyes said:
Run chkdsk also.

Yeh i googled that command and all it said it fixed / repaired some files (cant remamber precise phrase).

THough after that, my Belkin USB N wirless stopped working. U think those drivers might be the cause of BSOD if that is teh case?

Only i have had bsod in the past year on and off, though it seems to be more frequent now. Im starting to think its my hardware config, since i only seemed to have this issur whe i changed my GPU from a 8800 GTX to a Radeon 4870.

Thanks for the help tho. I will remember that one.

m4cc45 · 5 Aug 2009 at 10:43

Well if you've added new hardware and it's started blue screening that's a good place to start. The best way to deal with it is remove the hardware and try and replicate the blue screen. So remove USB stick, try again, remove sound card, try again, etc.

M.

m4cc45 · 5 Aug 2009 at 10:44

P.S. Assume you are running the latest drivers for everything?

The Jaded Raver · 5 Aug 2009 at 11:05

m4cc45 said:
P.S. Assume you are running the latest drivers for everything?

Yes i am, just checked "touch wood". KK, will try that one. Cheers again

Pho · 5 Aug 2009 at 13:33

Email me (or post up) C:\Windows\Minidump\Mini073109-01.dmp and I'll take a look.

The Jaded Raver · 5 Oct 2009 at 17:00

Pho said:
Email me (or post up) C:\Windows\Minidump\Mini073109-01.dmp and I'll take a look.

So your saying, there could be something wrong with that file??? What sort of file is it? Before i send it.

Dewotter · 5 Oct 2009 at 17:13

The Jaded Raver said:
So your saying, there could be something wrong with that file??? What sort of file is it? Before i send it.

Its a dump file that Windows creates when it encounters a serious error. For those few that can decrypt whats in it they can help figure out what is causing the random crashes.

Pho · 5 Oct 2009 at 18:53

2 month bump? It can't be that serious

.

As above

. It's perfectly safe to send or post, it just lets us know what caused the crash. You might want to post a more up-to-date one if you're still having problems though.

The Jaded Raver · 6 Oct 2009 at 12:39

Pho said:
2 month bump? It can't be that serious .

As above . It's perfectly safe to send or post, it just lets us know what caused the crash. You might want to post a more up-to-date one if you're still having problems though.

Yeh soz man. I actually forgot about this post. I have been doing other test besides all the ones previously mentioned. Such as Memtest +, prime95, core temps. All these passed with flying colours. Though ill run prime 95 again just to make sure.
Though I seriously thinks it is my motherboard (Gigabyte M57SLI-S4 nForce 570 SLI) hating my graphics card (Sapphire Radeon 4870 512gb, 1st model)

Ill send you that file (Mini100609-01.dmp)

Thanks again

Pho · 6 Oct 2009 at 14:09

Ok, here's your dump in English

p):

PHP:

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


Loading Dump File [C:\Users\Andrew\Desktop\Mini100609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\temp\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`01e4f000 PsLoadedModuleList = 0xfffff800`02013dd0
Debug session time: Tue Oct  6 12:03:05.307 2009 (GMT+1)
System Uptime: 0 days 1:49:51.195
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {fffffa80039aa5b0, fffffa8005ba3040, 1, fffffa80042156a0}

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

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

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

REFERENCE_BY_POINTER (18)
Arguments:
Arg1: fffffa80039aa5b0, Object type of the object whose reference count is being lowered
Arg2: fffffa8005ba3040, Object whose reference count is being lowered
Arg3: 0000000000000001, Reserved
Arg4: fffffa80042156a0, 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:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001eec358 to fffff80001ea9450

STACK_TEXT:  
fffffa60`074afa98 fffff800`01eec358 : 00000000`00000018 fffffa80`039aa5b0 fffffa80`05ba3040 00000000`00000001 : nt!KeBugCheckEx
fffffa60`074afaa0 fffff800`0211305e : fffff880`09df8800 fffffa80`00000000 fffff880`09df8800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2a2b8
fffffa60`074afb30 fffff800`02113314 : fffff880`09df5880 fffff880`09df5800 00000000`00000001 00000000`00000201 : nt!ObpCloseHandleTableEntry+0xce
fffffa60`074afbd0 fffff800`01ea8ef3 : fffffa80`05f3f7c0 fffffa60`074afca0 00000000`002f0003 fffffa80`0536bb10 : nt!ObpCloseHandle+0x94
fffffa60`074afc20 00000000`776d6e0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`011df9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776d6e0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2a2b8
fffff800`01eec358 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2a2b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  49e0237f

FAILURE_BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+2a2b8

BUCKET_ID:  X64_0x18_nt!_??_::FNODOBFM::_string_+2a2b8

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

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x18
PROCESS_NAME: audiodg.exe - audio!

Try updating to the latest Realtek audio drivers (I assume that board uses them) from http://www.realtek.com.tw/DOWNLOADS...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false - I had lots of BSODs with out-of-date ones.

The Jaded Raver · 6 Oct 2009 at 16:48

Pho said:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x18
PROCESS_NAME: audiodg.exe - audio!

Try updating to the latest Realtek audio drivers (I assume that board uses them) from http://www.realtek.com.tw/DOWNLOADS...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false - I had lots of BSODs with out-of-date ones.

I do also have a Steel series USB 7.1 audio dongle in use. Perhaps is that the cause? Or do u think its specifically Realtek?

Pho · 6 Oct 2009 at 17:44

Maybe - try unplugging it and see what happens. I just had dodgy experiences with old Realtek vista sound/network drivers.

Or, if you don't use it disable the onboard audio in your BIOS.

The Jaded Raver · 6 Oct 2009 at 21:58

K, cheers man for all your help

The Realtek driver update has seemed to of fixed the problem (Touch wood). Though with bsod errors, only time will tell.

Hopefully i wont have to post again

Pho · 6 Oct 2009 at 22:11

nice.

The Jaded Raver · 9 Oct 2009 at 16:12

The Jaded Raver said:
K, cheers man for all your help

The Realtek driver update has seemed to of fixed the problem (Touch wood). Though with bsod errors, only time will tell.

Hopefully i wont have to post again

Yeh, it happened again. Though I was doing well for a bit

If its not too much trouble, ill send you this new minidump file (Mini100909-01.dmp) and is the results show its to do with the audio again, ill know its my usb sound dongle.

Whole error

System Service exemption

0x0000003b, (00000000C0000005, FFFFF80001E8E606, FFFFFA6009E63100, 0000000000000000).

This would be very much appreciated indeed!!!