Windows Randomly Crashing

Well, let me start by saying this is my first post here on your forums.

I have been building and working on computers for several years now, but I have yet run into a situation like this. It is usually obvious, or easily tested for but my latest troubles come from a computer I just built.

I just put together a Conroe E6400 on an ASUS P5B Motherboard with 2 gigs of Corsair DDR2 800, an ATi X1900 XTX, and a Seagate SATA 250gb HDD, SB Live!.

All of this is being powered by an OCZ 600W, SLi Ready PSU.

So now to what has been happening. As the title suggests I am getting random reboots, ever since I built it. It does not happen often, at most so far just twice a day, but it should not be rebooting at all. I ran Memtest 86+ and that passed just fine, I have benched my computer several times, stressing the hardware enough (I think) without it rebooting, but it still does so occasionally.

Just recently I learned how to open the dump files, but I am unable to interperet exactly what they mean. I understand some things, but I cannot pull out the usefull information, or what it might be telling is causing this problem. I will post the first dump, and then bits of information I thought were important (to save space) and maybe you could lead me in the direction on what I should test for, or any driver changes.

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 80544e5d, The address that the exception occurred at
Arg3: 805503bc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!KiRetireDpcList+5f
80544e5d ff ???

TRAP_FRAME: 805503bc -- (.trap ffffffff805503bc)
ErrCode = 00000000
eax=ffdffcd0 ebx=ffdff000 ecx=805015ae edx=8055b4a0 esi=ffdff9c0 edi=8055b0a0
eip=80544e5d esp=80550430 ebp=ffdff980 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiRetireDpcList+0x5f:
80544e5d ff ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 80544d44 to 80544e5d

FAILED_INSTRUCTION_ADDRESS:
nt!KiRetireDpcList+5f
80544e5d ff ???

STACK_TEXT:
80550450 80544d44 00000000 0000000e 00000000 nt!KiRetireDpcList+0x5f
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
80544e5e - nt!KiRetireDpcList+60
[ d1:d9 ]
1 error : !nt (80544e5e)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption

I also have had.

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: rundll32.exe

LAST_CONTROL_TRANSFER: from 805b08c6 to 805af983

and

IRQL_NOT_LESS_OR_EQUAL (a)
READ_ADDRESS: 00000400

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KeWaitForSingleObject+bb
804fac65 803b02 cmp byte ptr [ebx],2

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

Several name the process as WoW.exe, which is from the game I play. That has been lately, before it was various other things, and usually its the KERNEL_MODE_EXCEPTION, but also a IRQL_NOT_LESS_OR_EQUAL (a).

Could it be caused by an overheating CPU?

If you need more information on any of the minidumps, just tell me what to post.

Thank you for taking a look at my troubles,
Mark

 

Hi, Gloomer. Welcome to Windows BBS!

I suggest you follow the instructions in this link.

DebugWiz will provide more detailed information that might be helpful in pinpointing the cause of your BSODs ( "Blue Screens Of Death ").


After you run DebugWiz, have a look at this article:
Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4)


Please let us know how it goes.

Good luck!

 

First off, thanks for the help. So I downloaded that program, and read the article but I am still stuck where I was. When I search up the stop codes, I get vague answers that do not directly point to the cause. Not to mention I have had 3 or 4 different stop codes.

I will list cronologically the debug reports that I have gotten and maybe we can try and figure out a cause.

Aug 25th

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E


PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 80544d44 to 80544e5d


MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

Aug 26th 1st Error

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: rundll32.exe


IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x8E_nt!MiMapViewOfImageSection+5b

Aug 26th 2nd Error


DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe


MODULE_NAME: rdbss

IMAGE_NAME: rdbss.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41108015

Aug 26th 3rd Error

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: WoW.exe

LAST_CONTROL_TRANSFER: from 805449cb to 80544e5d


MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

Aug. 27th

I had an error here, but I changed my drivers after the error and now it cannot open it because of invalid stuff.

Aug 28th First Error


DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: WoW.exe


MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

Aug 28th 2nd Error

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: WoW.exe


MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

Aug 29th 1st Error

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xA

PROCESS_NAME: WoW.exe


MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption


I have not had any today. Now I do see a lot of similarities, DEFAUL_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: WoW.exe
IMAGE_NAME: memory_corruption

But my problem is, that CODE_CORRUPTION has come from more than just WoW.exe or memory_corruption. Memory_corruption has come from more than CODE_CORRUPTION, and all of which have come from different BUGCHK_STR. Sometimes they are the same, but not always.

So unless there are multiple problems, there is one thing causing all of this. First think you would think was fault ram. But I have run Memtest 86+ twice and both times there have been no errors reported.

 

Hi, Gloomer.

I'm sorry to say I am not an expert with BSOD minidump analysis and we don't seem to have BSOD minidump analysis experts around here lately.

However, if you post the entire DebugWiz-generated minidump report for one or two of your crashes, somone might be able to give some guidance on how to proceed. I seem to recall reading posts in the past where the information in the "Followup: MachineOwner" section of the debuglog.txt, including the modules list, has been helpful.


If that doesn't prove successful, your best bet might be to submit a support ticket to Microsoft.

One possible route:

• Preparation Before You Contact Microsoft After Receiving a STOP Message on a Blue Screen
  (EDIT:) If you use this route to send a .ZIP file to them via FTP, perhaps you can zip up all your crash dumps in one .ZIP package for them to analyze.

Another possible route:

• Microsoft Support Services, and select an option to "open" a support request.
  You can use the log file (debuglog.txt) generated to supply the needed information to start your support request.

 

Hi, Gloomer.

Since many of your dumps involve WoW.exe, I Googled WoW.exe and found it's apparently related to the World of Warcraft game.

Therefore, I suspect you might need to see of there are any software updates for your World of Warcraft software and/or try some different graphics card drivers for your particular graphics card to see if that solves your issue.

I have been told by one of our hardware experts here at Windows BBS (mattman) that graphics drivers tend to reach their peak performance for a graphics card one or two versions after the version that shipped with the card. (In other words, the latest drivers are not necessarily the best.)

 

Ahh great, thanks very much. I will check around to see if anyone else has had some driver issues, and try some older ones myself.

 

Hi, Gloomer.

Also, because many of the dumps also involve "memory corruption ", I suggest testing your memory.

• Windows Memory Diagnostic
• Memtest86 - A Stand-alone Memory Diagnostic

Please keep us posted.

 

Wikipedia - Memory corruption errors can be broadly classified into four categories

 

As for memory tests themselves, I have run both those programs for several hours straight and come up with passes every time with both.

I was just talking to a friend of mine and he is having similar BSOD problems, but he has a much different system setup.