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

Random BSOD's


  • Please log in to reply
3 replies to this topic

#1 jrand

jrand

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia
  • Local time:03:54 AM

Posted 22 December 2008 - 11:05 AM

Okay, so after tackling my previous Malware/trojan infection I'm still having BSOD's. They have occurred for a while (since before the infection). The most frequent STOP messages I get are:

0xF4 (0x03)
-and-
Kernel_Stack_Inpage_Error ... 0x77 (0xC0000185,etc, etc)

These crashes do not generate a Minidump/Memory.dmp file so I can't run the WinDB tool to post the results. They seem to occur whenever the system is stressed (i.e. running VirusScanner and clicking around in Firefox). I've ran Memtest86 on both Corsair RAM modules, together and separate with no errors reported. I did, however, receive an error message on one RAM stick through Windows Memory Diagnostic tool. So, I took that stick out and have been using the stick that showed no errors in either Memory Diagnostic tool. Still receiving BSOD's.

I am running an AMD X2 4200+ 2.21GHz. Currently 1GB of Corsair TWIN2x2048-6400C4PRO, Foxconn C51XEM2AA mobo, w/ a WD SATA HD, GeForce 7900GT. Windows XP SP3

I've double-checked my memory timings and voltage to be as Corsair recommends. I've ran diagnostics on my HD (no errors reported).

In recently running an Ntune performance wizard I received the stop message: IRQL_NOT_LESS_OR_EQUAL ... 0x0A. The memory dump is shown below:


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


Loading Dump File [C:\MemoryDump\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Dec 22 10:24:33.390 2008 (GMT-5)
System Uptime: 0 days 1:40:46.083
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 1c, 1, 80502302}

Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+88 )

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

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

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: 00000004, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80502302, address which referenced memory

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiTimerExpiration+88
80502302 895f04 mov dword ptr [edi+4],ebx

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

TRAP_FRAME: 80551390 -- (.trap 0xffffffff80551390)
ErrCode = 00000002
eax=8055cba8 ebx=8055cba8 ecx=85400568 edx=000000ff esi=00000085 edi=00000000
eip=80502302 esp=80551404 ebp=80551428 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!KiTimerExpiration+0x88:
80502302 895f04 mov dword ptr [edi+4],ebx ds:0023:00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 80502302 to 805446f0

STACK_TEXT:
80551390 80502302 badb0d00 000000ff f75f1d3e nt!KiTrap0E+0x238
80551428 80545e7f 8055c4c0 00000000 0005e785 nt!KiTimerExpiration+0x88
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+88
80502302 895f04 mov dword ptr [edi+4],ebx

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTimerExpiration+88

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9

FAILURE_BUCKET_ID: 0xA_nt!KiTimerExpiration+88

BUCKET_ID: 0xA_nt!KiTimerExpiration+88

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


Sorry for such a verbose post, but I figure the most info I can give in 1 shot, the less we have to converse back and forth about minor missing details I've forgotten to include.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,857 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:54 AM

Posted 22 December 2008 - 11:56 AM

Some info: http://www.instant-registry-fixes.org/fix-...k_inpage_error/

It's been my observation (on my systems) that any number of different BSODs (not the same one every time) may point to a memory problem (or a hard drive problem) or a CMOS battery situation, whereas driver problems seem to result (IIRC) in repetitive error messages.

Louis

Edit: The fact that you had malware issues which may have damaged system or other files...makes it even tougher to troubleshoot, IMO.

When I had varied BSODs on a system, I attempted to do a clean install, in an effort to eliminate the XP install as a suspect. Once I found that I could not even complete the install, I knew that it had to hardware (memory) and further work proved that to be true.

Edited by hamluis, 22 December 2008 - 12:00 PM.


#3 jrand

jrand
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia
  • Local time:03:54 AM

Posted 22 December 2008 - 12:09 PM

Ok, thanks for the advice. I have a backup HD that I'm going to attempt to use and see if the issue keeps happening. If the BSOD's happen on that HD then I'll do a clean install on that HD and verify whether or not it's the OS.

Thanks again.

-Justin

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,857 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:54 AM

Posted 22 December 2008 - 01:21 PM

Keep us posted :thumbsup:.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users