Frequent BSOD's.. at wits end :( part 1

mrflib

Ladies and Gents,

Thank you for taking the time to read this post/tale of woe. I recently built and assembled a brand new PC, everything brand new. Since day one have had sporadic BSOD's and it's driving me round the bend. I convinced myself it was the GFX card so purchased a new one to test... BSOD's continued. I RMA'd the motherboard/ram/cpu - all passed tests and were returned.

So I formatted for the thrid time and reinstalled Windows 7, immediately getting 2 BSOD's while trying to install and one on first boot (after 15 seconds of being in Windows).

I use a SSD from OCZ (Vertex 2E) and have run Chkdsk numerous times and found no errors. So I attach the required information for just the latest errors since reinstall.

Is Windows 7 . . .
- x64 Home Premium
- the original installed OS on the system? - YES
- an OEM or full retail version? - RETAIL

- What is the age of system (hardware)? - BRAND NEW
- What is the age of OS installation (have you re-installed the OS?) - YES

Any help you can give me would be appreciated. I paid a professional to look at it, and he's stumped.

All the best, and thank you.

mrflib

Hi again,

I dont know if this will help but here's a list of BSOD's. Just had another one. They all seem to be different errors... :/

Attached text file from Blue Screen View.

reventon

Hi,

Code:

STACK_TEXT:   Ntfs!NtfsLookupAllocation+0x295 Ntfs!NtfsPrepareSimpleBuffers+0x146 Ntfs!NtfsPrepareBuffers+0xcb Ntfs!NtfsNonCachedIo+0x1bc Ntfs!NtfsCommonRead+0x7a6 Ntfs!NtfsFsdRead+0x1b8 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fltmgr!FltpDispatch+0xcf nt!IoPageRead+0x252 nt!MiIssueHardFault+0x255 nt!MmAccessFault+0x14bb nt!KiPageFault+0x16e 0x7fe`fea3117a 

BSODs mention HDD drivers (Ntfs as seen in the stack above) - and one of the few remaining pieces of original hardware is that SSD.

I would get it RMAd. The other possibility could be that your motherboard storage controller is faulty, but given you have already replaced it I do not think it is likely.

Regards,
Reventon

BUGCHECK SUMMARY

Code:

 Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Sep 24 08:30:17.144 2010 (GMT+12) System Uptime: 0 days 0:00:16.252 Probably caused by : memory_corruption DEFAULT_BUCKET_ID:  CODE_CORRUPTION PROCESS_NAME:  MsMpEng.exe BUGCHECK_STR:  0x24 Bugcheck code 00000024 Arguments 00000000`001904fb fffff880`09001e58 fffff880`090016c0 fffff880`0122b575 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Thu Sep 23 06:11:06.336 2010 (GMT+12) System Uptime: 0 days 0:00:12.334 Probably caused by : memory_corruption DEFAULT_BUCKET_ID:  CODE_CORRUPTION BUGCHECK_STR:  0x50 PROCESS_NAME:  svchost.exe Bugcheck code 00000050 Arguments fffffa7f`9091c5b4 00000000`00000001 fffff880`012d8d6f 00000000`00000007 ��������������������������������������������������������������������������������������`` Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Sep 22 07:00:35.089 2010 (GMT+12) System Uptime: 0 days 0:01:13.198 Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 ) DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT BUGCHECK_STR:  0x1E PROCESS_NAME:  explorer.exe Bugcheck code 0000001E Arguments ffffffff`c0000005 fffffa80`06cba880 00000000`00000001 00000000`4005ba35 ��������������������������������������������������������������������������������������``

mrflib

Thank you for your reponse, Reventon.

I have a spare HDD here - I will install Windows on to that and see if the issues go away. If so, I will be dead chuffed.

If there's anything else I can do, please let me know.

All the best

Pete

mrflib

Alas, failure.

I have disconnected the SSD and installed on a new HDD. Random crashes continue. New BSOD.text attached.

Any help sincerely appreciated

Pete

Edit: also added dumps.

I remember in a conversation long ago with a tech support guy something about my RAM voltages not being high enough. I upped the voltage to 1.65v, but still had another BSOD.

RAM: Corsair XMS3 6GB (3x2GB) DDR3 PC3-12800C9 1600MHz Triple Channel Kit

mrflib

Apologies for double post, couldn't attach dumps in edit. I thought it would also be prudent to post updated reports for you, as I'm now effectively on a fresh install and a new HDD.

reventon

Ok.

This time around - both Memory errors.

Only possible software cause I can see is the following

Code:

ASACPI.sys   Mon Mar 28 15:30:36 2005 (42476C4C)

ASACPI.sys - ASUS ACPI Driver; near guaranteed to cause BSODs on Windows 7 systems. Update link here, update instructions (slideshow) here (note that in the last step you select the ATK0110 driver in the list instead of the one mentioned)

There however remains the possibility that despite the RMAs one of your components is faulty.

Run these tests:

http://www.sevenforums.com/tutorials...t-prime95.html (run the Blend test as well as the Small FFT test)

RAM - Test with Memtest86+

BUGCHECK SUMMARY

Code:

 Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Sep 24 11:12:15.798 2010 (GMT+12) System Uptime: 0 days 0:02:21.906 Probably caused by : memory_corruption DEFAULT_BUCKET_ID:  CODE_CORRUPTION BUGCHECK_STR:  0xA PROCESS_NAME:  chrome.exe Bugcheck code 0000000A Arguments fffff6ff`e318ccf0 00000000`00000002 00000000`00000001 fffff800`0288a464 ��������������������������������������������������������������������������������������`` Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Sep 24 11:09:09.577 2010 (GMT+12) System Uptime: 0 days 0:07:09.685 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42c75 ) BUGCHECK_STR:  0x1a_41287 MEMORY_MANAGEMENT DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT PROCESS_NAME:  chrome.exe Bugcheck code 0000001A Arguments 00000000`00041287 00000000`48d38b4c 00000000`00000000 00000000`00000000 ��������������������������������������������������������������������������������������``

mrflib

Thank you, Reventon.

I have downloaded the driver, but when I click the install .exe, a command prompt flashes up for a split second and then disappears. Is this normal?

I have also been getting a lot more BSOD's since a Windows Update.

I will try prime and memtest, although I did memtest previously for a day with no errors and the RMA said they ran prime on my cpu/ram/motherboard for 48 hours with no errors.

reventon

�� Quote: Originally Posted by mrflib

I have downloaded the driver, but when I click the install .exe, a command prompt flashes up for a split second and then disappears. Is this normal?

Yes. It is normal.

Can you please upload the latest Minidumps from C:\Windows\Minidump (you will have to copy them to the desktop before zipping them up).

mrflib

Here you go. Driver now updated (I did it through the device manager > system) and have run a full chkdsk with no errors. Will now do Prime and Memtest.

Many thanks.

CarlTR6

I looked at all six of your dumps. Five of them blamed memory corruption or memory management and one simply blamed hardware. One of the dumps was a Driver Verifier enabled dump. It was the one that blamed hardware.

Stop error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usually caused by Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Stop error code 24, NTFS_FILE_SYSTEM -usually causes are Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure.

Stop error code 1A, MEMORY_MANAGEMENT - usually caused by Device driver, memory, kernel.

Stop error code C4, DRIVER_VERIFIER_DETECTED_VIOLATION - usually caused by a device driver.

Stop error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

I still see this driver in your latest dumps:
ASACPI.sys Sun Mar 27 22:30:36 2005 - Please install the latest ATK0110 Utility for Vista/7 from this link: ASUSTeK Computer Inc.-Support-.

I also find this outdated driver: anodlwfx.sys Fri Mar 06 05:10:08 2009 - Alpha filter driver, Alpha Networks, Inc, Alpha Networks Inc.. I am guessing this is a wireless or Ethernet adapter driver. Try to update it via your wireless or Ethernet adapter manufactures website.

mrflib

Hi Carl thanks for your time.

I have since updated that driver and, touch wood, I've had no BSOD's yet. However I have no idea what that Alpha Networks driver is - I use a D-Link adapter, nothing to do with Alpha.

I'm now however getting a couple of "black screen" errors when using 3D graphics, which reboots itself.

CarlTR6

That is good news - except for the black screens.

Alpha networks is a spin off from D-Link. See if you can update your adapter drivers from D-Link. It might have some bearing on your black screens.

I suspect that ASACPI.sys was the main cause of your BSOD's. The 2005 version is almost guaranteed to cause crashes.

mrflib

Ah ok - well I did infact download drivers direct from D-Link, not using the CD that came with the product. I will poke around to see if I can find any 64bit DWA-140 drivers newer than ones I have.

Where does this infamous 2005 driver come from? It's a new build system so I can't understand it.

CarlTR6

That infamous driver belongs to Asus ATK0110 ACPI Utility and is also a part of the Asus PCProbe and AISuite Utilities. You would not believe how many times we have encountered that monster.

The Alpha driver may work; but if you can update it, it would be a lot better.

mrflib

Guys, thanks to you my BSOD's seem to had gone! So thumbs up for your assistance.

I am occassionally getting black screens now, requiring a hard reboot. This can be in or out of a 3D application. WOuld you have any idea on that? Sorry to push my luck - I know it's the wrong colour screen!

Edit: Just had a blue screen after installing a few drivers.... have rolled back just in case and will not touch anything for a few days! Had a PAGE_FAULT error.

reventon

Have you run the hardware tests I mentioned in Post #7 yet?

mrflib

Hi Reventon,

I haven't had a chance to run Prime/Memtest since reinstall - unfortunately a lot of work has come up and I've needed the PC for other things. However, I did run IntelBurnTest - which failed. I was advised this tested CPU and RAM?



If you think I should still run the tests I can do memtest this evening and run prime overnight?

CarlTR6

Memtest will take about seven hours. You should run it over night. I am not familiar with the test you ran; but that indicates further testing and that you may well have a problem with the CPU. I just do not know how much trust to put in that test. I do not remember how long I ran Prime (old timers disease).

mrflib

Unfortunately just had another BSOD. Dump attached. I will run memtest now for 8 hours, then get prime going. I suspect prime won't finish as I'll get a BSOD during.

CarlTR6

Sorry to see another crash.

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usually caused by Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

This dump blames memory corruption and code corruption.

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_092610-20108-01.zip\092610-20108-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available  Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is:  Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50 Debug session time: Sun Sep 26 11:05:22.177 2010 (GMT-4) System Uptime: 0 days 0:02:28.286 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 50, {fffff87fd0d77c1c, 0, fffff80002f63e87, 5}   Could not read faulting driver name Probably caused by : memory_corruption  Followup: memory_corruption ---------  6: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced.  This cannot be protected by try-except, it must be protected by a Probe.  Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffff87fd0d77c1c, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80002f63e87, If non-zero, the instruction address which referenced the bad memory     address. Arg4: 0000000000000005, (reserved)  Debugging Details: ------------------   Could not read faulting driver name  READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec10e0  fffff87fd0d77c1c   FAULTING_IP:  nt!CmpParseKey+11c7 fffff800`02f63e87 0b8d0c4948c7    or      ecx,dword ptr [rbp-38B7B6F4h]  MM_INTERNAL_CODE:  5  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  CODE_CORRUPTION  BUGCHECK_STR:  0x50  PROCESS_NAME:  mscorsvw.exe  CURRENT_IRQL:  0  TRAP_FRAME:  fffff880098f2c80 -- (.trap 0xfffff880098f2c80) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8a000058000 rbx=0000000000000000 rcx=00000000b2d05e15 rdx=00000000000000f1 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002f63e87 rsp=fffff880098f2e10 rbp=fffff880098f3310  r8=0000000024c898f1  r9=0000000000000087 r10=0000000000000006 r11=fffff8a00370fc00 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei pl nz ac po cy nt!CmpParseKey+0x11c7: fffff800`02f63e87 0b8d0c4948c7    or      ecx,dword ptr [rbp-38B7B6F4h] ss:0018:fffff87f`d0d77c1c=???????? Resetting default scope  LAST_CONTROL_TRANSFER:  from fffff80002d088c1 to fffff80002c89740  STACK_TEXT:   fffff880`098f2b18 fffff800`02d088c1 : 00000000`00000050 fffff87f`d0d77c1c 00000000`00000000 fffff880`098f2c80 : nt!KeBugCheckEx fffff880`098f2b20 fffff800`02c8782e : 00000000`00000000 fffff8a0`015d690c 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b fffff880`098f2c80 fffff800`02f63e87 : fffff8a0`015d690c fffff880`098f3310 fffff8a0`00024010 fffff8a0`00022948 : nt!KiPageFault+0x16e fffff880`098f2e10 fffff800`02f82e84 : fffff800`02f62cc0 00000000`00000000 fffffa80`073aa010 fffff800`02f67b01 : nt!CmpParseKey+0x11c7 fffff880`098f30e0 fffff800`02f87e4d : fffffa80`073aa010 fffff880`098f3240 fffff8a0`00000040 fffffa80`05526510 : nt!ObpLookupObjectName+0x585 fffff880`098f31e0 fffff800`02f66dcc : fffff8a0`0377d000 00000000`00000000 fffff8a0`0373b701 00000000`000cd800 : nt!ObOpenObjectByName+0x1cd fffff880`098f3290 fffff800`02f68f0f : 00000000`000cce78 00000000`00020019 00000000`000cce98 00000000`00000000 : nt!CmOpenKey+0x28a fffff880`098f33e0 fffff800`02c88993 : fffffa80`07b32060 fffff880`098f34a0 00000000`fffdb000 fffff880`00000004 : nt!NtOpenKeyEx+0xf fffff880`098f3420 00000000`77020caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000cce38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77020caa   STACK_COMMAND:  kb  CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt     fffff80002f63e87 - nt!CmpParseKey+11c7     [ 4b:0b ] 1 error : !nt (fffff80002f63e87)  MODULE_NAME: memory_corruption  IMAGE_NAME:  memory_corruption  FOLLOWUP_NAME:  memory_corruption  DEBUG_FLR_IMAGE_TIMESTAMP:  0  MEMORY_CORRUPTOR:  ONE_BIT  FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT  BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT  Followup: memory_corruption ---------

