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

[yooz3r]

Hello I'm looking for some help/advice on what to do with my computer, I'm suffering random BSOD's mostly during a game but it happens browsing websites too.

What I tried?
- Upgraded GTX275 Driver, Soundblaster driver, Asus Motherboard drivers
- Running memtest whole night only at one stick of ram - Passed
- Stressing CPU and ram in Prime95 about 6hours - Passed
- Torture GPU test in Furmark - Passed
- Some stability tests in Everest Ultimate - Passed
- I borrowed another DDR3 and random BSOD occured while browsing.
- Runned driver verifier and last BSOD from 31.07.2010 10:33 I think it's from it during a boot.

What doesn't helped?
- Re-installed OS
- Rising Voltages, Lowering Timings on DDR3
- Running all on auto in BIOS
- Disabling C1E in Bios
- Disabled Realtek built-in audio processor

On usb port's I got:
scanner, printer, keyboard and mouse.

I upgraded this computer half year ago, and bsod's started a month ago.
Please help me, what can it be? CPU? Mobo? Sending motherboard to a service will not help because they will start OS on it... and say that everything is ok.

Might be some driver error cause I did run driver verifier and it BSOD during a boot.

attached bsod's and perfmon report.

Last BSOD:

Microsoft (R) Windows Debugger  Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\073110-19359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Vista Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Sat Jul 31 10:32:44.048 2010 (GMT+2)
System Uptime: 0 days 0:00:19.749
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff80003170a86, 2, 0, fffff80002ef8662}

Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff80003170a86, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002ef8662, address which referenced memory

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


READ_ADDRESS: GetUlongFromAddress: unable to read from fffff800031030e0
 fffff80003170a86 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!RtlDispatchException+122
fffff800`02ef8662 410fb60c24       movzx   ecx,byte ptr [r12]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_BETA2

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff80002ecab69 to fffff80002ecb600

STACK_TEXT:  
fffff880`02fae668 fffff800`02ecab69 : 00000000`0000000a fffff800`03170a86 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fae670 fffff800`02ec97e0 : 00000000`00000000 00000000`0000005a 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fae7b0 fffff800`02ef8662 : fffff800`03170a86 fffff880`02fae988 fffff880`02faf7e8 fffff800`02e5b000 : nt!KiPageFault+0x260
fffff880`02fae940 fffff800`02f058df : fffff880`02faf7e8 fffff880`02faf050 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x122
fffff880`02faf020 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!RtlDispatchException+122
fffff800`02ef8662 410fb60c24       movzx   ecx,byte ptr [r12]

FAULTING_SOURCE_CODE:  


SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!RtlDispatchException+122

MODULE_NAME:  nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!RtlDispatchException+122

BUCKET_ID:  X64_0xA_VRF_nt!RtlDispatchException+122

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

 

[Tews]

Blue Screen of Death (BSOD) Posting Instructions

 

[yooz3r]

I followed instructions that was first Thread I read here, I've read other IRQL and simillar problems but didn't found the solution for me.

 

[Tews]

Looking at them now... may take a few minutes... Have called in a specialist ...

 

[Tews]

Quick question, are you over clocking anything???

 

[swarfega]

This error is usually associated with ram problems. Try with just one stick installed then add 1 each time. Remembering of course to turn your computer off each time you swap out ram.

 

[yooz3r]

I'm not overclocking atm, I tried with 1 stick and still get bsod's I borrowed another ddr3 and problem occured again so I think it's not ram problem (
I have no idea what to do now

This is BSOD from yesterday, dxgmms1.sys I google some problems with it, some guy replaced mobo other one graphic card - as I can see 90% of people had AMD chipset and having this bsod...

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

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8a008482148, 800000012a16c101, fffff8800875c360, b}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a008482148, Virtual address for the attempted write.
Arg2: 800000012a16c101, PTE contents.
Arg3: fffff8800875c360, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_BETA2

BUGCHECK_STR:  0xBE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ef1a22 to fffff80002e71600

STACK_TEXT:  
fffff880`0875c1f8 fffff800`02ef1a22 : 00000000`000000be fffff8a0`08482148 80000001`2a16c101 fffff880`0875c360 : nt!KeBugCheckEx
fffff880`0875c200 fffff800`02e6f6ee : 00000000`00000001 fffffa80`04a3b740 00000000`00000000 fffff880`0433bee3 : nt! ?? ::FNODOBFM::`string'+0x423be
fffff880`0875c360 fffff880`04351507 : fffffa80`04a3b740 fffffa80`04a3b740 fffff8a0`0a295ce0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0875c4f0 fffff880`04337ecc : fffff8a0`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f
fffff880`0875c5c0 fffff880`04279c10 : 00000000`00000000 fffff8a0`0a6bd000 fffff8a0`0a6bd000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0875c5f0 fffff880`0428c67c : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0875c6e0 fffff880`04271815 : 00000000`fffffeda fffff8a0`09ffb710 fffff8a0`0a6bd000 fffffa80`07148000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0875c750 fffff880`042afca6 : 00000000`00000001 fffffa80`07148000 fffff8a0`09ffb710 fffff8a0`09ffb790 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0875c780 fffff880`042af63c : fffff900`c2b5b480 00000000`00000000 00000000`00000001 fffff900`c2b5b480 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0875c830 fffff960`00174aa4 : 00000000`0000126c fffff900`c2b5b480 00000000`00000000 fffff900`c2b5b480 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0875c8c0 fffff960`001741a7 : fffffa80`0723ba00 fffff880`0875cc20 00000000`00000000 fffff880`0875cc20 : win32k!GdiProcessCallout+0x244
fffff880`0875c940 fffff800`03157881 : fffffa80`0723ba60 00000000`00000000 00000000`00000000 fffffa80`041e4060 : win32k!W32pProcessCallout+0x6b
fffff880`0875c970 fffff800`031304d1 : 00000000`20010000 00000000`20010001 fffffa80`78457300 fffffa80`03d98b60 : nt!PspExitThread+0x561
fffff880`0875ca30 fffff800`02e4e0e3 : 00000000`00000100 fffffa80`041e4120 00000000`00000001 fffff800`02e7895d : nt!PsExitSpecialApc+0x1d
fffff880`0875ca60 fffff800`02e4e520 : 00000000`00000000 fffff880`0875cae0 fffff800`031305dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0875cae0 fffff800`02e708f7 : fffffa80`041e4060 00000000`000004d0 00000000`00000000 fffffa80`043de170 : nt!KiInitiateUserApc+0x70
fffff880`0875cc20 00000000`75212dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`1166f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75212dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
fffff880`04351507 488908           mov     [rax],rcx

