BSOD BCCode:1000007e

[Tyrandis]

I was playing Battlefield 4 until my computer locked up and gave me a blue screen. This is not the first time that it happened and would like to know what went wrong.

-----------------------------------------------------------------------------------------------------
Loading Dump File [C:\New folder\New folder\111013-8314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0341d000 PsLoadedModuleList = 0xfffff800`03661650
Debug session time: Sun Nov 10 10:43:06.610 2013 (UTC - 7:00)
System Uptime: 0 days 0:20:30.437
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800fb4e03b, fffff8800cac16c8, fffff8800cac0f20}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+7a03b )
Followup: MachineOwner
---------

 

[YoYo155]

Welcome, please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html .

Also please revert back any overclocks back to stock.

!sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502

 

[Tyrandis]

I tried to use the sf diagnostic tool for the forum but I got an error saying

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.IOException: Could not complete operation on some files and directories. See the Data property of the exception for more details.
at Microsoft.VisualBasic.FileIO.FileSystem.FxCopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryPath, String targetDirectoryPath, Boolean overwrite)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyDirectory(String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite)
at SF_Diagnostic_Tool.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diagnostic Tool
Assembly Version: 5.0.0.6
Win32 Version: 5.0.0.6
CodeBase: file:///C:/Users/****face/AppData/Local/Temp/Rar$EXa0.791/SF_Diagnostic_Tool.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSI...0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSI....0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSI..._b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

[YoYo155]

Try the TOOL again, make sure you run it as administrator Righ-click and choose "Run as administrator" and click each of the buttons individually except for CPU-Z.

 

[Tyrandis]

Ah I see... I had to run as admin, make sense. Well here are the dump files like you said and thanks!

View attachment 293284

 

[YoYo155]

Thanks for the file unfortunately some are missing, so I'm not getting the full picture.
Please run the SFDT again and let it run its course it can take 15min at times to collect all the data necessary.
There should be eight files generated not including the dumps.

Besides I asked to remove any overclocks that was applied and report back if things continue
to remain unstable, this includes the RAM and GPU as well .

 

[Tyrandis]

Ok I have all of my 8 attachments now but sadly I couldn't get my gpu, ram and cpu at stock clock because my computer would bsod when playing games which is really weird but it happened I guess.... really disappointing, but anyway here are my attachments and hopefully the problem would be an easy fix haha and thanks for helping me!

View attachment 293444

 

[YoYo155]

Ok I have all of my 8 attachments now but sadly I couldn't get my gpu, ram and cpu at stock clock because my computer would bsod when playing games which is really weird but it happened I guess.... really disappointing, but anyway here are my attachments and hopefully the problem would be an easy fix haha and thanks for helping me!

View attachment 293444

Thanks for the files .
How did you go about removing the overclocks?

 

[Tyrandis]

Well I changed the settings on the bios by setting the cpu and ram to stock clock and used precision to change my gpu back to stock clock but for some reason my computer liked it until I was playing games on it then it would give me a bsod.

 

[YoYo155]

Upload the new dumps, did you verify in any way if the CPU and GPU are in fact back at stock settings?
Use CPU-Z and GPU-Z to monitor and upload a screenshot of the clocks while under stress.

Test for thermals and stability:

• Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).

CPU-Z | GPU-Z

 

[Tyrandis]

Well I just finished the screenshots and the minidumps are all in my WinRAR archive. The last BSOD I had should be the last minidump. /cheers

View attachment 293541

View attachment 293542

 

[Tyrandis]

Well here are my file attachment's, one will have pictures while the other will have the minidumps.

View attachment 293543

View attachment 293544

 

[YoYo155]

No worries it happens .

Thanks for the files, at the moment it appears to be a RAM issue please follow the quotes
posted below, in the order they appear in.

Testing the RAM:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

:ar:When done with the testing procedure take a picture and upload it here.

If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Keep us posted .

 

[Tyrandis]

I have some bad news.... it seems like I have no errors which means that the problem is somewhere else....

View attachment 293681

 

[YoYo155]

Thanks.
Continue with the second part of post #13, enabling Driver Verifier.

 

[Tyrandis]

Sigh, I really thought that there wont be any more blue screens but it happened again. (very bottom of the minidumps)

View attachment 293932

 

[YoYo155]

You didn't enable Driver Verifier, any particular reason not to?
The last dump holds a cluster of drivers of all sorts, all of which are outdated.

First things first, verify that both the of the GPU's clocks are at stock speeds then remove EVGA Precision.

lmvm [U]RTCore64[/U]
Browse full module list
start             end                 module name
fffff880`0c71f000 fffff880`0c725000   RTCore64   (deferred)             
    Image path: \??\D:\EVGA Precision\RTCore64.sys
    Image name: RTCore64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U]Wed May 25 09:39:12 2005[/U][/COLOR]

• Driver Reference Table - RTCore64.sys

Update any Intel driver using this online utility:

lmvm [U]e1c62x64[/U]
Browse full module list
start             end                 module name
fffff880`04b47000 fffff880`04b96000   e1c62x64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U]Wed Sep 22 00:34:15 2010[/U][/COLOR]

• Driver Reference Table - e1c62x64.sys
• Intel® Driver Update Utility

Update the HD Audio driver:

lmvm [U]RTKVHD64[/U]
Browse full module list
start             end                 module name
fffff880`0748a000 fffff880`076f3800   RTKVHD64   (deferred)             
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U]Tue Nov 02 13:25:59 2010[/U][/COLOR]

• Driver Reference Table - RTKVHD64.sys
• Description | Version | Update | File Size | Download
  

  64bits Vista, Windows7, Windows8, Windows8.1 Driver only (Executable file) | R2.73 | 2013/11/11 | 106402k | Choose a server​

Update your network adapter and then disable it,
rb: Srat > type > network connections then press enter > Find the adapter Right-click > Disable.

lmvm [U]Rt64win7[/U]
Browse full module list
start             end                 module name
fffff880`05e08000 fffff880`05e72000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U]Wed Feb 16 11:03:57 2011[/U][/COLOR]

• Driver Reference Table - Rt64win7.sys

Description | Version | Update | File Size | Download

Win7 and WinServer 2008 R2 Auto Installation Program (SID:1606895) | 7.075 | 2013/9/24 | 5962k | Choose a server​

:ar:Remove any Asus Software/Utility as they're known to cause BSOD.

c:\program files (x86)\asus\ai suite ii\

Update (not so much of an update at this point in time) your RAID drivers:

R1.17.63WHQL (05/26/2011)
1. Fix issue:

a. OS may get BSOD with "System - Common Scenario Stress" test when Boot Device is not connected to 36X controller and other Disk/CD-Rom is connected. - Caused by AHCI Controller may receive D2H FIS and DMA to invalid address during Disable/Enable tests. - Modify driver to disable receiving FIS function before DMA addresses are properly initialized.

b. [#1302] "SCSI Compliance Test 2.0 (LOGO)" failed with WLK 1.6 snap2 - Modify to conform to SCSI specification and Microsoft provides a filter to ignore "ASSERTION: WRITE (10) Basic Functionality Test" item.

lmvm [U]jraid[/U]
Browse full module list
start             end                 module name
fffff880`00e4a000 fffff880`00e6b000   jraid      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\jraid.sys
    Image name: jraid.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U]Tue Aug 10 12:28:44 2010[/U][/COLOR]

• Driver Reference Table - jraid.sys
• JMB36X_WinDrv_R1.17.63_WHQL.zip

lmvm [U]mv91cons[/U]
Browse full module list
start             end                 module name
fffff880`00e9a000 fffff880`00ea4000   mv91cons   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\mv91cons.sys
    Image name: mv91cons.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=Red][U]Mon Nov 22 09:02:46 2010[/U][/COLOR]

• Driver Reference Table - mv91cons.sys
• P8P67 DELUXE - Motherboards - ASUS
• View attachment 294109

Keep updating.