New
#11
Just had another, this time it said something about Reference Pointer. ><
Edit: Downloaded and used the tool suggested here for submitting these. Sorry! Hopefully this helps.
Just had another, this time it said something about Reference Pointer. ><
Edit: Downloaded and used the tool suggested here for submitting these. Sorry! Hopefully this helps.
More bluescreens now. It seems to be getting worse. At one point I was stuck booting to BIOS, then it crashed on the login screen, and now it did a system restore and crashed immediately after booting into windows. BAD POOL HEADER and System Service Exception were the only named errors I could see. I've attached the one new dump here.
Also, the driver that was causing my other BSODs is still on my PC but is renamed to .bak as I was instructed.
Edit: I am sitting in safe mode right now and I have no issues at all. Weird.
Error code 19, BAD_POOL_HEADER. Usual caused by a device driver.
Try turning on Driver Verifier: Driver Verifier - Enable and Disable Use your computer normally while it is running. Upload any dumps triggered by Driver Verifier.Code:System Uptime: 0 days 0:01:19.299 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {3, fffffa80039612d0, fffffa80039612d0, 0} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a56 ) Followup: Pool_corruption --------- 0: 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: 0000000000000003, the pool freelist is corrupt. Arg2: fffffa80039612d0, the pool entry being checked. Arg3: fffffa80039612d0, the read back flink freelist value (should be the same as 2). Arg4: 0000000000000000, the read back blink freelist value (should be the same as 2). Debugging Details: ------------------ BUGCHECK_STR: 0x19_3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wmpnetwk.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002dacd6f to fffff80002c79740 STACK_TEXT: fffff880`08187358 fffff800`02dacd6f : 00000000`00000019 00000000`00000003 fffffa80`039612d0 fffffa80`039612d0 : nt!KeBugCheckEx fffff880`08187360 fffff800`02f57dcb : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0xa56 fffff880`08187450 fffff800`02f586ed : 00000000`00000027 00000000`00002730 fffff8a0`02c20948 00000000`000c8c88 : nt!CmpGetNameControlBlock+0x160 fffff880`081874b0 fffff800`02f571b7 : fffff8a0`005be010 00000000`0068ea50 fffff8a0`04582a54 fffff8a0`0269d380 : nt!CmpCreateKeyControlBlock+0x35e fffff880`08187550 fffff800`02f53195 : fffff8a0`00000000 fffff8a0`0068ea50 fffff8a0`005be010 fffffa80`063b7b10 : nt!CmpDoOpen+0x387 fffff880`08187610 fffff800`02f72e84 : fffff800`02f52cc0 00000000`00000001 fffffa80`063b7b10 00000000`00000001 : nt!CmpParseKey+0x4d5 fffff880`081878e0 fffff800`02f77e4d : fffffa80`063b7b10 fffff880`08187a40 00000000`00000040 fffffa80`03a1aa50 : nt!ObpLookupObjectName+0x585 fffff880`081879e0 fffff800`02f56dcc : 00000000`0259d600 00000000`00000000 fffff8a0`02360c01 fffff880`08187aa8 : nt!ObOpenObjectByName+0x1cd fffff880`08187a90 fffff800`02f58f0f : 00000000`0164e720 00000000`00020019 00000000`0164e7a8 00000000`00000000 : nt!CmOpenKey+0x28a fffff880`08187be0 fffff800`02c78993 : fffffa80`065ca8b0 fffff880`08187ca0 00000000`017c0940 fffffa80`067aba20 : nt!NtOpenKeyEx+0xf fffff880`08187c20 00000000`77360caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0164e6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77360caa STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+a56 fffff800`02dacd6f cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExDeferredFreePool+a56 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56 BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a56 Followup: Pool_corruption ---------
I am uploading a new one now. Is the one I uploaded at the top of this page done incorrectly? Sorry!
Edit for clarity: I had just read that when I posted last night at the top of the page so I added it on to that post. I had just been uploaded my new dumps after, and didn't see it before because I'm blind. I just ran CC cleaner because on a support website it said that BAD POOL HEADER was a registry error most of the time and to try that. I am running the program to give you guys an updated one to look at now.
Edit2: Uploaded now.
Since turning driver verifier on I have blue screened twice with no dump in my windows folder. Is there anything else I can upload that will help solve this? I am posting this from safe mode because if I boot into normal windows I only get a few seconds before it crashes.
Thanks in advance! Will reboot in normal mode to see if I can get a dump file for a bit.
Edit2: Dump file!
Edit3: It might also be worth noting that I sometimes have issues booting into windows normally still, yet if it does boot and it crashes I have had 0 problems loading into safe mode and 0 errors while in safe mode.
Edit4: Another Driver irql not less or equal bsod with no dump.
Edit5: Another BSOD with a dump this time. Uploaded it as well and booted into safe mode to see if they would continue. 20 minutes in safe mode and no blue screens.
Last edited by Bain; 09 Oct 2010 at 14:28.
Tried booting normally again and crashed after a couple of minutes so I'm back in safe mode. No dump this time.
Both dumps are error code D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. One dump was inconclusive. The other dump blames partmgr.sys, which is a Windows System driver and unlikely to be the real cause.
Run MSCONFIG, under the General tab, select Diagnostic startup and reboot. Let's see if you get a BSOD.Code:Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50 Debug session time: Sat Oct 9 14:54:42.943 2010 (GMT-4) System Uptime: 0 days 0:02:49.691 Unable to load image Unknown_Module_00b0248c`8b48c78b, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00b0248c`8b48c78b *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00b0248c`8b48c78b Debugger can not determine kernel base address Loading Kernel Symbols . Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {100000016, 2, 0, fffff880014010f9} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50 Debug session time: Sat Oct 9 15:15:38.456 2010 (GMT-4) System Uptime: 0 days 0:02:25.173 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {129, 2, 0, fffff88000f72f64} Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+34 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000129, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88000f72f64, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eaf0e0 0000000000000129 CURRENT_IRQL: 2 FAULTING_IP: partmgr!PmReadWriteCompletion+34 fffff880`00f72f64 80bf2901000000 cmp byte ptr [rdi+129h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: sppsvc.exe TRAP_FRAME: fffff88002d93780 -- (.trap 0xfffff88002d93780) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff88002d93938 rbx=0000000000000000 rcx=fffffa8004a34390 rdx=fffffa8006f38c10 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88000f72f64 rsp=fffff88002d93910 rbp=fffffa8006f38c10 r8=0000000000000000 r9=fffffa80047d41b0 r10=fffffa800395d620 r11=fffff88002d93a18 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc partmgr!PmReadWriteCompletion+0x34: fffff880`00f72f64 80bf2901000000 cmp byte ptr [rdi+129h],0 ds:0002:00000000`00000129=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c76ca9 to fffff80002c77740 STACK_TEXT: fffff880`02d93638 fffff800`02c76ca9 : 00000000`0000000a 00000000`00000129 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`02d93640 fffff800`02c75920 : fffffa80`0395d6a8 fffffa80`06f38e4b 00000000`c0000050 fffffa80`06819f68 : nt!KiBugCheckDispatch+0x69 fffff880`02d93780 fffff880`00f72f64 : fffffa80`05125480 fffff800`02dab4d3 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x260 fffff880`02d93910 fffff800`02c79d26 : fffffa80`06f38e4b 00000000`00000034 fffffa80`04a34390 fffffa80`06f38c10 : partmgr!PmReadWriteCompletion+0x34 fffff880`02d93940 fffff880`010018ee : 00000000`00009420 fffff880`13e55701 fffffa80`0512b4f0 00000000`00000000 : nt!IopfCompleteRequest+0x3a6 fffff880`02d93a20 fffff800`02c79d26 : 00000000`00000000 fffff880`13e9a66e 00000000`00000000 00000000`00000000 : CLASSPNP!TransferPktComplete+0x1ce fffff880`02d93aa0 fffff880`00e3c41a : 00000000`00000000 00000000`00000001 fffffa80`060c8b80 00000000`00000000 : nt!IopfCompleteRequest+0x3a6 fffff880`02d93b80 fffff880`00e3c242 : fffffa80`060c8b80 fffffa80`047c8ea0 fffffa80`06ad6c40 fffffa80`06ad6c00 : ataport!IdeCompleteScsiIrp+0x62 fffff880`02d93bb0 fffff880`00e36e32 : 00000000`00000000 00000000`00000000 fffffa80`047cb000 fffff800`0320ec60 : ataport!IdeCommonCrbCompletion+0x5a fffff880`02d93be0 fffff880`00e3f7ed : fffffa80`0395c1a0 fffffa80`060c8b80 00000000`00000000 fffffa80`060c8b80 : ataport!IdeTranslateCompletedRequest+0x236 fffff880`02d93d10 fffff880`00e3f0ec : fffffa80`0395c1a0 00000000`00000000 fffffa80`0395c1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5 fffff880`02d93e40 fffff800`02c82bfc : fffff880`02d64180 fffffa80`00002456 fffffa80`0395c050 fffffa80`0395c118 : ataport!IdePortCompletionDpc+0x1a8 fffff880`02d93f00 fffff800`02c7d865 : 00000000`00000000 fffffa80`060b4060 00000000`00000000 fffff880`00e3ef44 : nt!KiRetireDpcList+0x1bc fffff880`02d93fb0 fffff800`02c7d67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 fffff880`083b1650 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: partmgr!PmReadWriteCompletion+34 fffff880`00f72f64 80bf2901000000 cmp byte ptr [rdi+129h],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: partmgr!PmReadWriteCompletion+34 FOLLOWUP_NAME: MachineOwner MODULE_NAME: partmgr IMAGE_NAME: partmgr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11e FAILURE_BUCKET_ID: X64_0xD1_partmgr!PmReadWriteCompletion+34 BUCKET_ID: X64_0xD1_partmgr!PmReadWriteCompletion+34 Followup: MachineOwner ---------
As you suspected booting normally with those options set resulted in a smooth load and no crash, however booting normally with all drivers resulted in a bsod with the dump attached. A sincere thank you to all of those who have helped me so far - far more help here than Cyberpower wants to give me.