New
#11
Have you done what zigzag 3143 advised in Post 7...
Until you run Verifier as requested we will NOT have a definitive answer as to what is causing your problem.
Have you done what zigzag 3143 advised in Post 7...
Until you run Verifier as requested we will NOT have a definitive answer as to what is causing your problem.
I did like you described in your post. Although only the latest dump files that I've uploaded were made with verifier running.
I have installed the latest audio drivers and now I can't boot into normal mode with verifier running at all.
I'm attaching the dump file relative to the latest BSOD with verifier running.
The latest drivers are installed from asus, latest BIOS too.
Oh and i tried the verifier /query bit, doesn't seem to work in safe mode
Welcome to Seven Forums.
Always a good Idea to install new drivers from the Asus Motherboard website, also to update the UEFI BIOS(1101).
When you get a crash on a new build it's a good idea to take a close look at the hardware and it's settings in BIOS.
Can you download 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. Then post the screen shot in your next post, use this tutorial to do it.
How to Post a Screenshot in Seven Forums
With this information we can make better suggestions to find the cause of the crashes.
It is good that the RAM passed memtest86+ on another system, at least we know that the individual RAM cards are good.
You need to test it on your new build, if/when it is stable enough.
For now, take out two of your RAM cards, this will leave you with 2X4GB RAM. Check your motherboard manual for the correct RAM slots to use with two RAM cards, eight RAM slots is a lot to choose from.
Two RAM cards need to go in Dimm B1 and Dimm D1.
Your system may still not run stable with this amount of RAM.
Go to your UEFI and tell us what the first four RAM timings are set to, and the RAM frequency.
Also, what the DRAM and CPU IMC (Integrated Memory Controller) voltages are set at.
You may need to take out two of your graphics cards, try running it with one card until we can get it stable.
Did you check/update the Vertex 3 SSD firmware?
You have had 19 crashes today.
Your time setting must be off they are all dated 29 Jan 2012.
The last four crashes.
None of these are Driver Verifier caused, meaning the Driver Verifier is not set to run.
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Cause:
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000004b02, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000348694f, address which referenced memory Debugging Details: ------------------ PROCESS_NAME: audiodg.exe IMAGE_NAME: usbaudio.sys
STOP 0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
Usual causes: Device driver
This indicates that the system attempted to access pageable memory at a process IRQL that was too high.
Desktop Window Manager (dwm.exe) is the compositing window manager that gives you all those pretty effects in Windows.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_PORTION_MUST_BE_NONPAGED (d3) When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. 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 marking code or data as pageable when it should be marked nonpaged. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff88007bcba25, memory referenced Arg2: 0000000000000000, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff800036bdfe2, address which referenced memory Debugging Details: ------------------ PROCESS_NAME: dwm.exe IMAGE_NAME: hardware
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
Cause:
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
Code:******************************************************************************* * * * 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: fffff8000369894f, Address of the instruction which caused the bugcheck Arg3: fffff8801009d980, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ PROCESS_NAME: audiodg.exe IMAGE_NAME: usbaudio.sys
3b again.
Code:******************************************************************************* * * * 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: fffff800036e794f, Address of the instruction which caused the bugcheck Arg3: fffff880105d5a10, 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. PROCESS_NAME: audiodg.exe IMAGE_NAME: usbaudio.sys
From your System Events Log:
A lot of these.
Code:Event[20]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2012-01-28T16:56:11.696 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Neo Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor ID: 8 The details view of this entry contains further information. Event[107]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2012-01-28T16:53:27.164 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Neo Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor ID: 9 The details view of this entry contains further information. Event[250]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2012-01-28T16:46:04.156 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Neo Description: A corrected hardware error has occurred. Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor ID: 9 The details view of this entry contains further information.
This is indicating a CPU issue, could be motherboard also.
I would get Driver Verifier running first to see if it identifies any bad drivers.
Last edited by Dave76; 28 Jan 2012 at 09:16.
HI, thanks for the welcome :)
The BIOS has already been updated to 1101
The CPUZ screenshots are attached.
I can't boot into memtest on this system for some reason. It boots, past the post and i can see the memtest screen for a split second and it reboots by itself and enters a never ending loop or reboots after the post.
Ok, I'll check those and will remove two ram sticks.
I,m running with only one graphic card at the moment.
The vertex 3 firmware has been updated to the latest.
Last edited by yannickhk; 28 Jan 2012 at 08:38.
I don't get it, I stressed it for hours in safe mode, no crashes nothing ... Could it be a faulty CPU causing all those BSODs? I was about to change the MB but now I'm not so sure anymore.
I have AIDA64 installed, do you need some info from there?
Edit: I am stress testing the CPU with prime95 right now, nothing. Seems to be working just fine.
RAM Timing: 11 11 11 28
RAM frequency 1600Mhz
DRAM and CPU IMC set to auto
Last edited by yannickhk; 28 Jan 2012 at 09:24.
I did run verifier but the pc didn't crash any faster at all. I got the same BSODs that the one that I'm getting right now, without verifier.I would get Driver Verifier running first to see if it identifies any bad drivers.
Set everything, CPU, RAM, Graphics, all to stock settings, no OC'ing until the system is stable.
If memtest86+ can't even start, I would call that a RAM error.
Try re-burning to DVD, or if you are running it from a USB memory stick, re-download and re-install memtest86+. Just to be sure it's not corrupted.
Still have only two RAM cards installed and one graphics card.
The relaxed RAM timings should help them run stable.
Make the following RAM timing changes in the UEFI.
Change the tRAS to 30, that is the 4th setting. Will be 11-11-11-30.
Command Rate to 2T.
Save and exit UEFI.
Post the DRAM and VTT CPU (Integrated Memory Controller) voltage from UEFI.
The last crash dump files you posted after you enabled Driver Verifier, are not showing "Driver Verifier Enabled" dump files.
They actually say they are 'Driver Verifier' induced crashes, your dump files did not say that.
This means the Driver Verifier was not enabled.
From JMH post #2.
I would run Driver Verifier to check for any bad drivers before RMA'ing the CPU or motherboard.Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Run the Intel Processor Diagnostic Tool.
What is the Intel® Processor Diagnostic Tool?
Download the latest 64 bit version of the application (diagnostic tool) and/or supporting documentation:
Intel® Processor Diagnostic Tool (64 bit)**(download)
Last edited by Dave76; 28 Jan 2012 at 10:44.
You can tell if verifier is running and what drivers it is looking at by typing verifier /query. If it returns none it isnt looking at anything.
Follow the instructions carefully and if you need help dont hesitate to ask. Either JMH or I are on almost 24x7
It is probably a good idea to do one procedure at a time so your results will be valid.
Last edited by zigzag3143; 29 Jan 2012 at 01:03.