BSOD On Startup error 0x0000001a

[LarryB]

Hi all,

I am getting various BSOD error codes, the most recent error code in the subject line

I have used windbg to analyse the latest mini dump file and it tells me that it is a Vista driver error.

The other memory dumps gave memory_managemnt errors in the bsod

I have 2 X 2Gb of RAM. Earlier I have tested each memory stick in each slot and ran a diagnostic test on each change followed by a diagnostic check on the two of them and there are no issues-

Last week I reinstalled and activated my windows 7 home premium sp1, and it is fully updated

Can you help me diagnose my problem please.

I have attached minidumps from today

Thanks

 

[LarryB]

UPDATE:

I have just flashed the BIOS from v2.03 to v3.10 on my Acer Aspire 5732z

No BSOD's on startup however i have been working with the laptop over the last few hours. The BSOD usually occur if I leave the laptop cold for a few days

Any info on the mini dumps would.be much apprecited

 

[axe0]

Hi LarryB,

Please read BSOD Posting Instructions

Have you performed the built-in diagnostic test for the memory?

 

[LarryB]

Hi Axe0

I performed the memory test by launching mdsched.exe then restarting. Very l9ng process as it was tested with 2 sticks inserted then again with each single stick in each slot. Finally got through it and past with flying colours.

I read posts on memtest86 but i had nothing to flash it to! I'll bring home a usb key tonight and test it again x 8 .

I've read your link and i'll attach those details later also

Cheers!

 

[axe0]

Hi Axe0

I performed the memory test by launching mdsched.exe then restarting. Very l9ng process as it was tested with 2 sticks inserted then again with each single stick in each slot. Finally got through it and past with flying colours.

I read posts on memtest86 but i had nothing to flash it to! I'll bring home a usb key tonight and test it again x 8 .

I've read your link and i'll attach those details later also

Cheers!

That is the built-in memory test, this test is not as good as MemTest86+

 

[LarryB]

Coolaboola Axe0 coolaboola!! I'll get those details and tests done later and i'll post up.

Cheers

 

[LarryB]

Log collector files attached to the opening thread. Note that you will see one dump file from the 24/09/2015.

The time and date settings were lost when I powered up yesterday so you will see multiple dump files from 12/04/2011 . These are in fact dump files from yesterday

I will start the memtest86 testing shortly

Cheers

 

[axe0]

There are all sorts of crashes.

The most recent is a 0x1a that indicates memory problems.
There are some dumps that might indicate to a failing hard drive
Please uninstall AVG as a test using the uninstall instructions

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. ]MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8a947248, The address that the exception occurred at
Arg3: 8cc13900, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

FAULTING_IP: 
ataport!IdePortTranslateSrbToCrb+38
8a947248 741f            je      ataport!IdePortTranslateSrbToCrb+0x59 (8a947269)

TRAP_FRAME:  8cc13900 -- (.trap 0xffffffff8cc13900)
ErrCode = 00000000
eax=00000000 ebx=86114f00 ecx=85c1f0e8 edx=85c1f430 esi=861140b4 edi=85c1f0e8
eip=8a947248 esp=8cc13974 ebp=8cc1397c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
ataport!IdePortTranslateSrbToCrb+0x38:
8a947248 741f            je      ataport!IdePortTranslateSrbToCrb+0x59 (8a947269) [br=1]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

[COLOR="Red"]PROCESS_NAME:  avgcsrvx.exe[/COLOR]

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from 8a948f9c to 8a947248

 

[LarryB]

Thank you Axe0 for you time and input

Memtest86+ is running but I am sure you are aware this will take a while. More then likely it will run through the night.

1 pass so far and only 44% through the second test

I'll run a test on the HDD once it completes

As for AVG I removed that and installed Avast. I'll check again to ensure there is nothing left behind as program file / user profile and in the registry.

I'll report back once all tests are complete

Cheers

 

[axe0]

You're welcome

Let me know how it goes

 

[LarryB]

Hi Axe0,

Just to let you know MemTest86+ completed 9 tests successfully with no errors
I got around to completing the 5 tests available on Seagate Tools and they also passed with no issues
Chkdsk completed successfully and no errors found after a restart

As for AVG, Using the uninstall tools on their site, I still found references to AVG in the user profile \appdata directory, and also in the user registry. Those folders were deleted so as far as I am concerned AVG is compltely stripped from this laptop

So, after all of the tests no further blue screens occurred. The laptop was left powered off a number of times over the weekend and there were no blue screens on startup

The only significant change that was made was the BIOS upgrade. However as mentioned before these BSOD´s usually occur if the laptop is left off or cold for a few days. So lets see how it goes and I´ll report back next week

Thanks again for the help and pointers in diagnosing problems. I´ll keep these tools and your suggestions handy.

Cheers

 

[axe0]

You're welcome, glad I could help

 

[LarryB]

Hi Axe0

Unfortunately I am back to square 1. The laptop was off for a few days and on startup last night immediate black screen followed by a restart. This was over and over until it got that little but further past the Windows splash screen and managed to capture two blue screens, one a memory management

In spite of the tests performed at the weekend I am targetting tha hard disk and memory for replacement. I have a spare hard disk here in work, I think a solid state, and I will rebuild the machine and test. If that fails I´ll purchase memory

If you have thime would you mind reviewing the latest dump files and logs that I collected ' see attached zip in opening thread.

It is odd however that this issue comes about if the laptop is off for a few days. After 1 hour or so working in safe mode with networking the laptop can be restarted and loads in normal mode with no crashes.

Could it be a possible mboard issue rather then the HDD or memory? Hopefully it is one of those three, or else I will just tell my partner that she has magnets in her fingertips and they are causing havoc with her laptop!!!

Cheers

LarryB

 

[axe0]

Please use the tool again and upload the zip file.
I can take a look at the dump files, but I prefer to have updated information about your system in case of anything I miss or could be wrong about because of changes to the system.

 

[LarryB]

never clicked save!

There now

Cheers!

 

[axe0]

Please remove Avast using the uninstall instructions and use Microsoft Security Essentials for now.

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

 

[LarryB]

Removing Avast now, and will install Essentials. Will leave the laptop cold for a few days and power it up at the weekend and see what happens

Quite odd. That is two free but recommended AV´s now that flagged with errors on the laptop

 

[axe0]

That indeed is really odd, my guess is either some driver is not mentioned but messing or you have hardware / dust problems. I would doubt dust, but cannot rule it out yet.

To rule out drivers

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.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
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.

 

[LarryB]

Avast Removed using uninstall instructions. Upon restart of the PC it blue screened immediately. Essentials not on here yet and I am working in safe mode.

Latest log file and dump file collected and attached in opening thread

 

[LarryB]

Just saw your other post. I cleaned out the laptop with air compression a while back but I´ll do it again. I like dismantalling laptops. But I always end up with a screw that I forgot to put in!!!!

Cool. I´ll give it a go but I´ll need to keep this PC in safe mode for a bit and I should be able to get into normal mode to kick off the driver verifier