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

Racehunter · 11 Jan 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:

Attachment 192619
Attachment 192620
Attachment 192621
Attachment 192622
Attachment 192623

Dave76 · 12 Jan 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 · 14 Jan 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 · 15 Jan 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 · 15 Jan 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 · 15 Jan 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 · 15 Jan 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:  VERIFIER_ENABLED_VISTA_MINIDUMP
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:  VERIFIER_ENABLED_VISTA_MINIDUMP

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:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  ASSETUP.exe

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:  Asushwio.sys

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 · 15 Jan 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 · 15 Jan 2012

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

Racehunter · 15 Jan 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