Multiple Win7 Pro BSOD's (0x1000007e, 0x00000024, 0x0000001e, ...)

[zigzag3143]

Here are the logs (attached). Just as FYI, this morning my system was frozen again.

Several missing components.

First your Intel network connector (see below) is causing havoc. I woudl re-install it with the newest version available.


Log Name: System
Source: e1cexpress
Date: 2/20/2012 2:53:36 PM
Event ID: 27
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: foreigner
Description:
The description for Event ID 27 from source e1cexpress cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Intel(R) 82579LM Gigabit Network Connection

 

[pichogve]

If you remember, I reinstalled my OS on 2/20 around the time of that message you posted. It is very possible that message was logged before or while I was just installing the Intel drivers for my adapter. Also, I was not using that particular adapter, the Intel(R) 82579LM Gigabit Network Connection is the MB integrated adapter, and I was using a PCIE Intel PRO 1000 PT Server adapter for my network connection.

In any rate, this is what I did to try and narrow down my issue further, I physically took my PCIE network adapter out of my system, and now I am only using the integrated one.

I also uninstalled the Intel LAN drivers and reinstalled again.

Thanks again for your help.

 

[ickymay]

I don't want to step on zigzag3143 toes as it looks like your going through a process of elimination here but if you start to run out of ideas can i suggest have we gone down the route of checking voltages and timing's on your RAM ?

I cant help feeling the crashes seem to be quite random and vary across different drivers but could possibly be caused by memory thats very close to its tolerances and occasionally generates errors that are enough to make the system fall over ?

If you do decide to try eliminating ram from the process maybe take all sticks out but one and see if you can get your system to crash ?

 

[pichogve]

Hi ickymay, at this point I am willing to try anything. I am posting here screenshots from CPU-Z to show my timings and speeds.

View attachment 200012

View attachment 200013

View attachment 200014

View attachment 200015

View attachment 200016

View attachment 200017

View attachment 200018

View attachment 200019

View attachment 200020

 

[pichogve]

I have been running my system for 3 days now with no crashes nor freezes I am still running in a minimum configuration (no GPU and no HDD's). I will let it run for a couple more days and then I will try putting my GPU in again.

 

[pichogve]

It was just too good to be true I guess, I haven't had anymore crashes (BSOD's) since I remove my GPU from my system, but my system is still freezing, this morning it was frozen again.

 

[JMH]

Have you checked in Event Viewer { Application} to see what Source & ID is recorded at the time of the freeze?

 

[pichogve]

The only Error I see on the Event Viewer under Application, before the system froze is this one:

Log Name: Application
Source: SideBySide
Date: 2/28/2012 12:30:21 AM
Event ID: 72
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: foreigner
Description:
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SideBySide" />
<EventID Qualifiers="49409">72</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-02-28T05:30:21.000000000Z" />
<EventRecordID>2681</EventRecordID>
<Channel>Application</Channel>
<Computer>foreigner</Computer>
<Security />
</System>
<EventData>
<Data>imaging</Data>
<Data>urn:schemas-microsoft-com:asm.v1^assembly</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>c:\program files\microsoft security client\MSESysprep.dll</Data>
<Data>c:\program files\microsoft security client\MSESysprep.dll</Data>
<Data>10</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

And that event occurred at 12:30:21 AM, and I know the system froze sometime between 4AM and 8AM.

 

[pichogve]

I have gone 6 days without a crash nor freeze, using just one memory stick. Now I am going to add a second stick and see what happens.

 

[ickymay]

I have gone 6 days without a crash nor freeze, using just one memory stick. Now I am going to add a second stick and see what happens.

I keep seeing this problem on Asus motherboards and I think your testing is about to verify this is the same ?

The first thing to do is update your BIOS ASUS P8Z68-V Pro (with latest BIOS v1101) ??

there is a newer version

Version 3203
Description P8Z68-V-PRO BIOS 3203
1.Improve system stability.

