Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Totally Random BSOD with windows 7 64 and RIVE

28 Jan 2012   #11
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

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.



My System SpecsSystem Spec
.
28 Jan 2012   #12
yannickhk

Windows 7 ultimate 64bits
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by yannickhk View Post
Here goes, just had 4 bsods in a row
Are they driver verified? what drivers did verifiy /query say it was verifying?


You might want run malwarebytes just in case.

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.



Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!
If you mean that the BSODs happened with verifier running then yes, it was. I followed the above post to the letter.
My System SpecsSystem Spec
28 Jan 2012   #13
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by yannickhk View Post
Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by yannickhk View Post
Here goes, just had 4 bsods in a row
Are they driver verified? what drivers did verifiy /query say it was verifying?


You might want run malwarebytes just in case.

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.



Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!
If you mean that the BSODs happened with verifier running then yes, it was. I followed the above post to the letter.
When you typed verifier /query, what drivers were being verified?
My System SpecsSystem Spec
.

28 Jan 2012   #14
yannickhk

Windows 7 ultimate 64bits
 
 

Quote   Quote: Originally Posted by JMH View Post
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
My System SpecsSystem Spec
28 Jan 2012   #15
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

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.
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
Desktop Window Manager (dwm.exe) is the compositing window manager that gives you all those pretty effects in Windows.


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.
My System SpecsSystem Spec
28 Jan 2012   #16
yannickhk

Windows 7 ultimate 64bits
 
 

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.
My System SpecsSystem Spec
28 Jan 2012   #17
yannickhk

Windows 7 ultimate 64bits
 
 

Quote   Quote: Originally Posted by Dave76 View Post
Welcome to Seven Forums.

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.
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
My System SpecsSystem Spec
28 Jan 2012   #18
yannickhk

Windows 7 ultimate 64bits
 
 

Quote:
I would get Driver Verifier running first to see if it identifies any bad drivers.
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.
My System SpecsSystem Spec
28 Jan 2012   #19
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

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.
Quote:
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.
I would run Driver Verifier to check for any bad drivers before RMA'ing the CPU or motherboard.


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)
My System SpecsSystem Spec
28 Jan 2012   #20
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by yannickhk View Post
Quote:
I would get Driver Verifier running first to see if it identifies any bad drivers.
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.

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.
My System SpecsSystem Spec
Reply

 Totally Random BSOD with windows 7 64 and RIVE




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD totally random, Locale ID: 1043
Dear readers, Small introduction since I've this bad feeling we won't solve this problem quickly. My name is Ben and I live in Holland. Study accountancy and I'm 21 years old. I want to thank everyone in advance, first of all, for any help they may give. So I've been running this computer...
BSOD Help and Support
Bsod's, random restarts I'm totally confused.
This is my first post, so hi everybody. To the point... asus m5a78l-m lx AMD PHENOM II X4 960T Msi R6870 hawk 4gb DDR3 Kingston 1000gb seagate
BSOD Help and Support
BSOD Playing games and sometimes totally random dxgmms1.sys + ntoskrnl
About a half a year ago I've bought a totally new PC configuration. It went clearly but in the last one and a half month i started to get BSOD. The problem is coming mostly during playing games but sometimes on a clear desktop the PC reset with a BSOD. I tried to solve it by searching the error...
BSOD Help and Support
Totally random BSODs.
Hello! I'm suffering from really random BSOD's (it can be sometimes just crash, restart or GSOD too) - i can just watch desktop and it can crash. It's been happening for months (about 4-5) and I still didn't find any solution. I've got some minidumps from 3 weeks (had format). Main problem:...
BSOD Help and Support
BSOD - BCCode: 101 on totally new rig!
I really hope someone is able to help me troubleshoot this issue! I have recently bought and build a new computer - and Windows 7 Home Premium x64: ASUS P8H67-M EVO B3 Sandy Bridge Intel Core i7 2600 Sandy Bridge 3.4GHz Zalman ZM600-HP Power Supply Kingston 8GB DDR3 1333mHz (2x4) ValueRam...
BSOD Help and Support
totally random BSOD?
hello people. i have been getting random BSOD's lately. this is the first one in a few days, and sometimes my PC runs for a week without a BSOD. so, this is what windows said at boot: Probleemhandtekening: Gebeurtenisnaam van probleem: BlueScreen Versie van besturingssysteem: ...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:07.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App