Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

XP continual BSOD, several stop codes


  • Please log in to reply
3 replies to this topic

#1 rocketronnie

rocketronnie

  • Members
  • 28 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:11:35 PM

Posted 25 January 2010 - 06:43 PM

Hi,

Our other computer is an old Compaq that I should probably retire, but am not quite ready to yet. Its not well though. Its started a spate of BSODs mostly either 0x08E or 0x00A but now also 0x0D1s too. Using my limited talents, a well known search engine (and another computer!) I've gone through and eliminated a few of the obvious things:

hard disk space
corrupt swap file
memory error
tried to disable some of the memory things like caching/shadowing but can't find these in the Compaq BIOS menus

Safe Mode seems stable, but not if I try network support. In the event viewer I saw a few errors for my (Sophos) antivirus and Netgear wireless adapter, so tried taking these out of the startup folder but that didn't help.

As I suggested in the sub-title I'm rapidly running out of talent on this one. Any suggestions ? (i tried to upload some minidumps but I wasn't allowed to)

Thanks
Ronnie.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:35 PM

Posted 25 January 2010 - 07:24 PM

Try following the procedures at Help Diagnosing BSODs And Crashes (BC) - http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

How old is "old Compaq"? What model?

Have you tried a clean install?

Louis

Edited by hamluis, 25 January 2010 - 07:25 PM.


#3 rocketronnie

rocketronnie
  • Topic Starter

  • Members
  • 28 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:11:35 PM

Posted 26 January 2010 - 05:26 PM

Hi,

Its a Compaq Presario C-5365EA delivered around the start of 2002. I know it should probably be in a museum, but its quite useful to have the second machine for surfing or basic word processing on when our new(er) machine is in use. I haven't tried a clean install yet (last resort). After taking the network adapter and sophos update software out of the startup it did finally get a bit more stable today. So much so that I decided to bite the bullet and put SP3 on to see if that helps. It seems to be continuing stable & I have completed all windows updates.

Looking back at the windows update history, it looks like I let it install a number of updates on the day the first crash took place, with two the following day, but it was another 10 days after that (with no more updates) that the continual crashes started.

After reading the info on debugging tools I have looked at the minidumps produced and have pasted a couple here. Most but not all refer to ntoskrnl.exe, with rt61.sys (which I think is the driver for my USB WiFi adapter) causing a couple, and usbport.sys one. That leaves about 15 ntoskrnl.exe ones.

Not had any since yesterday....but I hadn't done anything before they stopped!


Most recent dump report:


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [F:\dumps\Mini012510-12.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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.090804-1412
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Mon Jan 25 21:30:51.500 2010 (GMT+0)
System Uptime: 0 days 0:01:48.093
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {4, 2, 1, f6000000}

Probably caused by : ntoskrnl.exe ( nt!KiDoubleFaultStack+2c30 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f6000000, address which referenced memory

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
+2c30
f6000000 0000 add byte ptr [eax],al

CUSTOMER_CRASH_COUNT: 12

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 80550330 to f6000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80550310 80550330 f67b504e 84fa2000 84fa46c8 0xf6000000
00000000 00000000 00000000 00000000 00000000 nt!KiDoubleFaultStack+0x2c30


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultStack+2c30
80550330 50 push eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiDoubleFaultStack+2c30

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a783efd

FAILURE_BUCKET_ID: 0xD1_nt!KiDoubleFaultStack+2c30

BUCKET_ID: 0xD1_nt!KiDoubleFaultStack+2c30

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


The first one:



Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [F:\dumps\Mini011410-01.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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.090804-1412
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Thu Jan 14 09:36:32.031 2010 (GMT+0)
System Uptime: 1 days 1:45:45.618
Loading Kernel Symbols
...............................................................
............................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {4, 2, 1, f6000000}

Probably caused by : ntoskrnl.exe ( nt!KiDoubleFaultStack+2c30 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f6000000, address which referenced memory

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
+2c30
f6000000 0000 add byte ptr [eax],al

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 80550330 to f6000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
80550310 80550330 f68a004e 8470b000 8470d6c8 0xf6000000
00000000 00000000 00000000 00000000 00000000 nt!KiDoubleFaultStack+0x2c30


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultStack+2c30
80550330 50 push eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiDoubleFaultStack+2c30

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a783efd

FAILURE_BUCKET_ID: 0xD1_nt!KiDoubleFaultStack+2c30

BUCKET_ID: 0xD1_nt!KiDoubleFaultStack+2c30

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

#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:09:35 AM

Posted 26 January 2010 - 05:30 PM

Check your devices in Device Manager (Start > Run > type "devmgmt.msc" (without the quotes) and press Enter). Look for any "!", "?" or "X" symbols.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users