2.Improve memory compatibility.

The timings and voltages are correct for one memory stick but when you add another it slightly alters the timings and or voltage sufficiently to generate errors that make the system "fall over" and or bluescreen ?

Important to remember that a Bluescreen is actually windows trying to protect itself from corruption so its not necessarily fatal but it is a warning that theres a major problem that needs to be resolved ?

In my personal experience if the BIOS update doesn't solve the problem and swapping sticks and slots around makes no difference proving both sticks are presumed working ok on their own there are two cost effective options left to solve the problem.

I notice your ram is not in the manufacturer QVL View attachment 201699 list

• the first is manually set your voltage to find something stable which can work with patience ?
  
• replace the memory with something taken from the QVL ?

try these ideas in sequence one by one plz and let us know how its going

 

[pichogve]

Hi ickymay, thanks again for your assistance.

I also noticed there was a new BIOS for my motherboard, I updated to the latest one Ver 3203 yesterday. I will keep watching, so far my system has been running for almost 48 hours without crashing / freezing. In the past I never went more than 3-4 days without a crash/freeze, so I will keep monitoring for a few more days and see what happens.

About my memory not being in the QVL, you are technically correct, although ASUS does list in the QVL the 8GB kit (2 x 4GB) version of the RAM I have, the 16GB kit I have is the exact same RAM but it has 4 sticks instead of just 2.

 

[ickymay]

Hi ickymay, thanks again for your assistance.

I also noticed there was a new BIOS for my motherboard, I updated to the latest one Ver 3203 yesterday. I will keep watching, so far my system has been running for almost 48 hours without crashing / freezing. In the past I never went more than 3-4 days without a crash/freeze, so I will keep monitoring for a few more days and see what happens.

About my memory not being in the QVL, you are technically correct, although ASUS does list in the QVL the 8GB kit (2 x 4GB) version of the RAM I have, the 16GB kit I have is the exact same RAM but it has 4 sticks instead of just 2.

Is that still running with just a single stick ?

BTW we havent finished yet

 

[pichogve]

No, I have been running with two sticks for almost 3 days now with no crashes/freezes.

 

[ickymay]

No, I have been running with two sticks for almost 3 days now with no crashes/freezes.

so the new bios has maybe solved it ?

If it was me then my next step would be to download and install CPUID HW monitor

then downnload and run Prime95

then take a note of your voltages and temperatures for CPU and chipset at idle then run prime95 for 15 -20 minutes and see if if any of the cores generate errors ?

If they do plz post a screen shot of the error message here ?

 

[pichogve]

I don't know for sure yet if the BIOS solved the issue, I am still not at the same RAM configuration I had when I had the last freeze, which was 4 sticks (16 GB of RAM). Today is going to be 5 days running with 2 sticks and so far no crashes / freezes.

Here is the sequence I have been following:

1. With previous BIOS (v 1101) and 4 RAM sticks (system froze after 3 days running).
2. With previous BIOS (v 1101) and 1 RAM stick, system ran for 6 days without freezing nor crashing, during this time I also let Prime 95 run for 24 hours with no errors reported.
3. With new BIOS (v 3203) and 2 RAM sticks, system has been running for almost 5 days now without freezing nor crashing, during this time I also ran Prime 95 for 24 hours with no errors reported.
4. Next step is going to be, to install all 4 RAM sticks now that I have the new BIOS (v 3203) and see what happens, I am also going to run Prime 95 for full 24 hours to see what happens.

And after I install all my RAM and if my system is still stable for a week or so, than I will continue adding back the rest of my hardware (GPU and hard drives) one at the time.

 

[ickymay]

I don't know for sure yet if the BIOS solved the issue, I am still not at the same RAM configuration I had when I had the last freeze, which was 4 sticks (16 GB of RAM). Today is going to be 5 days running with 2 sticks and so far no crashes / freezes.

