Solved Various BSOD over the last few weeks

[JonniBravo]

Hi

I have always had BSOD at various time and varying degrees happening one a week to once a month. Recently I have started to get BSOD every morning sometime as many as 3 then the system mostly runs without an issue.

When the BSOD occur I could be browsing the internet, looking through files in internet explorer or generally doing nothing. I have never had a BSOD that I remember whilst playing a game apart from round the 11th when I fitted a new GPU and I was having a problem with the new fifa demo which I believe I solved.

When I run driver verifier I get a BSOD which implicates L1C63x64.sys which is Atheros PCI-E driver, I have updated and rolled back this driver and nothing works it crashes constantly. I also get a number of other BSOD mainly memory management. I have done 5 passes with memetest which showed no errors.

I have been everywhere for advice and I cannot seem to get to the bottom of the problem with people stating cpu failure to a simple driver. I suspect there are multiple problems, can anyone help.

I have uploaded the debug file as mentioned in the BSOD instructions and added links to my kernel and mini dump files

mini dumps

https://onedrive.live.com/redir?resid=8D9FDFF7810CC568!105

Kernel Dump

https://onedrive.live.com/redir?resid=8D9FDFF7810CC568!1163&authkey=!ANGy0qnAuASuYCc&ithint=file,rar

 

[HarriePateman]

Hello and Welcome to 7F,

I had taken a look at 3 of your many DMP Files and they are all relating to drivers that need updating

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="blue"]BugCheck 1E[/COLOR], {ffffffffc0000005, fffff801501c87fa, 1, 0}

*** WARNING: Unable to verify timestamp for [COLOR="red"]Soluto.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]Soluto.sys[/COLOR]
Probably caused by : Soluto.sys ( Soluto+57fa )

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="blue"]BugCheck D5[/COLOR], {ffffcf812c1f4fe8, 0, fffff80070f50dbb, 0}

*** WARNING: Unable to verify timestamp for [COLOR="red"]atikmdag.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="red"]atikmdag.sys[/COLOR]

Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+c7dbb )

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Blue"]BugCheck D1[/COLOR], {ffffcf80cdc64f50, 2, 0, fffff801f9fa8101}

*** WARNING: Unable to verify timestamp for [COLOR="red"]L1C63x64.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="red"]L1C63x64.sys[/COLOR]
Probably caused by : L1C63x64.sys ( L1C63x64+7101 )

Followup: MachineOwner
---------

This is going to be along series of posts, but don't worry we will get this sorted for you.

   Tip

Please make sure all your windows updates are complete!

I also noticed that you are on Windows 8.1, we also have a windows 8 forum: Windows 8 Forums
I will someone from over there to come and take a look aswell.

What Drivers need to be updated:

L1C63x64.sys :ar: Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30) Click Here
atikmdag.sys :ar: ATI Video driver Click Here
Soluto.sys :ar: Soluto driver Click Here​

   Note

Please remember this is 3 of your 34 Dump files however some of these errors may be re-occurring

 

[JonniBravo]

The drivers are the latest available I have rolled back Atheros win 8 x64 drivers and it still crashes when using driver verifier.

Also the radeon ati drivers are also the latest.

Soluto has been removed crashed once and I immediately removed it. I have also bought some new ram to arrive tomorrow to test that theory

 

[HarriePateman]

The drivers are the latest available I have rolled back Atheros win 8 x64 drivers and it still crashes when using driver verifier.

Also the radeon ati drivers are also the latest.

Soluto has been removed crashed once and I immediately removed it

Okay, im just going to look at all of your DMP files and see what else could be causing this.

Meanwhile..

   Information

Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

:ar:http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[JonniBravo]

The drivers are the latest available I have rolled back Atheros win 8 x64 drivers and it still crashes when using driver verifier.

Also the radeon ati drivers are also the latest.

Soluto has been removed crashed once and I immediately removed it

Okay, im just going to look at all of your DMP files and see what else could be causing this.

Meanwhile..

   Information

Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

:ar:http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Thank you I appreciate it this really getting me down as I have spent a lot of money on this build recently and I am pulling my hair out at the moment

 

[HarriePateman]

Okay so i just looked at 19 more for you, 9 of them were drivers that were continuing to cause you your BSOD's.

Once you have Run Driver Verifier, and there are no BSOD's then try this however if there is an error please upload the latest DMP so i can analyze that:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]MEMORY_MANAGEMENT [/COLOR]([COLOR="blue"]1a[/COLOR])
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, [COLOR="Blue"]A page table page has been corrupted.[/COLOR] On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000a19be0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Debugging Details:
------------------

As we can see something has corrupted a page table, so there are a few tests i would like you to perform.

Test your RAM modules for possible errors.

