Muliple BSOD's, Stalls, failure to boot etc etc and I am now desperate

Racehunter · Dec 24, 2011

Please see additional information at end of post and zipped files. Thanks

This could be a long thread so please bear with me (a virgin 'sevenforums' poster)...

I built my PC 10 months ago and felt it was reasonably specified for my needs. Antec 300 case, Asus M4A87TD/USB3 Mobo, AMD Phenom II X6 1055T processor, Seagate Barracuda ST3500418AS 500GB 3.5" SATA II Hard Drive, Palit GeForce GTX 460 768MB GDDR5 PCI-Express Graphics Card, Mushkin 4GB (2x2GB) DDR3 PC3-12800 8-8-8-24 Blackline memory and [FONT=&quot]Be Quiet 600W Straight Power E7 PSU. OS is Windows 7 Home Premium 64 bit and the rest is Office 2010.

All was well (in fact really good) until a few months ago when I started getting crashes at random times. It got to the point where a BSOD event would not always lead to a clean reboot, with either the windows load stalling or no activity whatsoever at attempted reboot. I did all the usual, checking that RAM was seated properly etc, I monitored CPU temps and updated BIOS and graphics drivers. Following the graphics driver update, it seemed to work correctly for a couple of weeks, then back came the problem. I even disabled auto updates so I could see and choose what was happening.

I have run 14 passes using memtest86 and got an all clear. Sometimes on restart the Windows repair utility comes up and after letting that run I just get a 'Windows cannot fix' message. It seems very random, especially as sometimes after 3 or 4 restarts, it will work correctly for the rest of the day.

Over the last couple of days I have gone a bit further and backed up my user profiles, cleaned the hard drive using Diskpart, partioned and formated again with Diskpart, reloaded Windows, graphics driver, motherboard utilities, then let the Windows only updates load (stopped all driver updates), reloaded Office and went to bed (2:30am this morning)

When I got up, all I had to do was expand the Windows partition and recover the user profiles, but the PC stalled on boot-up. I eventually got it to load but it crashed when I started the restore of user profiles.

I realise I have not posted any logs, as I thought that they would only be relevant to this mornings crash. I am getting so frustrated and could do with any help or direction. A little more information I have just thought of, when I try to attach a file to an Outlook email, in the usual way, Outlook 'hangs' and I end up having to restart that programme. I can however go to the file and right click to 'send as' and that works. This might be totally unrelated, but thought I should mention it now.

Thanks for reading

Steve

Ps I have had it crash when running in safe mode and when accessing the internet through Asus Express Gate, which is a utility that can load before the OS

I have eliminated HDD error as I have changed to a SSD and only loaded the OS, updates and drivers. The system crashed twice while gathering the information for the zip files.
[/FONT]

Racehunter · Dec 28, 2011

Additional information and files added.

Racehunter · Dec 31, 2011

Still not solved - Info on BSODs when running Windows Experience Index

This is a very frustrating situation now, and I would really appreciate some help from the many experts on this forum. This morning I booted the PC up and decided to run the Experience Index. After about 30 seconds, the system crashed with a BSOD. I rebooted, and it stalled at the Windows logo screen. Power off and plug out for 5 mins and it booted back up. Tried to run the Index again, only this time along side Taskmanager just to see if anything was happening. The 2nd BSOD occured after a similar time and the memory usage, on Taskmanager, was showing at 31%. To restart I had to go through the unplug scenario. Another BSOD after a short while of running the Index test and another unplug for 5 mins before restart. This time I managed to complete the Index test with a score of 7.4 (7.9 SDD).

Having looked at the dump files, to me, all of the 'possible causes' are different and I am wondering if it is a hardware issue. Could the PSU be at fault? I have also noticed that the PC seems more vunerable to errors in the period after start up and is a little more stable after say 30 minutes. Any advice to this newbee fault finder would be gratefully received.

PS dump files zipped and attached.

zigzag3143 · Dec 31, 2011