Here is the sequence I have been following:

1. With previous BIOS (v 1101) and 4 RAM sticks (system froze after 3 days running).
2. With previous BIOS (v 1101) and 1 RAM stick, system ran for 6 days without freezing nor crashing, during this time I also let Prime 95 run for 24 hours with no errors reported.
3. With new BIOS (v 3203) and 2 RAM sticks, system has been running for almost 5 days now without freezing nor crashing, during this time I also ran Prime 95 for 24 hours with no errors reported.
4. Next step is going to be, to install all 4 RAM sticks now that I have the new BIOS (v 3203) and see what happens, I am also going to run Prime 95 for full 24 hours to see what happens.

And after I install all my RAM and if my system is still stable for a week or so, than I will continue adding back the rest of my hardware (GPU and hard drives) one at the time.

If your going to get errors with Prime95 its normally within the first ten minutes so 24 hours is rarely necessary or of any use unless your testing your cooling environment

make the jump to fitting all sticks of Ram and run Prime95 for twenty minutes and if no errors I would start putting components back in

 

[pichogve]

Here is an update, yesterday morning I installed all 4 RAM sticks in my system, ran Prime95 for a couple of hours (just to be sure), it ran with no errors.

But, this morning my system froze again.

 

[MiguelOne]

Hi pichogve!

How's your system been doing since your last post?

I would be interested to know whether you solved the problem since I've got a very similar system (same CPU, same RAM, P8z68-deluxe motherboard, nVidia GPU) and apparently similar problems (BOSD, freeze), although I haven't thoroughly checked my minidump files yet.

 

[pichogve]

Hi pichogve!

How's your system been doing since your last post?

I would be interested to know whether you solved the problem since I've got a very similar system (same CPU, same RAM, P8z68-deluxe motherboard, nVidia GPU) and apparently similar problems (BOSD, freeze), although I haven't thoroughly checked my minidump files yet.

My system is still having problems, I am at the point where I am thinking about buying new components (at least MB, video adapter and power supply).

The latest attempt I made to solve my problem was to change my RAM from DDR3 1600 to DDR3 1333 (still using all my 16 GB of RAM), and I also reconnected all my hardware components to my system (all the RAM and all my disk drives), after that my system was stable.

After running my system that way for about a week with no crashes I started reinstalling all my software and at one point I started seeing crashes again, so right now I have uninstalled all software I installed to find out which one is causing crashes. My next step is to start one piece of software at the time to find out which one is causing crashes.

 

[ickymay]

Hi pichogve!

How's your system been doing since your last post?

I would be interested to know whether you solved the problem since I've got a very similar system (same CPU, same RAM, P8z68-deluxe motherboard, nVidia GPU) and apparently similar problems (BOSD, freeze), although I haven't thoroughly checked my minidump files yet.

My system is still having problems, I am at the point where I am thinking about buying new components (at least MB, video adapter and power supply).

The latest attempt I made to solve my problem was to change my RAM from DDR3 1600 to DDR3 1333 (still using all my 16 GB of RAM), and I also reconnected all my hardware components to my system (all the RAM and all my disk drives), after that my system was stable.

After running my system that way for about a week with no crashes I started reinstalling all my software and at one point I started seeing crashes again, so right now I have uninstalled all software I installed to find out which one is causing crashes. My next step is to start one piece of software at the time to find out which one is causing crashes.

So the common factor for producing crash/freeze is when you install 4 sticks of ram ?

If you can confirm this it would suggest that the Bios is not setting the correct timings and or voltages for the Ram when using four sticks ?

What happens is that with one stick of Ram can work perfectly then as you add another stick it alters the timing slightly and will produce an allowable error then with another stick timings change again and it will produce too many errors and you get a system freeze ?

If you can confirm its ok with one stick then freezes with 2 or more then you can sometimes get past this problem by manually bumping the voltage very slightly ?