BSOD again.. computer has been very slow

[jake21]

Hi

My new laptop has been so slow lately..

I just bought this like 4 months earlier.

Specs:

Dual Core

2GB RAM

120GB HD

I attached the .dmp files:

(I renamed them from .dmp to .txt because it won't allow me to upload .dmp files)

Mini100308_01.txt

Mini100708_01.txt

[cluberti]

Mini100308_01.dmp

// The atapi driver is scanning the port for a hard disk to service the work item pending:
0: kd> kb
ChildEBP RetAddr  Args to Child			  
ba50fbb0 80515b72 0000007a c05cf000 c000000e nt!KeBugCheckEx+0x1b
ba50fbe0 805166df 81dbbd30 c05cf000 b9e0050c nt!MiWaitForInPageComplete+0x1ca
ba50fc60 80520239 c05cf000 b9e0050c c05cf000 nt!MiDispatchFault+0x2c1
ba50fccc 80544578 00000008 b9e0050c 00000000 nt!MmAccessFault+0x877
ba50fccc b9e0050c 00000008 b9e0050c 00000000 nt!_KiTrap0E+0xd0
ba50fd54 b9e02e29 8a4fd0e8 8a5bf478 8a4fd030 atapi!IdePortScanBus
ba50fd68 80576ad5 8a4fd030 8a5c1060 8056485c atapi!ChannelQueryBusRelation+0x2f
ba50fd7c 8053876d 8a5bf478 00000000 8a5ad020 nt!IopProcessWorkItem+0x13
ba50fdac 805cff64 8a5bf478 00000000 00000000 nt!ExpWorkerThread+0xef
ba50fddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

// This tells us the PTE that will be used, and the pointer it is looking to gather memory from:
0: kd> .frame 1
01 ba50fbe0 805166df nt!MiWaitForInPageComplete+0x1ca

// The PTE is valid...:
0: kd> dc 0xc05cf000
c05cf000  34354860 00000000 00000060 0000012e  `H54....`.......
c05cf010  0a7ee121 00000000 0a7ef121 00000000  !.~.....!.~.....
c05cf020  0a7f0121 00000000 0a7f1121 00000000  !.......!.......
c05cf030  0a7f2121 00000000 0a7f3963 00000000  !!......c9......
c05cf040  00000000 00000000 00000000 00000000  ................
c05cf050  00000000 00000000 7f523963 00000000  ........c9R.....
c05cf060  7f524121 00000000 7f525121 00000000  !AR.....!QR.....
c05cf070  7f526121 00000000 7f527121 00000000  !aR.....!qR.....

// ...but the contents are either invalid or paged out, thus the page in operation:
0: kd> dc 34354860 L1
34354860  ????????							 ????

// So why did the box bugcheck:
0: kd> .bugcheck
Bugcheck code 0000007A
Arguments c05cf000 c000000e b9e0050c 34354860

0: kd> !error c0000000e
Error code: (Win32) 0xe (14) - Not enough storage is available to complete this operation.

When a machine bugchecks with a 0x7A, and C000000E is the error code, then this means a hard disk subsystem error (usually the hard disk itself, although I've seen bad motherboard controllers cause this in rare occurrances). See this link for the OCA crash bug attached to dumps of this type.

Mini100708_01.dmp

// We crashed talking to the HAL, but this is just a victim of a bad driver, it appears:
1: kd> kb
ChildEBP RetAddr  Args to Child			  
a10f41a0 806ea153 00000cf8 80001090 806f1420 hal!WRITE_PORT_ULONG+0x9
a10f41b4 806e9f0f 806f1420 a10f41d4 a10f4300 hal!HalpPCIWriteUlongType1+0x23
a10f41e8 806ea337 a10f4200 00000002 a10f4300 hal!HalpPCIConfig+0x4d
a10f4208 806eb14d a10f422c 00000002 a10f4300 hal!HalpWritePCIConfig+0x2d
a10f4298 b9e50ae0 00000000 00000000 00000002 hal!HaliPciInterfaceWriteConfig+0x33
a10f42bc b9e50b74 8a5986f8 00000002 a10f4300 pci!PciReadWriteConfigSpace+0x38
a10f42dc b9e50fcc 8a5cb450 a10f4300 00000090 pci!PciWriteDeviceConfig+0x1e
a10f4404 b9e53cbd 8a5cb450 a10f448c 00000090 pci!PciExternalWriteDeviceConfig+0x1ac
a10f4428 b9e5034d 8a5cb450 00000000 a10f448c pci!PciWriteDeviceSpace+0x5d
a10f4448 b8694212 8a5cb450 00000000 a10f448c pci!PciWriteAgpConfig+0x1d
a10f4464 b86b4a11 8a3fe358 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
a10f4498 b86c838d 8a3fe358 000000ea 00000000 igxpmp32+0xda11
a10f44e8 b869435b 8a3fe358 000000ea 8a1b1000 igxpmp32+0x2138d
a10f450c b86a1114 a10f45a4 00000000 8a276b78 VIDEOPRT!pVpGeneralBugcheckHandler+0x61
a10f45cc 804ef18f 89bcc040 88ef7e58 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa
a10f45dc bf85a1ae 00000000 00000000 00000000 nt!IopfCallDriver+0x31
a10f460c bf93c989 89bcc040 0023002c 00000000 win32k!GreDeviceIoControl+0x93
a10f4634 bf9608fa 00000000 a10f468c bf805b86 win32k!DrvPrepareForEARecovery+0x26
a10f4654 bf805b2f e2638008 00000000 00000000 win32k!HandleStuckThreadException+0x24
a10f468c bf8baafd e263a018 e5611a90 00000000 win32k!WatchdogDrvCopyBits+0x77
a10f46d4 bf8ba915 bf805b3a a10f477c e263a018 win32k!OffCopyBits+0x7d
a10f4788 bf8bab4a e263a018 e5611a90 00000000 win32k!SpBitBlt+0xfc
a10f47bc bf80a37e e263a018 e5611a90 00000000 win32k!SpCopyBits+0x27
a10f4850 8054161c e263a008 bf9a5ea8 e1c198f8 win32k!NtGdiBitBlt+0x51c
a10f4850 7c90e4f4 e263a008 bf9a5ea8 e1c198f8 nt!KiFastCallEntry+0xfc
0012e630 00000000 00000000 00000000 00000000 0x7c90e4f4

// Looks like an invalid interface pointer was passed...:
1: kd> .trap 0xffffffffa10f4130
ErrCode = 00000000
eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806f1420 edi=a10f422c
eip=806ecae1 esp=a10f41a4 ebp=a10f41b4 iopl=0		 nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00000286
hal!WRITE_PORT_ULONG+0x9:
806ecae1 c20800		  ret	 8

// ...but checking to be sure...:
1: kd> .bugcheck
Bugcheck code 1000008E
Arguments 80000004 806ecae1 a10f4130 00000000

// ...and it was:
1: kd> !error 80000004
Error code: (HRESULT) 0x80000004 (2147483652) - No such interface supported

// The driver responsible:
1: kd> lmvm igxpmp32
start	end		module name
b86a7000 b8c657a0   igxpmp32 T (no symbols)		   
	Loaded symbol image file: igxpmp32.sys
	Image path: igxpmp32.sys
	Image name: igxpmp32.sys
	Timestamp:		Fri Jun 27 11:46:47 2008 (48650B67)
	CheckSum:		 005C093F
	ImageSize:		005BE7A0
	Translations:	 0000.04b0 0000.04e4 0409.04b0 0409.04e4

I think it's important to note that both of these failures are happening at a low level on the system, so having your hardware checked would probably be your best option at this point. I'm not entirely certain of what's going on, because these two aren't seemingly related - however, the first is complaining about your disk hardware, and the second failed when talking to the system hardware via the HAL (hardware abstraction layer .dll), so making sure the hardware is all kosher is probably a good idea.

[jake21]

Hi

My computer is like crawling lately.. my other computer which has lower specs even runs and boots faster than this..

Win XP SP2

2 GB Ram

Dual Core

120GB Hd

I attached the .dmp file:

Mini102008_01.txt

////edit::

after i made this post.. another bsod came out.

Mini102008_02.txt

Edited October 20, 2008 by jake21

[cluberti]

Did you see my response to your last posts about this? These are similar dumps, with the same crashes as those.

[IcemanND]

Merge two topics together. Please don't start a new topic when you already have one going with the same issue.

[jake21]

I was trying to find that thread I forgot to save it to my computer.. sorry i'm really not a computer savvy guy.

Anyway thansk again for your help.. So the problem could be hardware?

is it the hard drive itself?

but this is just new, what could be the cause?

should reformatting the disk fix this? what step should i take?

had another one: Mini102108_01.txt

i remembered.. i'm diskeeper pro before and disabled it.. could it be that that's causing this?

Edited October 21, 2008 by jake21

[cluberti]

It could be hardware, but I'd start by updating the video driver for certain first. All of the driver-level dumps had the Intel graphics driver working on bus-level imports, so. That'd be the first thing to address.

[jake21]

ok i updated my graphics driver just now.. it's like 3 months old..

but if the problem persists... should i be concerned with the hard disk itself? or reformatting will do the trick?

[cluberti]

ok i updated my graphics driver just now.. it's like 3 months old..

but if the problem persists... should i be concerned with the hard disk itself? or reformatting will do the trick?

It's hard to say, honestly, but I would consider starting with a reformat and reinstall if the problems persist, yes.