Windows 7: BSOD BCCode:1000007e

Tyrandis · 13 Nov 2013

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

Attachment 293541

Attachment 293542

Tyrandis · 13 Nov 2013

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

Attachment 293543

Attachment 293544

YoYo155 · 13 Nov 2013

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:

Quote: Originally Posted by koolkat77

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+

Tip

Pay close attention to part 3 of the tutorial "If you have errors"
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.

Quote: Originally Posted by Arc

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.

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

Quote: Originally Posted by Arc

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 · 14 Nov 2013

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

Attachment 293681

YoYo155 · 15 Nov 2013

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

Tyrandis · 17 Nov 2013

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

Attachment 293932

YoYo155 · 18 Nov 2013

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.

Code:

lmvm RTCore64
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:        Wed May 25 09:39:12 2005

Driver Reference Table - RTCore64.sys

Update any Intel driver using this online utility:

Code:

lmvm e1c62x64
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:        Wed Sep 22 00:34:15 2010

Update the HD Audio driver:

Code:

lmvm RTKVHD64
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:        Tue Nov 02 13:25:59 2010

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,

Srat > type > network connections then press enter > Find the adapter Right-click > Disable.

Code:

lmvm Rt64win7
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:        Wed Feb 16 11:03:57 2011

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

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

Code:

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

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

Quote:

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.

Code:

lmvm jraid
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:        Tue Aug 10 12:28:44 2010

Code:

lmvm mv91cons
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:        Mon Nov 22 09:02:46 2010

Keep updating.