Racehunter said:
This is a very frustrating situation now, and I would really appreciate some help from the many experts on this forum. This morning I booted the PC up and decided to run the Experience Index. After about 30 seconds, the system crashed with a BSOD. I rebooted, and it stalled at the Windows logo screen. Power off and plug out for 5 mins and it booted back up. Tried to run the Index again, only this time along side Taskmanager just to see if anything was happening. The 2nd BSOD occured after a similar time and the memory usage, on Taskmanager, was showing at 31%. To restart I had to go through the unplug scenario. Another BSOD after a short while of running the Index test and another unplug for 5 mins before restart. This time I managed to complete the Index test with a score of 7.4 (7.9 SDD).

Having looked at the dump files, to me, all of the 'possible causes' are different and I am wondering if it is a hardware issue. Could the PSU be at fault? I have also noticed that the PC seems more vunerable to errors in the period after start up and is a little more stable after say 30 minutes. Any advice to this newbee fault finder would be gratefully received.

PS dump files zipped and attached.

Two Issues.

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Second

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

Might also want to remove and replace your McAffee.

Racehunter · Dec 31, 2011

Thanks for the reply ZigZag,

I have been monitoring temps closely and all is well so I don't think its a temperature issue. I will work through the links to the 2 problems you have highlighted. You mentioned that I might want to consider removing and replacing Mcafee. Can you tell me the reason why you suggest this? I am only 4 months into a new 12 month term with Mcafee so am reluctant to lose money

Steve

zigzag3143 · Dec 31, 2011

Racehunter said:
Thanks for the reply ZigZag,

I have been monitoring temps closely and all is well so I don't think its a temperature issue. I will work through the links to the 2 problems you have highlighted. You mentioned that I might want to consider removing and replacing Mcafee. Can you tell me the reason why you suggest this? I am only 4 months into a new 12 month term with Mcafee so am reluctant to lose money

Steve

Steve

Mcaffee is one of the top malware apps when it comes to causing BSOD's. It is difficult to remove, and can cause freezes (On some systems)

I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST!

http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

http://www.microsoft.com/security_essentials/

Dave76 · Jan 1, 2012

ZigZag is right, remove Mcafee for testing purposes.

You can re-install it later if the issue is resolved and does not point to this known BSoD causing software.

Use MSE until the BSoDs are resolved.
Microsoft Security Essentials*- Free Antivirus for Windows

Racehunter · Jan 10, 2012

Well, here I am again. Yet another clean install, driver updates disabled from Windows, Mcafee not installed (MSE installed) No dust or debris in chassis or components, stress-tested graphics card using Furmark (both versions) with no problem and maximum GPU temp of 77 deg C, yet I have just had 3 crashes in succession, and one eror messgae telling me the graphics driver stopped working temporarily before restarting successfully.

How much damage can I do with a 10lb hammer.......... Anyway, latest zip file attached for anyones expert perusal.

Dave76 · Jan 11, 2012

First, can you tell us what SSD you have?
This is important.

