Random Bluescreen 0x0000001a

Hi folks. I need some assistance with a blue screen I'm getting on an older computer running W7 Home Premium 32 bit. Grab All files are attached below.

This is a desktop:

• P4 3.0 Northwood
• Asus P4C800-E Deluxe MB
• 3 GB PC3200 DDR SDRAM
• Asus Radeon 9800 Pro APG Video card
• 200GB WD Caviar HDD

This bluescreen occurs while the rig is unattended, usually after running idle all night. It does not occur while using the computer. It does not happen at the same time each day.


I have:

• Run Memtest - 5 passes - all good
• Run dskchk /r - All Good
• Clean/defrag
• Updated Hauppauge Drivers to the most recent.

If you can find something in the reports that will point me in the right direction it would be most appreciated.
TIA

Hi mate, see in Carrona.org, STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

Your crash dump says

Code:

...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, c0402000, 22ff, 22105ff}

Probably caused by : memory_corruption ( nt!MiAllocateWsle+6f )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00005003, The subtype of the bugcheck.
Arg2: c0402000
Arg3: 000022ff
Arg4: 022105ff

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  TS2PS.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 828be422 to 8291a490

STACK_TEXT:  
a3681c34 828be422 0000001a 00005003 c0402000 nt!KeBugCheckEx+0x1e
a3681c68 828b47df c0010c44 84c499b8 00000000 nt!MiAllocateWsle+0x6f
a3681ca8 828a8495 00000001 04311000 00000111 nt!MiResolveDemandZeroFault+0x3cc
a3681d1c 82880a68 00000001 04311000 00000001 nt!MmAccessFault+0x180e
a3681d1c 00fbaac1 00000001 04311000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
043b16c0 00000000 00000000 00000000 00000000 0xfbaac1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAllocateWsle+6f
828be422 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiAllocateWsle+6f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f7f30

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+6f

BUCKET_ID:  0x1a_5003_nt!MiAllocateWsle+6f

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

So, we may go for two things.....
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

RAM - Test with Memtest86+
Run it for at least eight passes. Preferably overnight.

BTW mate, there are some things you should take care of....
BIOS.

Code:

BIOS Version/Date    American Megatrends Inc. 1021.007, 3/16/2005

Audio.

Code:

Name    SoundMAX Integrated Digital Audio
Driver    c:\windows\system32\drivers\smwdm.sys (5.12.1.3630, 564.75 KB (578,304 bytes), 12/4/2011 10:30 AM)

Display.

Code:

Name    RADEON 9800 XT (Microsoft Corporation - WDDM)
Driver    c:\windows\system32\drivers\atikmdag.sys (8.1.1.859, 4.00 MB (4,194,816 bytes), 7/13/2009 6:09 PM)

Network

Code:

Name    [00000007] Intel(R) PRO/1000 CT Network Connection
Driver    c:\windows\system32\drivers\e1g60i32.sys (8.4.1.0, 116.00 KB (118,784 bytes), 7/13/2009 6:02 PM)

Please take care of these, too.

Update the results, when all done, ok?

I hope verifier will get something.

Hey Archie. Thanks so much for taking a look. Very helpful info.

I will run Memtest (again, longer) overnight tonight and Driver Verifier after that, so probably no additional info till Sun or Mon.
After DV crashes the machine, do I generate new reports?
Do you just need the dumps?

As for drivers, I am hamstrung. This machine barely made it over the line with W7 compatibility tool and there are very few W7 drivers offered on the manufacturer's websites. For the video card there is only one driver that works at all (from Windows Update), all others I've tried crash the system immediately or do not work. It may very well be a case as "it is what it is" with a machine this old. I am prepared for that possibility.

However, bluescreens are very new. It has run for over a year without any.
I have been installing and uninstalling PVR programs, doing a cleanup and system restore after each disappointing candidate. I suspect that I screwed something up doing this. I am braced for the clean install (from an image).

Let me know what you think!

EDIT: Just checked. The last stable BIOS offered for the MB was 1023 dated 2005.07.05. It adds support for mobile processors (?). BIOS 1022 adds a multiplier for a Dothan CPU. The last OS listed is Windows 2003.
We are talking old here man!

I can understand about the machine, mate :)

If DV cause ant crash, just collect those and upload those. Hoping there will be a way :)

OK, Memtest 86+ ran 8 passes - no errors.

I ran Driver Verifier. It didn't take long.
Bluescreen - Stop 0x000000c4 - portcls.sys

I selected a couple drivers I suspected might be a problem and ran those individually. They were OK.

I also ran my special hard drive torture test: 5 AV and anti-malware scans at once. No problem.

New Grabs below. Hope this helps.

Here it is, mate!

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 1c0, 820f9d40, 90fecd92}

*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*** WARNING: Unable to verify timestamp for aeaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for aeaudio.sys
Probably caused by : smwdm.sys ( smwdm+2d1fb )

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

smwdm.sys is SoundMAX Integrated Digital Audio driver, is to be updated from Analog Devices | Semiconductors and Signal Processing ICs.

aeaudio.sys is Andrea Electronics Corp Audio Noise Cancellation Driver, is to be updated from http://www.andreaelectronics.com/software.html

So do it at first, and see if it changes anything there. OK ? :)

Arrgggh!

Tried changing Soundmax driver. v 6.10.02.6585. Sound doesn't work. Tried another, only get one channel sound. Only that original driver works (for sound).

Looks like I'm a goner. I guess I could try and track down why the sound driver is kicking in at 7AM in the morning with no one using the PC.

TVeblen said:

Arrgggh!

Tried changing Soundmax driver. v 6.10.02.6585. Sound doesn't work. Tried another, only get one channel sound. Only that original driver works (for sound).

Looks like I'm a goner. I guess I could try and track down why the sound driver is kicking in at 7AM in the morning with no one using the PC.

Can you change the sound card?

That is a good idea.
I could add a sound card. The P4C800-E MB has on board sound. That is the Analog Devices High Definition Audio chip (AD1985) using the Soundmax driver.

If it is the audio driver that is causing this crash, would a good test be to disable it in Device Manager and run it like that for a while?
If it crashes again with the audio device disabled could that mean there is another problem too?
If there is another problem then if I disable the audio and then re-run Driver Verifier will DV skip over smwdm.sys, to see if there is an additional faulting driver?

Nicely thought. Disable the drivers ... and run the computer.

But then it may crash on any other driver, as the system is old ... and its drivers

And, continuation with the driver verifier is also a very nice idea. Let the verifier ve there, and identify all the problem drivers.