Windows 7 - BSOD's (IRQL, Bad Pool and many more)

**Tews** · 07-31-2010

+1 .... Spot on as usual!

**zigzag3143** · 07-31-2010

Quote: Originally Posted by Tews

+1 .... Spot on as usual!

Thanks. Its the Kona talking.

**yooz3r** · 07-31-2010

Hey, thank you for wasting your time on my problem I really apreciate it.
Answering to your post:

ctac32k.sys is creative soundblaster x-fi driver and it's downloaded from creative website, they say Release date : 16 cze 10 - but it uses as we see some old core and I couldn't find any newer.

ATK0110, ASACPI.sys is also the most up to date I could find on internet and it's downloaded from asus website.

About next file I found this information:
Spldr.sys with description loader for security processor is a driver file from company Microsoft Corporation belonging to product Microsoft® Windows® Operating System.

amdxata.sys can't find any update for this file.

I forgot to mention about USBPORT.sys I solved that one with removing a digital sign chipset card from usb.
SFC /SCANNOW passed 100% without errors.

I run Prime95 on Blend torture test it stress a lot of ram and I get errors on 2 cores.
I will run memtest again tonight on all sticks together. Strange because I had errors on other ddr3 rams. I tried to puting sticks in different slots even not as manufacturer says.
So this can be faulty motherboard? or CPU?

As usual, OC is off everything is on default I tried Auto too before.
I'm not running RAID on my disks.

BSOD from 3 hours ago:

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c3fc1d88, 0, fffff960001b5693, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!ValidateTimerCallback+73 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c3fc1d88, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960001b5693, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetUlongFromAddress: unable to read from fffff800030c10e0
 fffff900c3fc1d88 

