New
#11
OK. Disable verifier now, and use the computer normally. If you get one more crash, let us see it.
OK. Disable verifier now, and use the computer normally. If you get one more crash, let us see it.
So I tested the CPU with the IntelBurn test and it passed. Did exactly as in the link to restart into verifier mode. After the restart, Windows hangs at the "Starting Windows" screen where it has been for the last 30-45 minutes and does nothing.
new crash:IRQL_NOT_LESS_OR_EQUAL 0x0000000a. Working on getting the crash dump packed into a zip.
Couldn't get the thing to start in normal mode, but at least got into safe mode to get the minidump. Anything else with the minidump tool I was unable to get because of the lack of the Netframework.
Disable Driver verifier as stated earlier. It is not of any more help as it is seen.
Try to update the following drivers:Code:CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System
Atheros network adapter driver: ATHEROS drivers for Microsoft Windows (Atheros?????)
Atheros Bluetooth Driver: ATHEROS drivers for Microsoft Windows (Atheros?????)
Conexant High Definition SmartAudio: Conexant - Support
Intel Management Engine Interface: Intel Download Center
Intel rapid Storage driver: http://downloadcenter.intel.com/Deta...ST%29&lang=eng
nVidia Video drivers: Drivers - Download NVIDIA Drivers
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC: Realtek
Microsoft Application Virtualization (App-V) driver: Application Virtualization by Microsoft | Windows 8 Enterprise
Does machine BSOD in safe mode ?
if not you could try a clean boot Troubleshoot Application Conflicts by Performing a Clean Startup to remove all startup items and all non MS services, its a long shot but worth a try IMO
Also you have stressed cpu how about gfx and that has ram too ?
Video Card - Stress Test with Furmark
Last edited by Pauly; 17 Jan 2013 at 11:54.
Looks like a stubborn one.
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes. Each crash report will contain new information that will be useful.
Run the OCCT stability test, at the end it will produce graphs that may give some clues .
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.
Which Intel RST driver are you using?
If it's not v11.2.0.1006 or earlier, install v11.2.0.1006. there have been known issues with drivers after that version.
Intel Rapid Storage Technology 11.2.0.1006
Hardware can be very fickle, it does happen that a component will pass tests several times and then fail, especially RAM and to a lesser extent hard drives.
If the RST driver doesn't help, you may consider installing a different HDD and testing the system. That way the clients HDD and programs won't be disturbed.
If allowed, remove all Sony utilities, these types of programs are known to crash systems.
From old System Events logs:
Need the current System Event Logs to confirm.Code:Event[34981]: Log Name: System Source: Microsoft-Windows-Kernel-Processor-Power Date: 2012-12-06T14:55:40.622 Event ID: 26 Task: N/A Level: Informationen Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT-AUTORITÄT\SYSTEM Computer: Henning-VAIO Description: Prozessor 3 in Gruppe 0 weist Folgendes auf: 2 inaktive Zustände 7 Leistungszustände 8 Drosselungszustände Event[34982]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2012-12-06T14:55:41.590 Event ID: 89 Task: N/A Level: Informationen Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT-AUTORITÄT\SYSTEM Computer: Henning-VAIO Description: Die ACPI-Thermozone ACPI\ThermalZone\THRM wurde aufgelistet. _PSV = 374K _TC1 = 2 _TC2 = 5 _TSP = 1000ms _AC0 = 0K _AC1 = 0K _AC2 = 0K _AC3 = 0K _AC4 = 0K _AC5 = 0K _AC6 = 0K _AC7 = 0K _AC8 = 0K _AC9 = 0K _CRT = 357K _HOT = 0K _PSL - siehe Ereignisdaten.
This system has been overheating in the past.
The last Event Log entry was 2012-12-06, check setting, Clear Log if no new event are recorded.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.
If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.
Can you translate this Critical Event:
There are 48 items in the Start Menu, you should remove most of these and/or have them start at login.Code:Event[34976]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2012-12-06T14:55:39.671 Event ID: 41 Task: N/A Level: Kritisch Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT-AUTORITÄT\SYSTEM Computer: Henning-VAIO Description: Das System wurde neu gestartet, ohne dass es zuvor ordnungsgemäß heruntergefahren wurde. Dieser Fehler kann auftreten, wenn das System nicht mehr reagiert hat oder abgestürzt ist oder die Stromzufuhr unerwartet unterbrochen wurde.
Uninstall McAfee, it is known to cause crashes in Windows 7. Use MSE for testing.
From your App Event Log (which are up to date):Code:Event[34726]: Log Name: System Source: Service Control Manager Date: 2012-12-06T11:17:51.889 Event ID: 7036 Task: N/A Level: Informationen Opcode: N/A Keyword: Klassisch User: N/A User Name: N/A Computer: Henning-VAIO Description: Dienst "McAfee Scanner" befindet sich jetzt im Status "Beendet".
This is a CPU error, usually caused by overheating.
A lot of these.
Code:Event[18373]: Log Name: Application Source: Microsoft-Windows-WMI Date: 2013-01-17T09:31:51.000 Event ID: 10 Task: N/A Level: Fehler Opcode: N/A Keyword: Klassisch User: N/A User Name: N/A Computer: Henning-VAIO Description: Ereignisfilter mit Abfrage "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" konnte im Namespace "//./root/CIMV2" nicht reaktiviert werden aufgrund des Fehlers 0x80041003. Ereignisse können nicht durch diesen Filter geschickt werden, bis dieses Problem gelöst ist.
Last edited by Dave76; 18 Jan 2013 at 03:12.
New BSOD: 0x0000000A MEMORY_MANAGEMENT. I could not get the Seven Forums Diagnostic Tool to get all of the logs on my Desktop. I don't know why. I started it as Administrator, but it does not post the logs to the desktop. I got the new minidump and zipped it. OCCT is on a 30 minute test. I'll post results afterwards.
Give the Seven Forums Diagnostic Tool more time to run.
Change the Intel RST driver to v11.2.0.1006.
Last crash:
Not much info to go on.
Need the Event Logs.Code:STOP 0x0000001A: MEMORY_MANAGEMENT Usual causes: Device driver, memory, kernel BUGCHECK_STR: 0x1a_5100 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+aec7 FAILURE_BUCKET_ID: X64_0x1a_5100_nt!_??_::FNODOBFM::_string_+aec7
Done. Here are the OCCT results: