rifters

>we are doing work in win32k.sys when the crashes occur (win32k!SURFACE::bDeleteSurface+0x228), which would indicate a video card driver issue I see the line you mention in the first dump, but what about the second one? (the blue one) I don't see the same line there. Its an nvidia geforce 8800 ultra running 163.69 (certified offiicial latest), have also tried 162.18's. I've applied the changes to page file etc, will wait and see, curiously Windows recommended a page file of 6 GB so I set it to that (it was previously at 4.3GB) and so far theres only been 1 crash since my last post here, a few minutes ago infact, unfortunatley though when I tried to open it in the debugger it would not load for some reason (used the same process for the other 2 debugs). I wasn't at the screen when the BSOD came so didn't see the message. Will post back if\when I can do another debug process with new dump files. >You need to get Prime95 to confirm that your Core 2 Duo is stable. As I said in my original post I'm 99 percent sure the hardware is stable. The Orthos test I mention is prime95 with a GUI. I run 2 instances of this test in blend mode on each core, which stress tests CPU and memory at the same time, for 24 hours continuous, the system doesn't break a sweat. Core 2 Duos are notoriously good overclockers @ default V's. Plus I have all thermal throttling enabled in the BIOS which lowers the multiplier at idle and light loads - the same time all these BSOD's occur. -rifters

The process I linked to in my previous post about creating dumps does not work correctly for me in Vista x64. I followed the instructions re. creating registry keys, then rebooted, pressing right ctrl and scroll twice does nothing. In system properties > start up and recovery > write debugging information is set to kernel memory dump. The only other two options here are <none> and small memory dump, this is despite performing the steps in the link in my previous post. Thus, all I have been able to get into the debugger are these two minidump examples: #1 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa800310c440 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: iexplore.exe CURRENT_IRQL: 0 BAD_PAGES_DETECTED: d LAST_CONTROL_TRANSFER: from fffff80002870749 to fffff8000284dbd0 STACK_TEXT: fffff980`3fccfa88 fffff800`02870749 : 00000000`0000001a 00000000`00041790 fffffa80`0310c440 00000000`0000ffff : nt!KeBugCheckEx fffff980`3fccfa90 fffff800`0288d52a : 00000000`00000011 00000000`0f4bafff 00000000`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0xd49 fffff980`3fccfc20 fffff800`0284d673 : ffffffff`ffffffff fffffa80`095bbad0 00000000`00000001 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x38a fffff980`3fccfd20 fffff800`0284db80 : fffff960`000c34d8 00000000`0ee00000 00000000`00000004 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13 fffff980`3fccfeb8 fffff960`000c34d8 : 00000000`0ee00000 00000000`00000004 00000000`00000001 00000000`00000001 : nt!KiServiceLinkage fffff980`3fccfec0 fffff960`000cb615 : 00000000`0ee00000 00000000`00000001 fffff900`c018d540 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x228 fffff980`3fccffa0 fffff960`000c2ed4 : 00000000`00000000 fffff980`3fcd0c00 fffff900`c07a3180 fffffa80`048794f0 : win32k!NtGdiCloseProcess+0x2d5 fffff980`3fcd0000 fffff960`000c251f : 00000000`00000000 fffff900`c07a3180 00000000`00000000 fffff900`c01e6460 : win32k!GdiProcessCallout+0x1f4 fffff980`3fcd0080 fffff800`02ab360e : fffffa80`07ca04f0 00000000`00000000 fffffa80`07ca04f0 fffffa80`095bbad0 : win32k!W32pProcessCallout+0x6f fffff980`3fcd00b0 fffff800`02a6300d : fffffa80`000000ff 00000000`00000001 fffffa80`09a7f660 00000000`78457350 : nt!PspExitThread+0x29e fffff980`3fcd0170 fffff800`02846049 : fffffa80`095bbad0 fffff980`3fcd0220 00000000`08d8d070 00000000`00000020 : nt!PsExitSpecialApc+0x1d fffff980`3fcd01a0 fffff800`0285f9ea : 00000000`7ef82000 ffe7ebf6`ffe7ebf6 fffff800`02a63020 00000000`00000001 : nt!KiDeliverApc+0x409 fffff980`3fcd0240 fffff800`0284d71d : fffffa80`095bbad0 00000000`7ef82000 00000000`00000020 fffffa80`042e9b50 : nt!KiInitiateUserApc+0x7a fffff980`3fcd0380 00000000`76fa1ff7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0xa2 00000000`08d8e0b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fa1ff7 STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO_VISTA FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO_VISTA Followup: MachineOwner --------- *** Memory manager detected 13 instance(s) of page corruption, target is likely to have memory corruption. #2 MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa8003112080 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SearchProtocolH CURRENT_IRQL: 0 BAD_PAGES_DETECTED: 2 LAST_CONTROL_TRANSFER: from fffff80002870749 to fffff8000284dbd0 STACK_TEXT: fffff980`1bfff798 fffff800`02870749 : 00000000`0000001a 00000000`00041790 fffffa80`03112080 00000000`0000ffff : nt!KeBugCheckEx fffff980`1bfff7a0 fffff800`02871e37 : fffffa80`036f9f11 00000000`0069dfff 00000000`00000000 fffff680`00000000 : nt!MiDeleteVirtualAddresses+0xd49 fffff980`1bfff930 fffff800`02880597 : fffffa80`054a1c10 00000000`00000000 fffffa80`054a1c10 fffffa80`078c3e60 : nt!MiRemoveMappedView+0x62b fffff980`1bfffa60 fffff800`02ab3756 : fffff880`0576aaa0 00000000`00000000 00000000`00000000 fffffa80`04e208d0 : nt!MmCleanProcessAddressSpace+0x277 fffff980`1bfffab0 fffff800`02a85f9d : 00000000`00000000 fffffa80`04e20801 000007ff`fffdc000 00000000`00000000 : nt!PspExitThread+0x3e6 fffff980`1bfffb70 fffff800`02a8b93d : 00000000`00000000 00000000`0000000c 00000000`00187cb0 fffffa80`0000000c : nt!PspTerminateThreadByPointer+0x4d fffff980`1bfffbc0 fffff800`0284d673 : fffffa80`054a1c10 fffffa80`04e208d0 fffff980`1bfffca0 00000000`00187cb0 : nt!NtTerminateProcess+0x18d fffff980`1bfffc20 00000000`7765053a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000af9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7765053a STACK_COMMAND: kb SYMBOL_NAME: PAGE_NOT_ZERO_VISTA FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: PAGE_NOT_ZERO_VISTA Followup: MachineOwner --------- *** Memory manager detected 2 instance(s) of page corruption, target is likely to have memory corruption. One instance is the crash I referred to in my original post about IE7. The second module is unknown presumably because its a minidump. -rifters

