[kkngan]

Hi guys,

I did a search in relative to my error but couldn't find a solution from some of the previous thread with the same error code.




I get the following blue screen message:
Error:

A problem has been detected and windows has been shut down to prevent damage to your computer.

A wait operation,attach process, or yield was attempted from DPC routine.

If this is the first time you’ve seen this stop error screen, restart your computer.If this screen appears again,follow these steps:

Check to make sure any new hardware or software is properly installed.If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue,disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components,restart your computer, press F8 to select Advanced Starup options, and then select safe mode.

Technical information:

*** STOP: 0x000000B8 (0X00000000,0X00000000,0X00000000,0X00000000)

Begninning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.



I've attached my logs from Event Viewer and Minidump. Also, I've reinstalled my video card driver with the latest one available from ATI (my video card is ATI Radeon 9600 series), and upgraded from SP2 to SP3. Note that my problem was around even during SP2.

Please please do assist me. Thanks in advance.

[Rollin' Rog]

Most, but not all are "B8" errors as you have noted (http://msdn.microsoft.com/en-us/library/ms795832.aspx)

However almost all occur in different faulting modules -- which is highly likely to indicate a hardware problem such as faulty ram.

You can try booting up in Safe Mode with networking support and see if they continue. If they do, it is even more evidence of a hardware fault.

In the meantime also test the ram:

Beginners Guides: Diagnosing Bad Memory


Memtest86 - A Stand-alone Memory Diagnostic

[kkngan]

I took out the older ram. Will post back if I experience any more crashes after this (hopefully not).

Thanks for the advice!

[Rollin' Rog]

Good luck -- will knock on wood for ya'

[kkngan]

OK, it crashed again. And the error that stands out the most from eventviewer is ati2mtag.

I googled and found that it's a problem for many people, so I reverted back to CAT 7.6 as mentioned from others. Hopefully this fixes it this time.

[kkngan]

This is the latest one after I fixed my ati2mtag issue.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x00000000, 0xf8904dfc, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini071308-02.dmp.

[avisitor]

Upload the minidump.

[avisitor]

According to the first set of minidumps, the error was with mouclass.sys

[kkngan]

This is my latest set of information.

Question, how do I fix the mouclass.sys from the first set of data? Just update the mouse driver?

[Rollin' Rog]

I looked at the minidumps from 7/13 onward. They were similar to the previous -- mostly B8's in

BugCheck B8, {0, 0, 0, 0}

Probably caused by : ntkrnlpa.exe ( nt!SwapContext+157 )

There were a couple of Non Windows drivers mentioned -- but I do not think they are the root cause.

ntkrnlpa.exe is a memory manager.

I would both run a diagnostic memory test and also run chkdsk /r on the drive

Additionally since these errors seem to involve "delays" of some kind --- I would monitor for overheating.

http://www.almico.com/speedfan.php

Speedfan has a graphical monitor. Look for any rise in temps greater than 30 - 35 c from a cold boot.

The chkdsk log should be available in the Applicationsl Log > Winlogon entry after reboot.

You are not posting "errors" from the log files -- so those uploads are not very helpful. Errors can be individually opened by double clicking them -- and there is a double paper copy icon that can be used to copy the description to the clipboard.

I haven't reviewed the previous minidumps but as I recall mouclass.sys was one of many diffferent drivers that faulted -- indicating an underlying hardware problem.

Overheating really needs to be looked at.

[kkngan]

Hi there,

By diagnostic memory test, you mean the memtest86?

Will run chkdsk /r now and post the log here after that.

Also, I've installed smartfan and will monitor it to give feedback.

Thank you.

[kkngan]

Here's my info after running chkdsk from eventviewer.

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 404 unused index entries from index $SII of file 0x9.
Cleaning up 404 unused index entries from index $SDH of file 0x9.
Cleaning up 404 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

39070048 KB total disk space.
30898912 KB in 95351 files.
55972 KB in 7360 indexes.
0 KB in bad sectors.
693376 KB in use by the system.
65536 KB occupied by the log file.
7421788 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
1855447 allocation units available on disk.

Internal Info:
30 f4 07 00 43 91 01 00 77 27 02 00 00 00 00 00 0...C...w'......
9a 4e 01 00 00 00 00 00 52 08 00 00 00 00 00 00 .N......R.......
be c6 da 0e 00 00 00 00 fe ea 9a 16 01 00 00 00 ................
e4 8f 2b 1a 00 00 00 00 8e f1 ae 62 05 00 00 00 ..+........b....
0a b0 4f 6d 01 00 00 00 06 bc 9e 23 08 00 00 00 ..Om.......#....
99 9e 36 00 00 00 00 00 a0 39 07 00 77 74 01 00 ..6......9..wt..
00 00 00 00 00 80 eb 5d 07 00 00 00 c0 1c 00 00 .......]........

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[Rollin' Rog]

Nothing unusual in the chkdsk log.

Have you done the memory test using Memtest86?

How are things looking with Speedfan? Try to test under load -- video watching, heavy processing, gaming --etc.

[kkngan]

Memtest86 returned no errors.

Speedfan, I'm still monitoring it. Everything is below 50 degrees celcius. Question, does speedfan have a log saved? If not, how would I know the temperature of my PC if I'm playing a game?

Also, so far no crashes after chkdsk yet.

[Rollin' Rog]

Speedfan does have some kind of logging feature under Readings > Configure, but it provides no data that I can make sense of

More useful is the "charts" tab -- just enable the sensor monitors you want to see there -- I think it updates about once a second.