New
#21
Nah, you can keep them there unless you want to remove them to free up space. Just don't remove any .dmp files after you have another crash, though I'm wishing you the best that crashes do not happen again.
BSOD sometime on my system
-
-
New #22
-
New #23
Points more to a driver issue...Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\022612-42167-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eac670 Debug session time: Sun Feb 26 19:43:45.462 2012 (UTC - 7:00) System Uptime: 0 days 0:38:02.944 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, fffffa8004133070, fffffa8004133940, c8da1a0} GetPointerFromAddress: unable to read from fffff80002f16100 Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1c7 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000020, a pool block header size is corrupt. Arg2: fffffa8004133070, The pool entry we were looking for within the page. Arg3: fffffa8004133940, The next pool entry. Arg4: 000000000c8da1a0, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: fffffa8004133070 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: 1 IRP_ADDRESS: ffffffffffffff88 LAST_CONTROL_TRANSFER: from fffff80002e11cae to fffff80002ce3c40 STACK_TEXT: fffff880`07652878 fffff800`02e11cae : 00000000`00000019 00000000`00000020 fffffa80`04133070 fffffa80`04133940 : nt!KeBugCheckEx fffff880`07652880 fffff800`02cf909e : 00000000`00000001 fffff800`02ce64da 00000000`20206f49 fffffa80`04133090 : nt!ExDeferredFreePool+0x12da fffff880`07652930 fffff800`02cd72f7 : 00000000`00000000 00000000`00000000 fffffa80`043cff00 fffff880`07652ca0 : nt!IopCompleteRequest+0x5ce fffff880`07652a00 fffff800`02ce913d : fffff880`02fd62c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7 fffff880`07652a80 fffff800`02ceb74f : 00000000`000003ac 00000000`001ea4b0 fffff880`0000006a 00000000`0250f338 : nt!KiCommitThreadWait+0x3dd fffff880`07652b10 fffff800`02fda44e : fffff880`07652c00 fffffa80`00000006 00000000`00000001 fffff800`02cdf801 : nt!KeWaitForSingleObject+0x19f fffff880`07652bb0 fffff800`02ce2ed3 : fffffa80`07ca0840 00000000`000003ac fffff880`07652bf8 fffffa80`07d33800 : nt!NtWaitForSingleObject+0xde fffff880`07652c20 00000000`773f135a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0250f298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773f135a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDeliverApc+1c7 fffff800`02cd72f7 4533c9 xor r9d,r9d SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiDeliverApc+1c7 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x19_20_nt!KiDeliverApc+1c7 BUCKET_ID: X64_0x19_20_nt!KiDeliverApc+1c7 Followup: MachineOwner ---------
-
New #24
-
New #25
Unfortunately, no. The only one that still stands out is the Creative driver.
-
New #26
Good morning, the MEMTEST still running this morning 8 pass no error... I will check tonight when I come back from work.
I remember in the last year, some tech on internet told me that my SoundBlaster is not so "compatible" with Win 7... I should buy a new one ? Do you think it is why the driver is not good... I mean, I have a retail box of SoundBlaster Audigy 2 Platinum ZS...but when I try to install the good driver for this card it doenst work (on Creative web site) The tech told me to check the model on my card and it is SB0460, so that why I have to install driver for this card to make it work... Do you understand what I try to explain lol...
The model SB0460 is an SoundBlaster X-FI... strange no ?
Should I go buy another SoundBlaster Fully compatible with Win 7 and that support my FRONT CONTROL (for my SoundBlaster)
-
New #27
It is worth investigating. Try a newer sound card that is known to work with Windows 7 and see if it helps. Borrow one from a friend if you can so you do not have to spend the money in case it does not resolve the issue.
-
New #28
-
New #29
Yes, I would say that is sufficient testing. Have you tested with all three modules?
-
New #30
No...only 2 X 2048 DDR2... I crash with those last time so I think I dont need to test the othr 2 module ? 21 Pass now with no error :)
Maybe I should remove my SB driver , remove my SB card and put the soundcard that come with my motherboard ?
Maybe that the problem ? or its really the memory... really Im a bit confused
Quote
Related Discussions