I find this out of date driver on your system and it may be contributing to your system instability:

anodlwfx.sys Fri Mar 06 05:10:08 2009 - ANOD Network Security Filter driver, Alpha filter driver, Alpha Networks, Inc. Alpha is a spinoff from D Link. See if you can update this driver through D Link. I assume you have a DLink adapter?

mrflib

Thank you again for your assistance.

I did actually try to find an update or driver of any kind on Alpha Network's site, but could only find irrelevent files. I will certainly have a more in depth look.

I'm currently out, and the PC is doing memtest as we speak. I am determined to get this sorted, and to have websites like this where you find people genuinely looking to help is fantastic. I would be delighted to donate some funds towards site maintenance if there is such a facility in place.

CarlTR6

YOu are certainly welcome. Don't forget to try D-Link for that driver. I have not looked for it there myself.

That is very thoughtful and generous of you. I understand that there used to be a provision for donations. But the forum owner decided against that. The site is maintained through advertising revenue. Visitors see the adds; members do not see them. We are all volunteers here who like to help and share with others.

mrflib

Consider some ads clicked!

Memtest is currently on its 5th pass with no errors yet. I'm not quite as confident about Prime, however. We shall see.

CarlTR6

Let us know - and good luck.

mrflib

Hi guys, was just typing a response and had another BSOD. I have attached dump.