Your last crash is STOP 0x00000116: VIDEO_TDR_ERROR, again.
What NVidia graphics driver version are you using?
Update it if it's not the current driver, be sure to completely delete the current driver first, use Driver Sweeper.
If it is the latest driver, completely delete the current driver first, use Driver Sweeper, download and install the last known working driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800728b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004eec188, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+6ec188
fffff880`04eec188 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`061bcb88 fffff880`0412d000 : 00000000`00000116 fffffa80`0728b010 fffff880`04eec188 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`061bcb90 fffff880`04100867 : fffff880`04eec188 fffffa80`061f0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061bcbd0 fffff880`0412ce0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0728b010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`061bcc80 fffff880`04037ec1 : fffffa80`06263220 00000000`00000080 00000000`00000000 fffffa80`0620d230 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`061bcd00 fffff800`03135fee : 00000000`fffffc32 fffffa80`061e1060 fffffa80`039ed040 fffffa80`061e1060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`061bcd40 fffff800`02e8c5e6 : fffff880`0308f180 fffffa80`061e1060 fffff880`0309a040 fffff880`01227384 : nt!PspSystemThreadStartup+0x5a
fffff880`061bcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+6ec188
fffff880`04eec188 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+6ec188

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c6d3530

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

Old, out of date drivers:

Code:

AtiPcie.sys  Tue May 05 23:00:22 2009

Get the latest chipset driver from Asus.

Have you updated all the motherboard drivers from the Asus website?
Don't use the drivers on the CD/DVD, they are old versions.

Second to last crash was STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880043f3d29, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003103100
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
usbohci!OHCI_PollAsyncEndpoint+37d
fffff880`043f3d29 f0834b2808      lock or dword ptr [rbx+28h],8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030b7990 -- (.trap 0xfffff880030b7990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800532e860
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043f3d29 rsp=fffff880030b7b20 rbp=fffff88005fa6160
 r8=000000004f444648  r9=0000000000000000 r10=00000000ffffffff
r11=00000000ced7c162 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbohci!OHCI_PollAsyncEndpoint+0x37d:
fffff880`043f3d29 f0834b2808      lock or dword ptr [rbx+28h],8 ds:e000:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed01e9 to fffff80002ed0c40

STACK_TEXT:  
fffff880`030b7848 fffff800`02ed01e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b7850 fffff800`02ecee60 : fffffa80`059d1b98 fffffa80`058f2960 fffffa80`051461a0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b7990 fffff880`043f3d29 : 00000000`00000000 fffffa80`058f2c30 00000000`00000000 fffff880`05fa6000 : nt!KiPageFault+0x260
fffff880`030b7b20 fffff880`043f5737 : fffffa80`058f2ba8 fffffa80`058f2960 00000000`00000000 fffffa80`051461a0 : usbohci!OHCI_PollAsyncEndpoint+0x37d
fffff880`030b7b80 fffff880`04464e8b : 00000000`00000002 fffffa80`058f2960 fffffa80`051461a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff880`030b7bb0 fffff880`044699d1 : 00000000`00000010 00000000`00000004 fffffa80`058f2960 fffffa80`05146050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`030b7be0 fffff880`04475077 : fffffa80`051461a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`030b7c40 fffff880`04465f89 : fffffa80`05146050 00000000`00000000 fffffa80`05146a02 fffffa80`05146a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`030b7ca0 fffff800`02edc0ac : fffff880`0308f180 fffffa80`05146a18 fffffa80`05146a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b7cd0 fffff800`02ec896a : fffff880`0308f180 fffff880`0309a040 00000000`00000000 fffff880`04465db0 : nt!KiRetireDpcList+0x1bc
fffff880`030b7d80 00000000`00000000 : fffff880`030b8000 fffff880`030b2000 fffff880`030b7d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbohci!OHCI_PollAsyncEndpoint+37d
fffff880`043f3d29 f0834b2808      lock or dword ptr [rbx+28h],8

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbohci!OHCI_PollAsyncEndpoint+37d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbohci

IMAGE_NAME:  usbohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0bff

FAILURE_BUCKET_ID:  X64_0xD1_usbohci!OHCI_PollAsyncEndpoint+37d

BUCKET_ID:  X64_0xD1_usbohci!OHCI_PollAsyncEndpoint+37d

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

The crash file blamed a Windows OHCI USB Miniport Driver.
This is likely the result of the problem and not the cause.

Third from last crash was STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA, This indicates that invalid system memory has been referenced.
This was the first since you re-installed Windows.
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff6999c000030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e7127b, 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 fffff800030b9100
 fffff6999c000030 

FAULTING_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`02e7127b 488b19          mov     rbx,qword ptr [rcx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031eb7c0 -- (.trap 0xfffff880031eb7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6999c000030
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e7127b rsp=fffff880031eb950 rbp=000000199c000033
 r8=0000000000000001  r9=fffffa8003b7cec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1d1:
fffff800`02e7127b 488b19          mov     rbx,qword ptr [rcx] ds:fffff699`9c000030=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e313bf to fffff80002e86c40

STACK_TEXT:  
fffff880`031eb658 fffff800`02e313bf : 00000000`00000050 fffff699`9c000030 00000000`00000000 fffff880`031eb7c0 : nt!KeBugCheckEx
fffff880`031eb660 fffff800`02e84d6e : 00000000`00000000 fffff699`9c000030 00000000`00001000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`031eb7c0 fffff800`02e7127b : 00000003`00000000 b2f00000`1a385867 00000000`00000000 00000000`0000332f : nt!KiPageFault+0x16e
fffff880`031eb950 fffff800`02f02ac5 : fffffa80`03b7cec8 fffff880`00000001 00000000`00000001 fffff880`031ebbb0 : nt!MiAgeWorkingSet+0x1d1
fffff880`031ebb00 fffff800`02e71826 : 00000000`000005ed 00000000`00000000 fffffa80`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x4d786
fffff880`031ebb80 fffff800`02e71cd3 : 00000000`00000008 fffff880`031ebc10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`031ebbd0 fffff800`03121fee : fffffa80`03abca60 00000000`00000080 fffffa80`039d3040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`031ebd40 fffff800`02e785e6 : fffff880`02f63180 fffffa80`03abca60 fffff880`02f6e040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031ebd80 00000000`00000000 : fffff880`031ec000 fffff880`031e6000 fffff880`031eb700 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1d1
fffff800`02e7127b 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1

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

There is a known issue with the AMD IMC (Integrated Memory Controller) with RAM frequencies above 1333MHz.
I hope AMD will solve this soon.

Run memtest86+ again, I have seen it pass several times and then throw errors, that means the RAM settings need adjusted.
Run it with both RAM cards installed.
RAM - Test with Memtest86+

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your CPU temperatures?
You mentioned that you have, what are the CPU temps?
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Racehunter · Jan 11, 2012

The version of Nvidia driver is 8.17.12.5944. This is the original of the graphics card CD. During my trials and test I have used later drivers as soon as I have done a clean install so no problem of having to remove driver fragments. However I will try again with 'calculated' updates. With regards to Driver Sweeper, which do you recommend. If I remember correctly, the one on Guru site no longer has a download link.

Thanks

Steve

PS The SSD is an OCZ Vertex 3 120Gb but I have uninstalled it as I was getting crashes with and without. The other information, I will gather later and post.

Racehunter · Jan 11, 2012

Ok, here is some more information. I have correctly removed the Nvidia driver with Driver Sweeper and installed the latest one from their website. I have also updated the chipset and motherboard drivers that needed doing so. I have been into BIOS and noted the VCore, 3.3V, 5V and 12V figures, which correspond to those shown by PC Probe (Asus utility) Downloaded and run the CoreTemp tool as well as the CPU-Z tool and snipped the relevant tabs. One thing I have noticed is that the CPU temp indicated by the BIOS was 43 deg C (Mobo 26 deg C) which was some 9 degs higher than indicated by the desktop tool.

That leaves me to continue to log CPU temps (possibly stress test at the same time) and run Memtest86 again. Here are the snipped pictures:

View attachment 192619
View attachment 192620
View attachment 192621
View attachment 192622
View attachment 192623

Dave76 · Jan 12, 2012

All the CPUZ information looks good.
Your RAM is running at 1333MHz, it will be stable at this frequency.

Leave the OCZ Vertex 3 out until the cause is found, these SSDs can have a controller BSoD issue.

Motherboard utilities, generally, can cause BSoDs, uninstall Asus PC Probe and any other Asus utilities for testing purposes.

Download your motherboard manual: Asus M4A87TD/USB3
Page 2-14, Ai Tweaker menu, CPU/NB Offset Voltage, this is the Integrated Memory Controller voltage.
Post the voltage, if you can't see it, change it to 'Manual' and it will show you a value.

When you got the CPU core temps, was your system at an idle?
Post the CPU core temps (using Core Temp) with your system at an idle and when stressed, use Prime95 Blend test, max RAM.

CPU - Stress Test with Prime95
If memtest86+ passes then run Prime95 torture test.
First open Core Temp to monitor CPU temperatures, don't go over 67°C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 6, then click OK to start the test.

Racehunter · Jan 14, 2012

Dave,

Finally got back to running the tests and here are the results:

Ran Memtest86 overnight again, and after 9 hours, no fault found (both sticks in)

CPU/NB Offset Voltage - 1.150

CPU Temps - Idle 24 deg C. Maximum reached running Prime95 Blend test 48 deg C but most of the time 46 deg. (over 1 hour test time) Maximum reached running the Torture test was 47 deg C but mainly at 45 deg (nearly 2 hours test time)

I did not get an error during this time.

Does this tell you anything?

Steve

Dave76 · Jan 15, 2012

Have you had any crashes since your last posted crash?

Any/all RAM testing apps may show no errors and then after several runs show errors.
This is normal and due to the difficulty of finding problems with RAM, just a fact of electronics.
We'll call the RAM good for now but, may need to come back to it.
May adjust some of the RAM settings if we don't find a driver issue.

CPU temps look normal for your CPU.

Did you uninstall the Asus utilities for testing purposes yet?

Racehunter · Jan 15, 2012

I ran Prime95 Torture test overnight and during the test, the system crashed. Additionally I had problems getting it started earlier in the day, while today I have had 2 seperate crashes.

Zip files attached. Asus utilities was removed as requested.

Thanks in advance

Layback Bear · Jan 15, 2012

Just a thought. Be Quiet power supply. Can't really find but a few reviews but most of them were just specs and pictures. Did find 2 reviews that stated they didn't put out the amps and volts as specified on label. After the hell racehunter has had with this computer I would get a power supply like Antec, Corsair, Seasonic which are know quality power supplies. The few reviews I have found do say that the Be Quiet power supplies are very quiet.

Dave76 · Jan 15, 2012

A Prime95 torture test failure indicates CPU and/or RAM.
There are several things that can cause a CPU error, drivers, settings, voltage settings including the PSU.

Are you overclocking CPU or GPU?
If you are, return to default settings for testing.

The PSU issue mentioned by Layback Bear is definitely worth looking into.
Do you have a spare PSU or can you borrow one for testing?

STOP 0x000000C5: DRIVER_CORRUPTED_EXPOOL
Usual causes: Device driver, ?Memory
Cause: The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.
The Verifier Enabled crash doesn't indicate a specific driver, only 'System'.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80003000f13, address which referenced memory

DEFAULT_BUCKET_ID:  [COLOR="Red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
PROCESS_NAME:  System
BUCKET_ID:  X64_0xC5_2_VRF_nt!ExDeferredFreePool+1570

Followup: Pool_corruption

STOP 0x100000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
This Driver Verifier Enabled crash is blaming: usbohci.sys - Windows OHCI USB Miniport Driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002ca6d29, address which referenced memory
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003101100
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
usbohci!OHCI_PollAsyncEndpoint+37d
fffff880`02ca6d29 f0834b2808      lock or dword ptr [rbx+28h],8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR="Red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

FOLLOWUP_IP: 
usbohci!OHCI_PollAsyncEndpoint+37d
fffff880`02ca6d29 f0834b2808      lock or dword ptr [rbx+28h],8

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbohci!OHCI_PollAsyncEndpoint+37d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbohci

IMAGE_NAME:  usbohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0bff

FAILURE_BUCKET_ID:  X64_0xD1_VRF_usbohci!OHCI_PollAsyncEndpoint+37d

BUCKET_ID:  X64_0xD1_VRF_usbohci!OHCI_PollAsyncEndpoint+37d

Followup: MachineOwner

STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
This is blaming: Asushwio.sys file is installed and associated with ASUS Utilities and Drivers.
Did you uninstall all of the Asus utilities?

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000c4, Handle value being referenced.
Arg3: fffffa800631ab30, Address of the current process.
Arg4: fffff88005fc1436, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  [COLOR="red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]

PROCESS_NAME:  [COLOR="red"]ASSETUP.exe[/COLOR]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000335c3dc to fffff80002ed2c40

STACK_TEXT:  
fffff880`07e8b598 fffff800`0335c3dc : 00000000`000000c4 00000000`000000f6 00000000`000000c4 fffffa80`0631ab30 : nt!KeBugCheckEx
fffff880`07e8b5a0 fffff800`03371ae4 : 00000000`000000c4 fffffa80`0631ab30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`07e8b5e0 fffff800`0312a210 : 00000000`00000000 fffff880`07e8b810 00000000`00000000 00000000`00000000 : nt!VfCheckUserHandle+0x1b4
fffff880`07e8b6c0 fffff800`031ad375 : fffffa80`0535cb00 00000000`000f001f 00000000`00000000 fffff800`031ad300 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`07e8b790 fffff800`03371878 : 00000000`00000001 00000000`00000002 fffff880`07e8b880 fffff800`02ece470 : nt!ObReferenceObjectByHandle+0x25
fffff880`07e8b7e0 fffff880`05fc1436 : 00000000`00000000 00000000`00000002 00000000`00000001 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`07e8b830 00000000`00000000 : 00000000`00000002 00000000`00000001 00000000`00000000 fffff880`07e8b8b8 : Asushwio+0x1436


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Asushwio+1436
fffff880`05fc1436 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Asushwio+1436

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Asushwio

IMAGE_NAME:  [COLOR="Red"]Asushwio.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4774a4bf

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_Asushwio+1436

BUCKET_ID:  X64_0xc4_f6_VRF_Asushwio+1436

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

System event logs.

Code:

Event[174]:
  Log Name: System
  Source: Microsoft Antimalware
  Date: 2012-01-15T10:50:25.000
  Event ID: 3002
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Aquuileus
  Description: 
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
 	Feature: Behavior Monitoring
 	Error Code: 0x80004005
 	Error description: Unspecified error 
 	Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

Update MSE definition files through Windows Update.

Code:

Event[759]:
  Log Name: System
  Source: Server
  Date: 2012-01-14T14:47:44.000
  Event ID: 2505
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Aquuileus
  Description: 
The server could not bind to the transport \Device\NetBT_Tcpip_{DBD166DC-7D27-4707-B44F-9E1759C9DE2B} because another computer on the network has the same name.  The server could not start.

If you have another computer with the same name on your network you must change one of the names and add it to the network.

Racehunter · Jan 15, 2012

I am not clocking at all. In fact I never have done. The error message indicating Asus setup was probably set when I deleted the utility and lost ethernet connectivity for some reason. I had to restore to a point 2 days earlier to get it up and running again. I thought it was just a problem with the driver but tried to reload from the Asus disc and it errored every time saying that some file or other could not be accessed.

With regards to the PSU, as I did wonder about this, I bought an Antec Truepower 750W modular unit to try, but as yet havent fitted it as I woud rather track down the reason first. I think I should install it tomorrow and see what happens. For the small cost, I also think I will pick up some more RAM. Any suggestions as to the best suited for my board? Should I stay with 1333mhz or go up to 1600?

My Windows phone does carry the same name as the PC so again, I will correct that.

Many thanks for all of the suggestions and I will keep you informed how it goes now.

Steve

Layback Bear · Jan 15, 2012

This will help you.
ASUSTeK Computer Inc. - Motherboards- ASUS M4A87TD/USB3

Racehunter · Jan 15, 2012

Thanks for the link. I am sure that it was mentioned in an earlier post that there is an issue with running RAM at more than 1333MHz, so I suppose I should stay with that frequency?

Anyway, I booted PC up tonight with the intention of running Prime95 again. I logged on and then started Prime, but got A BSOD as soon as it started to set itself in motion. Had to press the reset button to get it going again, then it shut itself down soon after I logged on. This time it auto started, but did exactly the same when I tried to open Control Panel.

There seems to be some correlation between trying to quickly open programmes, files, folders etc and switch between them shortly after the PC has been started. The dump file for the BSOD was VIDEO_TDR_FAILUE (116) again.

Steve

Muliple BSOD's, Stalls, failure to boot etc etc and I am now desperate

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Endeavor to Persevere

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Endeavor to Persevere

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Endeavor to Persevere

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Endeavor to Persevere

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

3 Brain Cells

My Computer My Computer

At a glance

Endeavor to Persevere

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

3 Brain Cells

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer