Win XP BSOD intermittent during daily use (stop oa)

By donbrownzd
Nov 4, 2010
Post New Reply
  1. Getting constant BSODs in windows xp pro.

    The code is Stop OA, 0x0a 00 11 0c, 0x00 00 00 02, 0x00 00 00 00, 0x80 4d be 7b

    Always an IRQL_NOT_GREATER_OR_EQUAL error. I think it's a buggy driver but I have been unable to figure it out.

    I have not changed any hardware, I'm not overheating (doesn't always happen under a load).

    This error is sometimes extremely persistent on boot (or shortly after the user logon screen) rendering the laptop impossible to use, and sometimes it functions (like now).

    I am attaching some dump logs that were generated as part of error reporting. I hope this will help.

    This is a Compaq Evo N800C.

    Thank You,

    Donbrownzd

    Attached Files:

  2. donbrownzd

    donbrownzd Newcomer, in training Topic Starter

    TSF_XP links if this helps.

    I read some of the other messages on this forum, if this helps, attached is a link to the TSF package that was generated.

    rapidshare.com/files/428894233/TSF_XP_Support.rar (I cannot post links yet)

    Thanks Again,

    Donbrownzd
  3. donbrownzd

    donbrownzd Newcomer, in training Topic Starter

    Locked out of the "normal" boot modes.

    Now, I get a BSOD everytime the Windows splash screen comes up, can't even get to the logon page.

    This is me using the safemode w/networking, which is not completely stable.

    Thanks,

    Donbrownzd
  4. Jonathan King

    Jonathan King Newcomer, in training Posts: 133

    The good news is that the cause is clearly shown. Your Compaq network drivers are most likely the cause. Install these ones:

    ftp://ftp.hp.com/pub/softpaq/sp29001-29500/sp29156.exe

    They are about a month newer than your current ones.

    Symantec might also be taking part in it. Remove it with this tool: ftp://ftp.symantec.com/public/english_us_canada/removal_tools/Norton_Removal_Tool.exe

    Replace it with MSE: www.microsoft.com/Security_Essentials/

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Documents and Settings\JK\Desktop\TSF_XP_Support\Mini110410-27.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.100427-1636
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
    Debug session time: Thu Nov  4 12:19:47.864 2010 (GMT-4)
    System Uptime: 0 days 0:03:59.454
    Loading Kernel Symbols
    ...............................................................
    ......................................................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000000A, {60014, 2, 0, 805338a6}
    
    Unable to load image wlcom51b.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for wlcom51b.sys
    *** ERROR: Module load completed but symbols could not be loaded for wlcom51b.sys
    Probably caused by : wlcom51b.sys ( wlcom51b+69d6 )
    
    Followup: MachineOwner
    ---------
    
  5. donbrownzd

    donbrownzd Newcomer, in training Topic Starter

    driver updates?

    First of all, thanks for your help, your solution has made this system stable enough to post this message.

    I will let it run a day or two straight and see if it continues to behave.

    How did you specifically identify how old/new the drivers were, and how did you find them on the ftp site?

    I was pretty sure I had installed the latest network drivers from the hp support page...

    Thanks,

    Donbrownzd
  6. Jonathan King

    Jonathan King Newcomer, in training Posts: 133

    One way to find the dates of drivers is to use the List Module command in Windbg, and add the t parm, to display timestamps. I use the command lmntsm

    Because you provided us with the jcgriff2 report as well, I could also use the driverq_v file, but I didn't. Actually, my laptop was overheating at the time I posted, so it was crazy slow. As a result, I just used the Modules window in Windbg. You can't copy/paste from there, but at least it was fast, and that's what I needed.

    I got the FTP downloads the same way you did. I went to the HP site, entered your computer model, and went to the downloads page.
  7. donbrownzd

    donbrownzd Newcomer, in training Topic Starter

    Ok, we are at it again... sigh.

    I'm posting the rapidshare upload link:rapidshare.com/files/429215951/TSF_XP_Support.rar

    Still having intermittent issues, however, nowhere near as bad as before (if this helps).

    Thanks,

    Donbrownzd
  8. reventon

    reventon Newcomer, in training

    Hi,

    I notice that one of the other drivers blamed was symsnap.sys - part of Symantec.

    Have you removed it using the removal tool yet? It's drivers are still present in the last dump.

    Regards

    Code:
    Built by: 2600.xpsp_sp3_gdr.100427-1636
    Debug session time: Fri Nov  5 05:19:47.864 2010 (GMT+13)
    System Uptime: 0 days 0:03:59.454
    BugCheck 1000000A, {60014, 2, 0, 805338a6}
    *** WARNING: Unable to verify timestamp for wlcom51b.sys
    *** ERROR: Module load completed but symbols could not be loaded for wlcom51b.sys
    Probably caused by : wlcom51b.sys ( wlcom51b+69d6 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  svchost.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 2600.xpsp_sp3_gdr.100427-1636
    Debug session time: Fri Nov  5 05:15:14.340 2010 (GMT+13)
    System Uptime: 0 days 0:09:30.930
    BugCheck 1000000A, {60014, 2, 0, 805338a6}
    *** WARNING: Unable to verify timestamp for wlcom51b.sys
    *** ERROR: Module load completed but symbols could not be loaded for wlcom51b.sys
    Probably caused by : wlcom51b.sys ( wlcom51b+69d6 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  svchost.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 2600.xpsp_sp3_gdr.100427-1636
    Debug session time: Fri Nov  5 05:04:28.480 2010 (GMT+13)
    System Uptime: 0 days 0:08:07.060
    BugCheck 1000000A, {60014, 2, 0, 805338a6}
    *** WARNING: Unable to verify timestamp for wlcom51b.sys
    *** ERROR: Module load completed but symbols could not be loaded for wlcom51b.sys
    Probably caused by : wlcom51b.sys ( wlcom51b+69d6 )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  msmsgs.exe
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 2600.xpsp_sp3_gdr.100427-1636
    Debug session time: Fri Nov  5 04:24:50.287 2010 (GMT+13)
    System Uptime: 0 days 0:00:39.797
    BugCheck 1000000A, {a00110c, 2, 0, 804dbe7b}
    *** WARNING: Unable to verify timestamp for symsnap.sys
    *** ERROR: Module load completed but symbols could not be loaded for symsnap.sys
    Probably caused by : symsnap.sys ( symsnap+1599b )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
    Built by: 2600.xpsp_sp3_gdr.100427-1636
    Debug session time: Fri Nov  5 04:23:30.148 2010 (GMT+13)
    System Uptime: 0 days 0:00:26.658
    BugCheck 1000000A, {a00110c, 2, 0, 804dbe7b}
    Probably caused by : ntoskrnl.exe ( nt!KiInsertTimerTable+2f )
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  System
    ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  9. donbrownzd

    donbrownzd Newcomer, in training Topic Starter

    Frustration...

    I just removed and reinstalled the Wireless drivers, and in addition verified that Symsnap was removed.

    The computer is still crashing with the same Stop 0A error. Is it possible that the wifi driver is just not compatible with XP SP 3?

    Or am I overlooking something?

    Thanks,

    Donbrownzd
  10. reventon

    reventon Newcomer, in training

    Can you upload the latest minidumps from C:\Windows\Minidump please (you will have to copy them to the desktop before zipping them up)
  11. donbrownzd

    donbrownzd Newcomer, in training Topic Starter

    Totally F*n bizzare....

    On a very outdated thread, somewhere on the net (it came up in google), I found a suggestion that you roll the drivers for the WLAN 200 back to version 1.0 C.

    This is a very very very old driver. So I did. It works fine now, the big difference is, I cannot get maximum throughput on the wireless (not that it's required). Example, went from the maximum of 11mbps to 5mbps. Also, there are no device options other than channel and power management.

    Very strange solution, but it appears to have worked. I'm surprised the later version drivers cause the crash -- or that they are buggy.

    Thanks for the efforts guys, y'all saved me a lot of money and aggravation

    Donbrownzd
     


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.