FAULTING_IP: 
win32k!ValidateTimerCallback+73
fffff960`001b5693 48399058010000   cmp     [rax+0x158],rdx

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_BETA2

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f08832 to fffff80002e89600

STACK_TEXT:  
fffff880`079488c8 fffff800`02f08832 : 00000000`00000050 fffff900`c3fc1d88 00000000`00000000 fffff880`07948a30 : nt!KeBugCheckEx
fffff880`079488d0 fffff800`02e876ee : 00000000`00000000 fffff900`c234e5f0 fffff880`07948a00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x40f00
fffff880`07948a30 fffff960`001b5693 : 00000000`00000000 fffffa80`05550b60 fffff880`07948ca0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07948bc0 fffff960`001b54e7 : 00000001`4004e5a0 000000c1`0199bd8c 00000000`00000212 00000000`00000005 : win32k!ValidateTimerCallback+0x73
fffff880`07948bf0 fffff800`02e88853 : fffffa80`05550b60 00000000`02000002 00000000`00000020 00000000`00000020 : win32k!NtUserValidateTimerCallback+0x27
fffff880`07948c20 00000000`771abeca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012fd78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771abeca


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
win32k!ValidateTimerCallback+73
fffff960`001b5693 48399058010000   cmp     [rax+0x158],rdx

FAULTING_SOURCE_CODE:  


SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  win32k!ValidateTimerCallback+73

MODULE_NAME:  win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

FAILURE_BUCKET_ID:  X64_0x50_win32k!ValidateTimerCallback+73

BUCKET_ID:  X64_0x50_win32k!ValidateTimerCallback+73

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

**Jonathan_King** · 07-31-2010

I suspect a bad CPU. Is it still under warranty? If not, I suggest taking it into the computer shop and let them figure out whether it is a CPU or Mobo problem.

**yooz3r** · 07-31-2010

yes it's still on warranty I bought it together with mobo in same shop so I might send it there and hope they will replace the bad one ;d

EDIT: Just got another BSOD I will go tomorrow to a computer service with mobo and cpu.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C5, {fffff8000104cdc8, 2, 0, fffff80002ff18ed}

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+51d )

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

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: fffff8000104cdc8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002ff18ed, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  0

FAULTING_IP: 
nt!ExAllocatePoolWithTag+51d
fffff800`02ff18ed 4c8b4908         mov     r9,[rcx+0x8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_BETA2

LAST_CONTROL_TRANSFER:  from fffff80002ecb13a to fffff88003e887f2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`02ecb13a : 00000000`ffffffed fffffa80`0560a778 fffff800`03045c40 00000000`00000001 : 0xfffff880`03e887f2
fffff800`00b9cca0 fffff800`02ec5dcc : fffff800`03037e80 fffff800`00000000 00000000`00000000 fffff880`040ae52c : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!ExAllocatePoolWithTag+51d
fffff800`02ff18ed 4c8b4908         mov     r9,[rcx+0x8]

FAULTING_SOURCE_CODE:  


FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!ExAllocatePoolWithTag+51d

MODULE_NAME:  nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xC5_2_nt!ExAllocatePoolWithTag+51d

BUCKET_ID:  X64_0xC5_2_nt!ExAllocatePoolWithTag+51d

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

**yooz3r** · 08-01-2010

I will let everyone know when I solve this problem ;p

**yooz3r** · 09-07-2010

Motherboard, CPU and Memory DDR3 came back from my friend computer service all tests were good without single crash (3dmark, prime95, everest, furmark), it was ok for 5 days and now I get crashes again mostly by playing a game like Starcraft2... I'm so frustrated that I cannot solve this so much time and I'm starting to think that the problem is in a system

I got new graphic card even and still bsod's everytime different, though I solved this problem with disabling the hdmi audio on gfx and was ok for 2 days than again BSOD ... Please HELP ;/

**Jonathan_King** · 09-07-2010

Well no matter what the chop said, we still need to account for the RAM errors.

I don't know if you ever got around to testing all sticks together, but that is important. I am assuming you already have a USB drive/CD with Memtest prepared, so skip directly to Part 2: RAM - Test with Memtest86+

Hopefully you can diagnose a RAM, motherboard, or compatibility/speed issue.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:49:29.581 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:45.001
BugCheck A, {2000050, 2, 0, fffff80002a9c4ef}
Probably caused by : memory_corruption ( nt!MiCheckControlArea+17f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 17:16:44.876 2010 (UTC - 4:00)
System Uptime: 0 days 11:09:03.671
BugCheck 10D, {7, 57ff8bdabf8, fffffa8007425400, fffffa80071e8010}
Probably caused by : Wdf01000.sys ( Wdf01000!FxObject::~FxObject+1e8 )
BUGCHECK_STR:  0x10D_7
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 17:32:39.205 2010 (UTC - 4:00)
System Uptime: 0 days 2:12:10.625
BugCheck A, {fffffa8061be587b, 2, 0, fffff80002a96895}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+265 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 10:16:54.077 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:47.872
BugCheck 1000007E, {ffffffffc0000005, fffff88003e31ca9, fffff88003aba5d8, fffff88003ab9e40}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+31 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 10:08:15.391 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:21.811
BugCheck A, {fffffa80618c4030, 2, 1, fffff80002af0f9e}
Probably caused by : memory_corruption ( nt!MiRemoveAnyPage+13e )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 09:57:11.867 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:13.287
BugCheck 24, {1904fb, fffff88002f9a6e8, fffff88002f99f50, fffff80002a5a5b9}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+10c )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep  4 09:55:15.789 2010 (UTC - 4:00)
System Uptime: 0 days 0:13:58.584
BugCheck 1A, {41201, fffff680001c8bb0, 98c000008b597847, fffffa8003e68db0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

**amandeepmail** · 10-07-2010

Hi, I have a similar problem and I have been trouble shooting for 2 weeks. I finally found out that it was my Nvidia VGA Card (8800GTX).

You can do one thing- Disable your Nvidia driver and use VGA driver and see if this helps. My BSODs were gone when I used VGA driver to check. You can use VGA driver and also setup Driver Verifier to speed up process. If you don't get any BSODs with Nvidia Driver unsinstalled and Driver Verifier on then you know the problem.

**yooz3r** · 10-07-2010

PROBLEM SOLVED:
I found hardware that was making those failures and it was my CPU - it got replaced and everything is fine now.

Thanx all for help even when it was a bit far from solving my problem

Windows 7 - BSOD's (IRQL, Bad Pool and many more)

BSOD's (IRQL, Bad Pool and many more) problems?