Solved Frequent BSOD's.. at wits end :(

[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,

[font=lucida console][B]STACK_TEXT:  [/B]
[color=blue]Ntfs[/color]!NtfsLookupAllocation+0x295
[color=blue]Ntfs[/color]!NtfsPrepareSimpleBuffers+0x146
[color=blue]Ntfs[/color]!NtfsPrepareBuffers+0xcb
[color=blue]Ntfs[/color]!NtfsNonCachedIo+0x1bc
[color=blue]Ntfs[/color]!NtfsCommonRead+0x7a6
[color=blue]Ntfs[/color]!NtfsFsdRead+0x1b8
fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fltmgr!FltpDispatch+0xcf
nt!IoPageRead+0x252
nt!MiIssueHardFault+0x255
nt!MmAccessFault+0x14bb
nt!KiPageFault+0x16e
0x7fe`fea3117a
[/font]

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[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

[font=lucida console][B]ASACPI.sys [/B]  Mon Mar 28 15:30:36 [B][COLOR=Red]2005[/COLOR][/B] (42476C4C)[/font]

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/100352-cpu-stress-test-prime95.html (run the Blend test as well as the Small FFT test)

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

BUGCHECK SUMMARY

[font=lucida console]
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 : [COLOR=Blue]memory_corruption[/COLOR]
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 [COLOR=Blue]MEMORY_MANAGEMENT[/COLOR]
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`48d38b4c 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[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]

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.