Hi, my PC with Vista x64 has started firing off BSOD's. Namely MEMORY_MANAGEMENT about once maybe twice a day, and occasionally the IRQ_NOT_EQUAL BSOD aswell. This PC has had Vista x64 installed for appx 3 months. During the first couple of months the system ran fine, no BSOD's or anything. Then all of a sudden, out of the blue, with no hardware changes, these BSOD problems have appeared. I've just completed a clean reinstall yesterday to see if it goes away, and today, once again, a MEMORY_MANAGEMENT BSOD. The OS is a fully updated Vista x64 OEM activated version. No hardware has been changed since the initial install and activation. Spec fwiw: Core 2 Duo E6600 @ 3GHz (334x9) 4 GB OCZ DDR2 @ 502MHz Abit IP35 Pro P35 Motherboard EVGA 8800 Ultra PCIE VGA X-FI Extreme Gamer PCI Soundcard Hauppauge DVB-t-500 Dual DVB Tuner PCI card 700w Seasonic PSU CPU, case etc all well cooled with third part performance parts. I'm 99 percent sure hardware wise the system is stable - again - this ran fine for just over 2 months like this with no BSOD's. I've tried various different drivers, some beta, some final & certified. The problem is the same throughout. The BSOD's aren't occuring in anything specific either. For example not under a heavy gaming load, or a large download. The last one occured whilst simply opening IE7 from the desktop. Vista reports appx 1GB physical is in use once the OS has loaded. Using Orthos in blend mode, there are no errors or other problems with either memory or CPU under load either. The page file is set to auto managed by Vista. I've just downloaded the debugger kit for x64, after reading this thread http://www.msfn.org/board/Creating_memory_dumps_t90244.html, but before I go on, does that process work in Vista x64? Can anybody shed some light on this? Thanks in advance. -Rifters