I have looked using my limited knowledge for an updated Alpha Networks driver to no avail. If anyone knows a more up to date version, I would be happy to give it a try.

I have run memtest for almost 17 hours, please see result below.

I will now try running Prime, though I'm not particularly sure on how to run it to best effect, so again if anyone has any advice it would be appreciated. I am reading sevenforums tutorial now. Specifically, what am I looking for? What should I paste on here in terms of results? Should I leave it running for 12 hours on blend and 12 hours on FTT?



Many thanks.

CarlTR6

RAM looks good. Just follow the tutorial for running Prime: http://www.sevenforums.com/tutorials...t-prime95.html

Error code 3B, SYSTEM_SERVICE_EXCEPTION - BSOD Index

The dump blames memory corruption and indicates AirNCFG.exe as the cause. Airncfg.exe - D-Link Wireless LAN Monitor is a process file from D-Link belonging to the Wireless LAN Monitor and I think this outdated driver, anodlwfx.sys, is part of it. I can find very little on this driver.

I have a D-Link wireless adapter and I have neither Airncfg.exe nor anodlwfx.sys on my system. I suspect that AIRncfg.exe is a configuration program for your adapter. When I installed the adapter, I did not install the configuration program. I let Windows configure my wireless with its built in program.

How old is your adapter? If it is more than two years old, I recommend that you try a new adapter. You can also try going to the D-Link website and upgrading the drivers and firmware for your D-Link model.

Code:

Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50 Debug session time: Mon Sep 27 10:05:52.362 2010 (GMT-4) System Uptime: 0 days 0:16:56.472 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 3B, {c0000005, fffff80002f57686, fffff8800946baf0, 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: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002f57686, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800946baf0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero.  Debugging Details: ------------------   EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.  FAULTING_IP:  nt!CmpCheckKeyBodyAccess+c6 fffff800`02f57686 66ff88c4010000  dec     word ptr [rax+1C4h]  CONTEXT:  fffff8800946baf0 -- (.cxr 0xfffff8800946baf0) rax=1775c53a4000006a rbx=fffff8a001450614 rcx=fffff8a000024010 rdx=0000000000000000 rsi=fffffa8007a0e320 rdi=fffff8a002f6bfa0 rip=fffff80002f57686 rsp=fffff8800946c4c0 rbp=fffff8a002f6bfa8  r8=fffff8a00002f680  r9=0000000000000001 r10=fffff80002df5720 r11=fffff8800946c530 r12=0000000000000001 r13=0000000000000001 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei ng nz na po nc cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286 nt!CmpCheckKeyBodyAccess+0xc6: fffff800`02f57686 66ff88c4010000  dec     word ptr [rax+1C4h] ds:002b:1775c53a`4000022e=???? Resetting default scope  CUSTOMER_CRASH_COUNT:  1  DEFAULT_BUCKET_ID:  CODE_CORRUPTION  BUGCHECK_STR:  0x3B  PROCESS_NAME:  AirNCFG.exe  CURRENT_IRQL:  0  LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f57686  STACK_TEXT:   fffff880`0946c4c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpCheckKeyBodyAccess+0xc6   CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 3 errors : !nt (fffff80002f571c7-fffff80002f57677) fffff80002f571c0  48  8b  f0  48  8b  84  24 *40  01  00  00  48  39  18  0f  84 H..H..$@...H9... ... fffff80002f57660  00  0f  85  dd  bc  05  00  48  85  db  0f  84  e4  bc  05 *40 .......H.......@ fffff80002f57670  65  48  8b  04  25  88  01 *40  00  48  89  ac  24  a0  00  00 eH..%..@.H..$...  MODULE_NAME: memory_corruption  IMAGE_NAME:  memory_corruption  FOLLOWUP_NAME:  memory_corruption  DEBUG_FLR_IMAGE_TIMESTAMP:  0  MEMORY_CORRUPTOR:  STRIDE  STACK_COMMAND:  .cxr 0xfffff8800946baf0 ; kb  FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE  BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE  Followup: memory_corruption ---------  0: kd> lmtsmn start             end                 module name fffff880`04498000 fffff880`044d6000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00f8c000 fffff880`00fe3000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`03c01000 fffff880`03c8b000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`044f7000 fffff880`0450d000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`010cd000 fffff880`010d8000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`03d15000 fffff880`03d1e000   anodlwfx anodlwfx.sys Fri Mar 06 05:10:08 2009 (49B0F680) fffff880`044d6000 fffff880`044de000   ASACPI   ASACPI.sys   Wed May 13 21:25:17 2009 (4A0B72FD) fffff880`00ff6000 fffff880`00fff000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00db9000 fffff880`00de3000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`05611000 fffff880`05dcc000   atikmdag atikmdag.sys Wed Aug 25 21:47:22 2010 (4C75C7AA) fffff880`01196000 fffff880`011e0000   atikmpag atikmpag.sys Wed Aug 25 21:20:56 2010 (4C75C178) fffff880`02d8f000 fffff880`02d96000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`02c3c000 fffff880`02c4d000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`05571000 fffff880`0558f000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00730000 fffff960`00757000   cdd      cdd.dll      Wed May 19 15:48:26 2010 (4BF4408A) fffff880`02d5c000 fffff880`02d86000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00e19000 fffff880`00ed9000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`0148a000 fffff880`014ba000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00cfe000 fffff880`00d5c000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`014ed000 fffff880`01560000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`044e7000 fffff880`044f7000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`06e8f000 fffff880`06e9d000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03dd3000 fffff880`03df1000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03dc4000 fffff880`03dd3000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01474000 fffff880`0148a000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`038bc000 fffff880`039b6000   Dnetr28ux Dnetr28ux.sys Wed Aug 05 09:59:46 2009 (4A799052) fffff880`05f8a000 fffff880`05fac000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`06e9d000 fffff880`06ea7000   dump_diskdump dump_diskdump.sys Mon Jul 13 20:01:00 2009 (4A5BCABC) fffff880`06f34000 fffff880`06f47000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`06ea7000 fffff880`06f34000   dump_mv91xx dump_mv91xx.sys Wed Mar 17 03:53:06 2010 (4BA08A62) fffff880`02d41000 fffff880`02d49000   dump_mvxxmm dump_mvxxmm.sys Wed Mar 17 03:52:37 2010 (4BA08A45) fffff880`06e83000 fffff880`06e8f000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`03ea1000 fffff880`03f95000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`03f95000 fffff880`03fdb000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`01124000 fffff880`01138000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`010d8000 fffff880`01124000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01571000 fffff880`0157b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`0143a000 fffff880`01474000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`0178d000 fffff880`017d7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`031e5000 fffff800`0322e000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`03fdb000 fffff880`03fff000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`05ef1000 fffff880`05f4d000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`06f8d000 fffff880`06fa6000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06fa6000 fffff880`06fae080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`06f7f000 fffff880`06f8d000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`054a9000 fffff880`05571000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`017f1000 fffff880`017fa000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`02c73000 fffff880`02c89000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`045c2000 fffff880`045d1000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`039de000 fffff880`039ec000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bce000 fffff800`00bd8000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`05e15000 fffff880`05e58000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013c9000 fffff880`013e3000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01762000 fffff880`0178d000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`05fac000 fffff880`05fb1200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`03844000 fffff880`03859000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`03800000 fffff880`03823000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00ca6000 fffff880`00cea000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`039d0000 fffff880`039de000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`045d1000 fffff880`045e0000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`039c3000 fffff880`039d0000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`0558f000 fffff880`055a7000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`055a7000 fffff880`055d4000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`05400000 fffff880`0544e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`0544e000 fffff880`05471000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`02df4000 fffff880`02dff000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fec000 fffff880`00ff6000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01138000 fffff880`01196000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03db9000 fffff880`03dc4000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`017df000 fffff880`017f1000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01009000 fffff880`01096000   mv91xx   mv91xx.sys   Wed Mar 17 03:53:06 2010 (4BA08A62) fffff880`010c5000 fffff880`010cd000   mvxxmm   mvxxmm.sys   Wed Mar 17 03:52:37 2010 (4BA08A45) fffff880`01610000 fffff880`01702000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04531000 fffff880`0453d000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`039ec000 fffff880`039ff000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5) fffff880`0453d000 fffff880`0456c000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`05edc000 fffff880`05ef1000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03d1e000 fffff880`03d2d000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03c8b000 fffff880`03cd0000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01702000 fffff880`01762000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02c00000 fffff880`02c11000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03dad000 fffff880`03db9000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02c09000 fffff800`031e5000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01226000 fffff880`013c9000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02d86000 fffff880`02d8f000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`05e6a000 fffff880`05e82000   nusb3hub nusb3hub.sys Thu Jan 21 22:22:18 2010 (4B5919EA) fffff880`015c7000 fffff880`015f7000   nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010 (4B5919ED) fffff880`03859000 fffff880`038ac000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B) fffff880`03cd9000 fffff880`03cff000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00d8f000 fffff880`00da4000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d5c000 fffff880`00d8f000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00e0d000 fffff880`00e14000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01560000 fffff880`01571000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`02c89000 fffff880`02d2f000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`05f4d000 fffff880`05f8a000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cea000 fffff880`00cfe000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`0450d000 fffff880`04531000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0456c000 fffff880`04587000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`04587000 fffff880`045a8000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`045a8000 fffff880`045c2000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03d5c000 fffff880`03dad000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`02dd9000 fffff880`02de2000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02de2000 fffff880`02deb000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02deb000 fffff880`02df4000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01400000 fffff880`0143a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`06faf000 fffff880`06fc7000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`06c5c000 fffff880`06e82300   RTKVHD64 RTKVHD64.sys Fri Jan 29 01:48:35 2010 (4B6284C3) fffff880`01096000 fffff880`010c5000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`05471000 fffff880`0547c000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E) fffff880`017d7000 fffff880`017df000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB) fffff880`07a00000 fffff880`07a71000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A) fffff880`07b38000 fffff880`07bce000   srv      srv.sys      Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`07ad0000 fffff880`07b38000   srv2     srv2.sys     Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`0547c000 fffff880`054a9000   srvnet   srvnet.sys   Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`045e0000 fffff880`045e1480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`055d4000 fffff880`055e6000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02c2f000 fffff880`02c3c000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02c11000 fffff880`02c2f000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03d48000 fffff880`03d5c000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00400000 fffff960`0040a000   TSDDD    TSDDD.dll    unavailable (00000000) fffff880`02c4d000 fffff880`02c73000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`05e58000 fffff880`05e6a000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`06f64000 fffff880`06f7ec00   usbaudio usbaudio.sys Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`06f47000 fffff880`06f64000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`03df1000 fffff880`03df2f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`03e63000 fffff880`03e74000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`05e82000 fffff880`05edc000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`03e0d000 fffff880`03e63000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`03e00000 fffff880`03e0d000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00e00000 fffff880`00e0d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02d96000 fffff880`02da4000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02da4000 fffff880`02dc9000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00da4000 fffff880`00db9000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`0157b000 fffff880`015c7000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`039b6000 fffff880`039c3000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39) fffff880`03cff000 fffff880`03d15000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A) fffff880`03d2d000 fffff880`03d48000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02dc9000 fffff880`02dd9000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00ed9000 fffff880`00f7d000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f7d000 fffff880`00f8c000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03cd0000 fffff880`03cd9000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00060000 fffff960`0036f000   win32k   win32k.sys   Sat Jun 19 00:31:59 2010 (4C1C483F) fffff880`044de000 fffff880`044e7000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00fe3000 fffff880`00fec000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`03823000 fffff880`03844000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1) fffff880`04435000 fffff880`04498000   yk62x64  yk62x64.sys  Mon Feb 23 10:02:27 2009 (49A2BA83)  Unloaded modules: fffff880`01600000 fffff880`0160e000   crashdmp.sys     Timestamp: unavailable (00000000)     Checksum:  00000000 fffff880`014ba000 fffff880`014c4000   dump_scsipor     Timestamp: unavailable (00000000)     Checksum:  00000000 fffff880`02cb4000 fffff880`02d41000   dump_mv91xx.     Timestamp: unavailable (00000000)     Checksum:  00000000 fffff880`02d49000 fffff880`02d5c000   dump_dumpfve     Timestamp: unavailable (00000000)     Checksum:  00000000

mrflib

Been running Prime, but as suspected BSOD so cuts out. I get BSOD's whether idle, whether GPU/CPU instensive, or whether simply browsing. Latest dump attached.

As I have quad core i7 I should be running with 8 threads tested in prime, is this correct? Alternatively should I be testing 4...?

Another quick question - could Chipset Drivers have anything to do with it? How can I find out what drivers I have and if I should upgrade them?

Thanks for your continued support.

EDIT

I should point out that I did in fact RMA the board, CPU and ram as a unit to my vendor. They declined the return stating they had run prime on it for 48 hours with no issue. I don't know what to think!

CarlTR6

Your latest dump is another error code 3B and nearly identical to the dump above. Both blame memory corruption and AirNCFG.exe. See my additions to my post above.

I am inclined to believe that your motherboard passed the Prime test. For now, we can forget Prime.

mrflib

�� Quote: Originally Posted by CarlTR6

RAM looks good. Just follow the tutorial for running Prime: http://www.sevenforums.com/tutorials...t-prime95.html

Error code 3B, SYSTEM_SERVICE_EXCEPTION - BSOD Index

The dump blames memory corruption and indicates AirNCFG.exe as the cause. Airncfg.exe - D-Link Wireless LAN Monitor is a process file from D-Link belonging to the Wireless LAN Monitor and I think this outdated driver, anodlwfx.sys, is part of it. I can find very little on this driver.

I have a D-Link wireless adapter and I have neither Airncfg.exe nor anodlwfx.sys on my system. I suspect that AIRncfg.exe is a configuration program for your adapter. When I installed the adapter, I did not install the configuration program. I let Windows configure my wireless with its built in program.

How old is your adapter? If it is more than two years old, I recommend that you try a new adapter. You can also try going to the D-Link website and upgrading the drivers and firmware for your D-Link model.

Thanks Carl.

The adaptor is brand new, and I think I did install a configuration program with the adaptor. How best to completely remove all of these unwarranted drivers/utilities? I will reinstall once prime has been running for a few hours/the next BSOD, whichever is sooner.

FTT testing is currently going on in Prime and thus far no errors, with CPU temps reaching 65-70 C.

EDIT

As per your advice I will finish prime for now, and focus on removing those drivers.

mrflib

Ok, first step I have uninstalled the Dlink adapater from Device manager. Then I had a bit of a facepalm moment as I realised in doing so I was unable to use the actual installer to uninstall the software. I've therefore deleted the files held within, including the infamous AirNCFG.exe which no longer loads on boot.

I have done a windows search for anodlwfx.sys and it can no longer be found. I have also disabled anything from dlink in msconfig in the startup section. This includes WZCSKDR2.exe, which is according to my research something to do with dlink. I have not however deleted the files just in case.

I am now running on a wired connection to the router, though the missus is incredibly unhappy with this situation so I don't know how long it will last.

For good measure, and I don't know if this will be of any use or entirely superfluous, I have redone my initial reports for you. See attached.

I guess we'll see how things run for a while. If I find it to be something as simple as this I will hit the roof! Then I'll be happy and drink beer.

Thanks again for all your help. I will keep you posted. Please let me know if there's anything else you want me to do.

CarlTR6

You are certainly welcome and I hope the solution is this simple.

Now that everything is running smoothly, create a restore point or a system image or both. Reinstall your D-Link adapter without the configuration program and let Windows configure it. Be sure to change the startup files. You may find it necessary to physically remove the adapter, reboot, shutdown, put the adapter back in, and install from scratch.

I am very interested to know if this solves the problem. Please let us know.

mrflib

Ok Carl - will do. I think what I may do is run this on the cable for a little while longer. No BSOD's yet, but it's early days. If I can get a good amount of time stable I will do exactly as you say. I will let Windows Update install the necessary drivers. I will certainly be back to give feedback!

CarlTR6

Looking forward to a good report without BSOD's attached. When you reinstall the adapter, let windows configure the wireless settings; don't install the configuration tool.

mrflib

Will do. I will plug it in, let it install, reenable all of the msconfig files I disabled for startup, reboot and carry on. System Restore point first, of course!

mrflib

Alas, BSOD.

mrflib

And another, this one while trying to install .net 4.0.

Edit: High frequency BSODs now!!! Argh!

mrflib

Gents,

Unfortunately BSOD's are now so frequent the PC is completely unusable. I am going to be forced to completely format and start again. I am now getting Bugcheck 50, 3B and 109 every couple of minutes.

To be quite honest I am really quite downhearted about the situation, I'm half tempted to break up the PC and sell the components.

Does anyone know a reputable, experienced technician or company in the London area of the UK who could diagnose and fix my errors? The professionals I have so far hired have not been equal to the task, much like myself.

Thank you all for your help so far. I will be back once formatted - which might be best as we can start on a completely clean system.

Pete

reventon

�� Quote: Originally Posted by mrflib

Hi Reventon,

I haven't had a chance to run Prime/Memtest since reinstall - unfortunately a lot of work has come up and I've needed the PC for other things. However, I did run IntelBurnTest - which failed. I was advised this tested CPU and RAM?



If you think I should still run the tests I can do memtest this evening and run prime overnight?

The above test uses a different test method to Prime95 (both are valid).

I would re-run the BurnInTest and if you get the same result take it to a local technician who is willing to put a working CPU in it for testing purposes.

Of course - if it's not the CPU that's faulty, the next most likely component is your motherboard.

Don't know any good technicians in London sorry!

Good luck

mrflib

Hi Reventon,

Thanks for the response. I have just reformatted completely and have taken the following actions:

1. Installed Windows 7
2. Let Windows Update get my Graphics Drivers and the default security updates it does on first boot
3. Updated the ATK0110 file from the Asus Website
4. Running on a wired connection - no Dlink adapter
5. Run the reports suggested by this forum
6. Additionally I have upped the voltage of the RAM in the BIOS from the default to 1.64V (DRAM Bus). BIOS was previously flashed to latest version.
7. As you can see the BIOS default the RAM to a slower speed than their spec - I have 1600 RAM. I assume this would not be an issue?
8. I have taken screenshots of CPU-Z
9. I have provided a SIW report and WinAudit in addition to your standard requests. These are in the attached zip file.
10. Attached 2 BSOD crash dumps that have already occured.

Before I can take this to a technician I want to at least get the basics of this system correct. As you can see from the reports, and my below Device Manager screenshot a couple of devices do not yet have drivers. Where is the correct place to download them from?

ATK0110 Driver at present


Device Manager at present


CPU-Z Screenshots







I realise I'm being a royal pain in the butt here, but I really don't know what else I can do. It seems you guys are my only hope.

Thank you all again for your extended time.

mrflib

As per your request, Reventon, IntelBurnTest run again. Failed again.



Also, I have uploaded a view of some power levels from Everest:

Jonathan_King

Well...

We know darn near 100% that this is a hardware problem:

Quote:

So I formatted for the thrid time and reinstalled Windows 7, immediately getting 2 BSOD's while trying to install and one on first boot (after 15 seconds of being in Windows).

RAM seems okay as far as Memtest86 goes. Your CPU test does not, but remember, no hardware test is perfect.

Now I looked up your motherboard manual and notice a few things. I have attached the pdf for reference.

First, reduce the RAM voltage slightly, as advised on Page 31.

Second, I do not find your RAM listed on the compatibility list. Would you mind taking a peek to confirm?

You may need to purchase some new RAM, or have a tech test some, that is found on that list, unless you can locate your RAM on there.

Apologies, even in a zip folder, I couldn't get the size of the pdf below the 8MB attachment limit here. I have instead uploaded it to Rapidshare: http://***************/files/42189998...5_P6X58D-E.pdf

mrflib

Lancaster, thank you very much for your time. Let's look at a couple of pages from the manual you kindly uploaded:

Code:

Page 2.4.2 Memory Configrations  Due to Intel spec definition, X.M.P. DIMMs and DDR3-1600 are supported for one DIMM per channel only.  According to Intel CPU spec, DIMM voltage below 1.65v is recommended to protect the CPU

I do have DDR3-1600, though as mentioned in the manual it is underclocked based upon the Serial Presence Detect. I have not altered this, and it's running at 1066.

The voltage (DRAM Bus) is set to 1.64. I could try lowering this to 1.50v? What do you think?

Also, looking at the QVL, I'm a bit confused. The part number given to me by CPU-Z is CM3X2G1600C9 - which I can only see as the middle part of a longer code on the QVL (see red box in image).

However, when purchasing I actually bought Overclockers UK (from aria.co.uk, though they dont stock it now). This is code TR3X6G1600C9 which is on the QVL (green box).



Flumoxed.

Edit, some screenshots of the BIOS

mrflib

Gents,

Thank you all for your time and effort, I am extremely grateful for the advice and support you have given me. I am more certain than ever that this issue is hardware related, and if I have to update another driver I think my head will explode!

I have been speaking with my retailer and we have agreed that a second RMA is the correct course of action. I will try to RMA the whole PC rather than just components this time.

I will of course keep you informed of any progress.

All the best and take care.

Pete

CarlTR6

Please do let us know how it goes. I hope your new computer is trouble free.

mrflib

Well I just got my PC back from the guys I purchased the components from - this time they agreed there is a fault with the RAM and have replaced it... If only they had agreed with me from the start.

They insist things are now running smoothly, but this post is the first thing I've done since I turned it on. Fingers crossed it works. Will keep you posted and thanks again for your time. Your posts here went some way to convincing the RMA team to take me seriously!

CarlTR6

Thanks for the update. I hope the new RAM has solved the problem. Please let us know.

mrflib

Seems solid as a rock now, which is great. Just proves that memory that passes memtest doesn't mean it's error free.

Thank you for your help.

CarlTR6

I am glad your problems are behind you. Thank you for reporting back and telling us the solution. Happy computing and don't be a stranger to the forum.