BSOD nightmares!

[nlan]

Hi!

Last month I bought some hardware from Aria for a decent upgrade:

ASUS M2N-E
AMD Athlon 64 X2 4200
nVidia GeForce 7600GT 256MB PCI-E
Arianet High Perf. 1GB DDR2 667

Other hardware:

Using a RAID 1 array of two WD2500 HDDs.
Sound Blaster Live
1 x RICOH CDRW

I have been getting random system freezes & BSODs, blaming various system/device drivers, especially when playing music or watching videos!
Typically, if a sound was playing, it gets stuck in a quick loop on the speakers on freeze..

- Re-installed XP32 a few times: no luck.
- Upgraded to latest BIOS: no luck.

I even spent £65 for a new Hipro 650W PSU (thinking my Enermax 465W was not adequate!), still no luck!

I'm thinking of RMAing, but where should I start? Motherboard? CPU? Graphics Card?

Thanks
Nikos

[Firerat]

Hi Nikos

Welcome to the Lair

My first guess would be your Memory

You can test this with memtest+
http://www.memtest.org/

[nlan]

Hi

Thank you for your reply.

I have already tried memtest, let it run for around 30', and it found no problems.

I've also used microsoft's memory test. I noticed that it froze in a couple of occassions.

However, I suspect that it might not be a memory problem. Freezing during the memory test is an indication of this. Normally, the memory test should display an error instead.

Of course I've also tried moving the memory stick to other slots & re-inserting, as I did with my PCI/PCIe expansion cards. Nothing changed!

I am convinced that this is a Motherboard/CPU issue..

[Firerat]

What temps are your GPU running at ?

This thread, on an external Forum, details the same problem as yours
http://forums.filefront.com/showthread.php?t=247041

The Solution was a Zalman VF700-ALCU and Arctic Silver V

The Temp Monitor mentioned can be found here
http://www.guru3d.com/index.php?page=rivatuner

[nlan]

Hi

GPU is running at 52 degrees, which doesn't sound too high.

Further, I don't overclock my PC or play any 3D games like the people in the referred discussion did..
Regards
Nikos

[Firerat]

Ok NP


have you tried removing the soundblaster?

[nlan]

hi

Tried that but no change.
Wouldn't make any sense anyway, as I have been using the sblive with no problems until the upgrade..

[Firerat]

