Windows 7: Irql bsod

Sabrac · 15 Aug 2011

Had some trouble while turning on my computer today. Luckily, there are some dumps.

FredeGail · 15 Aug 2011

Hello again!

Dump says CPU.

Please, run a stress test with Prime95. It'll test your CPU for problems. I personally suggest that you run it for 6 hours, or if errors appear earlier, you can stop the test and we'll go give you further instructions.

I will also ask you do to all three phrases. You want to run Small FFT Test, Big FFT Test and lastly, Blender.

During the process, monitor your temperatures closely to avoid fatal error.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004fee8f8, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004fee8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031b66f0 fffff800`02eddc59 : fffffa80`04fee8d0 fffffa80`03a81040 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02dbdf57 : fffffa80`04fee8d0 fffff800`02e382b8 fffffa80`03a81040 00000000`00000286 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02d255d5 : fffff800`02e99ae0 00000000`00000001 fffffa80`058e1190 fffffa80`03a81040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02ca2001 : fffff880`0106de00 fffff800`02d255b0 fffffa80`03a81000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`02f32fee : 00000000`00000000 fffffa80`03a81040 00000000`00000080 fffffa80`039f5040 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02c895e6 : fffff880`02f64180 fffffa80`03a81040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`03d06540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Best Regards,
FredeGail

Sabrac · 16 Aug 2011

I forgot to run that CPU test last night, but I'll definitely run it tonight and post back.
Also I have a new minidump here.

FredeGail · 16 Aug 2011

Hello again!

Update DirectX files.

You haven't been updating your DirectX files for a while, you can update it in a couple of clicks provided below.

Download Details - Microsoft Download Center - DirectX End-User Runtime

Code:

*******************************************************************************
*                                                                             *
*                        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: 00000000caf00027, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003e05c05, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f17100
 00000000caf00027 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+2d
fffff880`03e05c05 f0830488ff      lock add dword ptr [rax+rcx*4],0FFFFFFFFh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffd670 -- (.trap 0xfffff88002ffd670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000caf00027 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003e05c05 rsp=fffff88002ffd800 rbp=0000000000000001
 r8=fffffa8003c914e0  r9=0000000000000001 r10=fffffa80050c6bd0
r11=fffff88002ffd978 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+0x2d:
fffff880`03e05c05 f0830488ff      lock add dword ptr [rax+rcx*4],0FFFFFFFFh ds:0001:00000000`caf00027=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ce41e9 to fffff80002ce4c40

STACK_TEXT:  
fffff880`02ffd528 fffff800`02ce41e9 : 00000000`0000000a 00000000`caf00027 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffd530 fffff800`02ce2e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`02ffd670 fffff880`03e05c05 : 00000000`00000001 fffff880`112284a6 fffffa80`0511c000 fffff880`112284a6 : nt!KiPageFault+0x260
fffff880`02ffd800 fffff880`03e0d034 : fffffa80`03ecbdd0 fffff880`1134c0c5 00000000`00000001 fffff880`11285ca1 : dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+0x2d
fffff880`02ffd830 fffff880`03e090ba : fffffa80`000242d3 00000000`00000000 00000001`893238ce fffffa80`00017e70 : dxgmms1!VidSchiCompleteFlipEntry+0x130
fffff880`02ffd8c0 fffff880`03e08ce8 : fffffa80`00000000 fffff880`0000002e fffffa80`00000000 0002fd25`0002fd24 : dxgmms1!VidSchiProcessDpcVSyncCookie+0x262
fffff880`02ffd980 fffff880`03e08c4c : 00000000`00000000 fffffa80`050c6410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880`02ffd9d0 fffff880`11cd31cf : fffffa80`052c5480 fffff880`112788fc 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02ffda20 fffff880`110eb138 : fffffa80`0555a000 fffffa80`0555a000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02ffda50 fffffa80`0555a000 : fffffa80`0555a000 00000000`00000000 00000000`00000000 fffff880`110eb0cb : nvlddmkm+0xce138
fffff880`02ffda58 fffffa80`0555a000 : 00000000`00000000 00000000`00000000 fffff880`110eb0cb fffffa80`0555a000 : 0xfffffa80`0555a000
fffff880`02ffda60 00000000`00000000 : 00000000`00000000 fffff880`110eb0cb fffffa80`0555a000 00000000`00000000 : 0xfffffa80`0555a000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+2d
fffff880`03e05c05 f0830488ff      lock add dword ptr [rax+rcx*4],0FFFFFFFFh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+2d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+2d

BUCKET_ID:  X64_0xD1_dxgmms1!VIDMM_GLOBAL::UnreferencePrimaryAllocation+2d

Followup: MachineOwner

Cheers!
FredeGail

Sabrac · 16 Aug 2011

And yet another BSoD. This time it was a Bad Pool Header.

Also when I went to install the DirectX files it said I have the most up to date version.

Sabrac · 17 Aug 2011

Trying to download Prime95 and the download gets 50% in and the download speed keeps going down until it hits zero kbps. I tried other downloads from other websites and it seems to only do it with this one.
Is there another mirror of it somewhere?

Dave76 · 17 Aug 2011

Your crashes are showing all the signs of RAM issues, post the below information and we can check it.

Which RAM cards are you running now?
Mixing RAM cards with different timings and frequencies can cause issues.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Core Temp for AMD CPU , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Sabrac · 17 Aug 2011

Could it still be the RAM even though I did an overnight MemTest and got no errors?
If it ends up being the RAM, then that's a much cheaper alternative than buying a new CPU, but I wanna be sure I'm replacing the right pieces.
Also I am mixing RAM cards since one is from an old computer. The 2 I removed had gone bad.

Plus, I have a new BSoD dump. APC Mismatch Index. Which I've never seen before.

Sabrac · 17 Aug 2011

Here's the screenshots of my CPU-Z.

Dave76 · 18 Aug 2011

Mixing RAM, manufacturers and size can cause instability.
It will depend on your RAM, motherboard and memory controller.

If memtest86+ passes several times and shows errors one time it means you have RAM issues.
One error over the coarse of several tests means you have a RAM problem.
These can sometimes be solved by adjusting settings.

Post this information in your next post, these are the settings we need to adjust, without this information we can not proceed.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

We can try a couple things to test if we can get them stable.

Counting the RAM slots, #1 being closest to the CPU, put the 2GB RAM card in slot #1, the other two 1GB RAM cards in slot #2 and slot #4.

With the voltage information we can make a few adjustments.

Windows 7: Irql bsod

Irql bsod problems?