BSOD only after normal log in (ntoskrnl.exe+735c0)

[axe0]

A driver is trying to write data to the memory, but the memory was not meant for that driver.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: [COLOR="red"]fffffa801f178370, memory referenced[/COLOR]
Arg2: 0000000000000002, IRQL
Arg3: [COLOR="Red"]0000000000000001[/COLOR], bitfield :
	bit 0 : value 0 = read operation, [COLOR="red"]1 = write operation[/COLOR]
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800033402e6, address which referenced memory

The driver causing this is from the Atheros Wifi network adapter.
Please check your manufacturers site for driver updates.

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys

2: kd> lmvm athrx
start             end                 module name
fffff880`050b0000 fffff880`05365000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: [U]athrx.sys[/U]
    Timestamp:        [COLOR="red"][U]Wed Feb 22 07:29:09 2012[/U][/COLOR] (4F448B35)
    CheckSum:         002B0EFE
    ImageSize:        002B5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

We have also that the memory is giving data that was not meant for the driver that requested it.
This could be a 1 time issue as this is only happening once from the 4 times, but I am not too sure about it.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: [COLOR="red"]ffff80001b030430, memory referenced[/COLOR]
Arg2: 0000000000000002, IRQL
Arg3: [COLOR="red"]0000000000000000[/COLOR], bitfield :
	bit 0 : [COLOR="red"]value 0 = read operation[/COLOR], 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000339035f, address which referenced memory

 

[D3C3n50r]

Ok before I do any update could you confirm which is the best option I should take as the official Atheros (UK) website does not have any place to download drivers.

According to Device Manager I currently have

Atheros AR9485WB-EG Wireless Network Adapter
Driver Date: 21/02/2012
Driver Version: 9.2.0.489

There are 3 places I can get a Windows 7 64-bit update from:

1. atheros.cz (Unofficial) Version: 10.0.0.326 - https://www.atheros.cz/atheros-wireless-download.php?chipset=61&system=6
2. pcpitstop.com (Unofficial) Version: 10.0.0.67 - Qualcomm Atheros AR9485WB-EG Wireless Network Adapter Driver Download - PC Pitstop Driver Library
3. sony.co.uk (Same version) Version: 9.2.0.489 - Sony Support

If none of these are good is there a way to disable it and test to see if the BSOD does not appear?

 

[axe0]

I would go to the Atheros.cz site.

You can't disable it, except if you don't want internet.

 

[D3C3n50r]

lol that makes sense xD

 

[D3C3n50r]

Right I updated the driver and then rebooted into Normal mode. BSOD returned.

Couple observations:
- Wireless light stays lit up only in Safe Mode even though I am using ethernet and have it turned off.
- After rebooting Windows it took a while to load up the log-in screen.
- After typing in log-in details the screen stayed black for about a minute before everything else loaded.

Attached latest minidumps awaiting next instructions.

 

[axe0]

McAfee is causing the trouble.
Please update or uninstall McAfee.
If you uninstall McAfee, use Microsoft Security Essentials as alternative.

*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys

 

[D3C3n50r]

Ok uninstalled McAfee and installed Microsoft Security Essentials. BSOD appeared while it was updating.

Will try to update again.

Just out of curiosity can bumping a laptop cause a problem like this? I ask because a couple days before first BSOD I dropped something on table which might have shook the laptop a bit.

 

[axe0]

That mainly depends on how high it was.
To be sure, there are a few tests you could try.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials/433-disk-check.html

Diagnostic test

 GPU TEST

Run Furmark to test your GPU. Furmark tutorial

   Note

Run Furmark for around 30 minutes

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

Diagnostic Test

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

[D3C3n50r]

Ok other than Furmark and Prime95 I was able to run the others without any issues.

SeaTools for Windows:
Short Drive Self Test - Pass
Short Generic Test - Pass
Long Generic Test - Pass

Disk Check (Scan and Automatically Attempt to Fix Errors and Recover Bad Sectors):
0 KB in bad sectors.

FurMark - GPU Stress Test:
Can't run in Safe Mode and BSOD in Normal.

Prime95
Tried to run this in Safe Mode but according to SpeedFan Temp1 was exeeding the amount it should. Can't run in Normal due to BSOD.

Hopefully this rules out physical damage?

 

[axe0]

Not really as the GPU couldn't be tested.

Try removing the GPU drivers and reboot in normal mode, Windows should install the right drivers automatically

 

[D3C3n50r]

Any program I should use to remove or can I just uninstall from Device Manager?

 

[axe0]

You could try DDU

Please uninstall everything of AMD using Display Driver Uninstaller

 

[D3C3n50r]

Ok just uninstalled GPU and rebooted in normal mode. DDU did say it would prevent Windows from auto updating after removal, should I do this manually?

 

[D3C3n50r]

Just checked AMD site and they have a newer driver compared to the one I had but it's in beta.

version 15.10 beta: Mobile

my old one is:

version 8.933.0.0: Sony Support

Go with newer?

 

[axe0]

As you have a laptop, ALWAYS and ONLY get your drivers from your manufacturer.
Your manufacturer is Sony, so only get it from Sony.

 

[D3C3n50r]

Ok I installed the driver and it said everything installed properly. However I can not find it under Display Adpaters and it is not showing in dxdiag either.

Also here's latest dumps:

 

[axe0]

Please check your manufacturer for BIOS updates, it is dating 2012.

 

[D3C3n50r]

That is the latest one according to website:

BIOS - R0240E6

6.33 Mb - 32 / 64 bit
-12-2012

Sony Support

 

[D3C3n50r]

Just checked Sytem Info again and my current one says release date:

R0240E6 16/11/2012

You telling me this is an update?

R0240E6 XX/12/2012

 

[axe0]

Just wanted to make sure the BIOS is up to date

The crashes are write errors, but no driver is flagged.
Please run driver verifier, this in most cases helps to mark the driver(s) causing problems.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: [COLOR="Red"]fffffa801f1a0370, memory referenced[/COLOR]
Arg2: 0000000000000002, IRQL
Arg3: [COLOR="red"]0000000000000001[/COLOR], bitfield :
	bit 0 : value 0 = read operation, [COLOR="red"]1 = write operation[/COLOR]
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800039922e6, address which referenced memory

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.