:ar: How to Test and Diagnose RAM Issues with Memtest86+​

 

[JonniBravo]

Okay so i just looked at 19 more for you, 9 of them were drivers that were continuing to cause you your BSOD's.

Once you have Run Driver Verifier, and there are no BSOD's then try this however if there is an error please upload the latest DMP so i can analyze that:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
[COLOR=red]MEMORY_MANAGEMENT [/COLOR]([COLOR=blue]1a[/COLOR])
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, [COLOR=blue]A page table page has been corrupted.[/COLOR] On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000a19be0
Arg3: 000000000000ffff
Arg4: 0000000000000000
 
Debugging Details:
------------------

As we can see something has corrupted a page table, so there are a few tests i would like you to perform.

Test your RAM modules for possible errors.

:ar: How to Test and Diagnose RAM Issues with Memtest86+
​

Ok I can test again I did 4-5 passes no errors but a test will obvisouly take an entire evening how many passes would you like me to complete?

 

[HarriePateman]

Okay so i just looked at 19 more for you, 9 of them were drivers that were continuing to cause you your BSOD's.

Once you have Run Driver Verifier, and there are no BSOD's then try this however if there is an error please upload the latest DMP so i can analyze that:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
[COLOR=red]MEMORY_MANAGEMENT [/COLOR]([COLOR=blue]1a[/COLOR])
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, [COLOR=blue]A page table page has been corrupted.[/COLOR] On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000a19be0
Arg3: 000000000000ffff
Arg4: 0000000000000000
 
Debugging Details:
------------------

As we can see something has corrupted a page table, so there are a few tests i would like you to perform.

Test your RAM modules for possible errors.

:ar: How to Test and Diagnose RAM Issues with Memtest86+
​

Ok I can test again I did 4-5 passes no errors but a test will obvisouly take an entire evening how many passes would you like me to complete?

9 passes would be great, this can take up-to 20 Hours. However i would like to sort out the drivers First

 

[JonniBravo]

OK no problems let me know what you would like me to try and I'll put the memtest on overnight

 

[JonniBravo]

OK no problems let me know what you would like me to try and I'll put the memtest on overnight

Do you want me to run driver verifier?

 

[HarriePateman]

OK no problems let me know what you would like me to try and I'll put the memtest on overnight

Do you want me to run driver verifier?

Yes Please, lets sort out the Drivers First as they could be giving us a false DMP.

 

[JonniBravo]

I'm just going to finish tea and I'll get to it thanks harrie, I post when I run it. Do you want the dump file after BSOD

 

[HarriePateman]

I'm just going to finish tea and I'll get to it thanks harrie, I post when I run it. Do you want the dump file after BSOD

That would be perfect

 

[JonniBravo]

I'm just going to finish tea and I'll get to it thanks harrie, I post when I run it. Do you want the dump file after BSOD

That would be perfect

Running now with dump set to kernel

 

[JonniBravo]

OK no problems let me know what you would like me to try and I'll put the memtest on overnight

Do you want me to run driver verifier?

Yes Please, lets sort out the Drivers First as they could be giving us a false DMP.

Found a driver on the motherboard site that seems to have resolved the problem pc has now booted without blue screen and has been running for a few minutes.

I think the driver I originally got from the site may have been re updated by windows causing the blue screen and that maybe why I decided that driver was not working. Any how that's sorted no crashes as yet what do you think I should do next?

 

[JonniBravo]

I'm just going to finish tea and I'll get to it thanks harrie, I post when I run it. Do you want the dump file after BSOD

That would be perfect

Ok after about 10 minutes I got a black screen for aound 10 seconds before the pc rebooted, this one started happening today and I have had two of them not including this one. There are no dumps about this event and here is the event log

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 22/09/2014 18:49:51
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: JARVIS
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>3</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2014-09-22T17:49:51.168249100Z" />
<EventRecordID>11363</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>JARVIS</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">126</Data>
<Data Name="BugcheckParameter1">0xffffffffc00000a1</Data>
<Data Name="BugcheckParameter2">0xfffff8034a1021ac</Data>
<Data Name="BugcheckParameter3">0xffffd001cf577cf0</Data>
<Data Name="BugcheckParameter4">0xffffd001cf577d90</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
</EventData>
</Event>

 

[HarriePateman]

That just tells us that windows did not shutdown properly try the 7F tool again :S

 

[JonniBravo]

That just tells us that windows did not shutdown properly try the 7F tool again :S

Is that dm log collector

 

[JonniBravo]

I am now running verifier with the beta drivers for the GPU R9 290 vapour-x oc

 

[HarriePateman]

I am now running verifier with the beta drivers for the GPU R9 290 vapour-x oc

Brilliant, keep us updated.