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

pichogve said:

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

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.

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.

Attachment 200012

Attachment 200013

Attachment 200014

Attachment 200015

Attachment 200016

Attachment 200017

Attachment 200018

Attachment 200019

Attachment 200020

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.

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.

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

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.

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.