[quote:df2597f9d8=\"nlan\"]hi

Tried that but no change.
Wouldn't make any sense anyway, as I have been using the sblive with no problems until the upgrade..[/quote:df2597f9d8]

I hear ( read?) you,

But Previously working cards can fail after transposing due to ESD
I know a lot of people say
\"Well I have never had a problem, blah blah blah\"
But its a possibility, anyway it is eliminated now

Any USB devices attached?,
USB Modems are often overlooked

Failing that I'm out of Ideas, it would have to be a case of swapping bits out and seeing what solves the problem.

How instable is it?
can you get it to fall over quite quickly or is it one of these nightmare intermitent things?

[nlan]

Unfortunately it's an intermittent thing..

However there is a way to trigger a blue screen, and that is by connecting my USB Satellite Receiver, a Twinhan Starbox. Soon after I've watched some TV, it will cause a failure.
Again, the box was tested with my friend's laptop and is perfectly fine..

Unfortunately I don't know anyone around here, with whom I could swap parts.

I think I will have to RMA.

One question, if I RMA my motherboard/cpu, can I get different models?
e.g other motherboard brand or cpu brand?

Seems there are a few people on the net, suffering with M2N-E's..

[Firerat]

Once bitten, twice shy :wink:

I'm not supprised that other people on the net are having problems,
its just unfortunate that some items are.... well... just faulty.

Fact is the net is a bit like the news on the telly or in the papers, its full of doom and gloom.

No one says

Hey guys, my Mod-XYZ motherboard is NOT FAULTY !!, is anybody else not having problems with their Mod-XYZ?



Aria is a business, if we see disproportionate failure rates on a line it will be 'killed', this seldom happens though.

[Anonymous]

[Removed at the request of the author]

[nlan]

I don't disagree at all.. And in fact I do question such \"rumors\" and try to troubleshoot as much as I can.

But I think that after one month of dysfunctionality, it's time to swallow my pride as an electronic engineer, and say \"I give up\"!

Could you please PM suggesting the best RMA route?

Ideally I'd like to send my whole order back (cpu/mobo/memory/graphics card) so Aria could see what's faulty and what's not..

[nlan]

[quote:48644b53c7=\"PrivatePyle\"]Hi Nikos..

before you start arbitrarily RMA'ing parts of your system until you find the faulty/offending component, can you post any details of the BSOD error? You need to set your machine to not immediately restart if it falls over.[/quote:48644b53c7]
Using windbg.exe & windows in debug mode (& after my system got a BSOD instead of just freezing), here is what happened when i attempted to use the usb satellite receiver. OK, could be a driver fault, but other random errors are pasted further below..

[color=darkred:48644b53c7]Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\\WINDOWS\\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x80800000 PsLoadedModuleList = 0x80885700
Debug session time: Sat Dec 2 16:53:37.515 2006 (GMT+0)
System Uptime: 0 days 0:17:13.230
Loading Kernel Symbols
.................................................. .................................................. .................................
Loading User Symbols
Loading unloaded module list
..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, edfb43c2, f7997c9c, f7997998}
*** ERROR: Module load completed but symbols could not be loaded for UDSTDrv.sys
Probably caused by : UDSTDrv.sys ( UDSTDrv+13c2 )
Followup: MachineOwner
---------
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: edfb43c2, The address that the exception occurred at
Arg3: f7997c9c, Exception Record Address
Arg4: f7997998, Context Record Address

Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at \"0x%08lx\" referenced memory at \"0x%08lx\". The memory could not be \"%s\".
FAULTING_IP:
UDSTDrv+13c2
edfb43c2 894804 mov dword ptr [eax+4],ecx
EXCEPTION_RECORD: f7997c9c -- (.exr fffffffff7997c9c)
ExceptionAddress: edfb43c2 (UDSTDrv+0x000013c2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000004
Attempt to write to address 00000004
CONTEXT: f7997998 -- (.cxr fffffffff7997998)
eax=00000000 ebx=86dc2020 ecx=84d83cac edx=00000000 esi=85cf7ef8 edi=84d83810
eip=edfb43c2 esp=f7997d64 ebp=f7997d7c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
UDSTDrv+0x13c2:
edfb43c2 894804 mov dword ptr [eax+4],ecx ds:0023:00000004=????????
Resetting default scope
PROCESS_NAME: S

[nlan]

PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at \"0x%08lx\" referenced memory at \"0x%08lx\". The memory could not be \"%s\".
WRITE_ADDRESS: 00000004
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 80860757 to edfb43c2
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7997d7c 80860757 84e3cac0 00000000 86dc2020 UDSTDrv+0x13c2
f7997dac 808f7794 84e3cac0 00000000 00000000 nt!ExpWorkerThread+0xef
f7997ddc 8086e0ce 80860668 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
UDSTDrv+13c2
edfb43c2 894804 mov dword ptr [eax+4],ecx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: UDSTDrv
IMAGE_NAME: UDSTDrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 438e7cfa
SYMBOL_NAME: UDSTDrv+13c2
STACK_COMMAND: .cxr 0xfffffffff7997998 ; kb
FAILURE_BUCKET_ID: 0x7E_UDSTDrv+13c2
BUCKET_ID: 0x7E_UDSTDrv+13c2
Followup: MachineOwner
---------
And here is one of the random/intermittent errors. This occured while Norton Antivirus was scanning my hdd, and it's blaming NTFS.SYS! :
[color=darkred:7c79e6a837]
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\\WINDOWS\\Minidump\\Mini120106-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x80800000 PsLoadedModuleList = 0x80885700
Debug session time: Fri Dec 1 20:36:27.187 2006 (GMT+0)
System Uptime: 0 days 0:14:02.875
Loading Kernel Symbols
.................................................. .................................................. ............................
Loading User Symbols
Loading unloaded module list
................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1902fe, ba0788b4, ba0785b0, f7399124}
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
Probably caused by : Ntfs.sys ( Ntfs!NtfsCheckpointCurrentTransaction+35 )
Followup: MachineOwner
---------
1: 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: 001902fe
Arg2: ba0788b4
Arg3: ba0785b0
Arg4: f7399124

Debugging Details:
------------------
EXCEPTION_RECORD: ba0788b4 -- (.exr ffffffffba0788b4)
ExceptionAddress: f7399124 (Ntfs!NtfsCheckpointCurrentTransaction+0x00000035)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000678
Attempt to read from addr

[nlan]

ress 00000678
CONTEXT: ba0785b0 -- (.cxr ffffffffba0785b0)
eax=00000000 ebx=ba078980 ecx=00000000 edx=00000000 esi=86166270 edi=00000008
eip=f7399124 esp=ba07897c ebp=ba078984 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
Ntfs!NtfsCheckpointCurrentTransaction+0x35:
f7399124 398770060000 cmp dword ptr [edi+670h],eax ds:0023:00000678=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at \"0x%08lx\" referenced memory at \"0x%08lx\". The memory could not be \"%s\".
READ_ADDRESS: 00000678
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from f7372e11 to f7399124
STACK_TEXT:
ba078984 f7372e11 86166270 c00000d8 ba078b84 Ntfs!NtfsCheckpointCurrentTransaction+0x35
ba078b68 f7370c97 86166270 86077b28 86077b28 Ntfs!NtfsCommonWrite+0x1364
ba078bcc 80817eb1 86d63770 86077b28 86d5ff38 Ntfs!NtfsFsdWrite+0xf3
ba078bdc f74133ca 80818d76 00000000 ba078c94 nt!IopfCallDriver+0x31
ba078bec 80817eb1 86cfb770 e52f73e0 ba078c44 sr!SrWrite+0xaa
ba078bfc f493c0b4 00000000 ba078c44 86970780 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ba078c94 808a5243 864bf740 86077b28 86083f28 SYMEVENT+0xb0b4
ba078d38 8086960c 000002e4 00000000 00000000 nt!NtWriteFile+0x5d7
ba078d38 7c90eb94 000002e4 00000000 00000000 nt!KiFastCallEntry+0xfc
034edf08 00000000 00000000 00000000 00000000 0x7c90eb94
FOLLOWUP_IP:
Ntfs!NtfsCheckpointCurrentTransaction+35
f7399124 398770060000 cmp dword ptr [edi+670h],eax
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107eea
SYMBOL_NAME: Ntfs!NtfsCheckpointCurrentTransaction+35
STACK_COMMAND: .cxr 0xffffffffba0785b0 ; kb
FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsCheckpointCurrentTransaction+35
BUCKET_ID: 0x24_Ntfs!NtfsCheckpointCurrentTransaction+35
Followup: MachineOwner
---------