FAULTING_SOURCE_CODE:  


SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

MODULE_NAME:  dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

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

 

[Jonathan_King]

Try a RAM test just to make sure. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. Be sure to run it with all sticks in at the same time.

It appears your video card or its drivers is the cause. Your drivers are up to date, so I don't suspect them.

Do you have another video card you can test with?

ASACPI.sys should be updated. Please install the latest ATK0110 Utility for Vista/7 from this link: ASUSTeK Computer Inc.-Support-

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 04:32:44.048 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.749
BugCheck A, {fffff80003170a86, 2, 0, fffff80002ef8662}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 04:07:55.526 2010 (UTC - 4:00)
System Uptime: 0 days 0:39:57.211
BugCheck C2, {d, fffffa80044a87d0, 20206f49, fffffa800519b060}
Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
BUGCHECK_STR:  0xc2_d
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 30 12:05:51.856 2010 (UTC - 4:00)
System Uptime: 0 days 3:41:25.541
BugCheck BE, {fffff8a008482148, 800000012a16c101, fffff8800875c360, b}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 14:45:38.367 2010 (UTC - 4:00)
System Uptime: 0 days 0:43:01.052
BugCheck A, {fffffa7f9fffffe0, 2, 1, fffff80002f04209}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 11:55:14.327 2010 (UTC - 4:00)
System Uptime: 0 days 3:16:19.639
BugCheck A, {8, 2, 1, fffff80002ed74b2}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+f2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[yooz3r]

I did run Memtest I write it above in first post each memtest runned whole night on just one stick of ram with no errors at all. I will try tonight with all sticks together, but as I mentioned BSOD happened on borrowed other sticks of Patriot Rams that were in Qualified Vendor List posted by Asus to my motherboard.

Strange I upgraded that ATK0110 yesterday
from Asus website:
Description ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

File Size 119.88 (KBytes) 2009/12/07 update

No I don't have any video card to borrow cause bsod happen randoms sometimes only once a day.

I updated BIOS a week ago.

 

[zigzag3143]

I did run Memtest I write it above in first post each memtest runned whole night on just one stick of ram with no errors at all. I will try tonight with all sticks together, but as I mentioned BSOD happened on borrowed other sticks of Patriot Rams that were in Qualified Vendor List posted by Asus to my motherboard.

Strange I upgraded that ATK0110 yesterday
from Asus website:
Description ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

File Size 119.88 (KBytes) 2009/12/07 update

No I don't have any video card to borrow cause bsod happen randoms sometimes only once a day.

I updated BIOS a week ago.

yooz3r Hi and welcome

The date on the ATK0110 driver is a year and a half before windows seven even came out. If that is the most rrecent driver I suspect the hardware is much older. You have several old drivers built before win 7 come out that need updating

ctac32k.sys        fffff880`05600000    fffff880`056ae000    0x000ae000    0x486b3e7e    7/2/2008 04:38:22                        
spldr.sys        fffff880`01410000    fffff880`01418000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
ASACPI.sys        fffff880`03f2b000    fffff880`03f33000    0x00008000    0x4a0b72fd    5/13/2009 21:25:17                        
amdxata.sys        fffff880`00e00000    fffff880`00e0b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

You have the following causes of your BDOS"s. your video driver of course.
that needs to be completely removed before installing a new one.

Your USBPORT.sys and of course that needs fixing (how many unpowered external USB devices do you have)?

Several other causes pointing to the win 7 OS but in reality not. there are at least three things you should do.

I suspect hardware. Memory, or a device.

As Jonathan_Kng correctly said run Memtest (with one stick at a time if necessary). Find one good ram stick. test it in each mobo slot to decide if it is ram or mobo.

Run a system file check. while I suspect hardware you want to eliminate software as well
(type cmd in search>right click and run as admin>SFC /SCANNOW)

Let us know the results

Update the old drivers especially ASACPI.sys as it has a known history with BSOD.

The usual is also suggested
If overclocking stop (yes ZI know you arent)
If you are running a RAID update its driver.

Your .dmp file shows various stop errors which is may be a general hardware error .. You can read more on this error and what to try here... - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

Thanks


Ken

 

[Tews]

+1 .... Spot on as usual!

 

[zigzag3143]

+1 .... Spot on as usual!

Thanks. Its the Kona talking.

 

[yooz3r]

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:

....
*******************************************************************************
*                                                                             *
*                        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]

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]

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.

*******************************************************************************
*                                                                             *
*                        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]

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

 

[yooz3r]

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]

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: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

...Summary of the Dumps:

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[amandeepmail]

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]

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