200+ bsod

There was no dump file included. https://www.sevenforums.com/tutorials...en-forums.html

This was a Driver Verifier enabled dump with an error code of D3.

D3 - DRIVER_PORTION_MUST_BE_NONPAGED. Caused by a device drive. This indicates that the system attempted to access pageable memory at a process IRQL that was too high.

The dump blames a Microsoft core system driver, which in all probability is not the culprit.

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_canofworms5.zip\081910-21387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304ae50
Debug session time: Wed Aug 18 22:00:38.955 2010 (GMT-4)
System Uptime: 0 days 0:00:10.141
Loading Kernel Symbols
...............................................................
...................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D3, {fffff88000ece824, 2, 0, fffff80002eaa662}

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

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

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

DRIVER_PORTION_MUST_BE_NONPAGED (d3)
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
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 marking code or data as pageable when it should be
marked nonpaged.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88000ece824, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002eaa662, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b50e0
 fffff88000ece824 

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD3

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800335fcc0 -- (.trap 0xfffff8800335fcc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000ec0558 rbx=0000000000000000 rcx=fffff88000ece834
rdx=fffff88000ece7e4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eaa662 rsp=fffff8800335fe50 rbp=fffff88003360cf8
 r8=0000000000000072  r9=000000000000004d r10=fffff880033612e0
r11=fffff8800335fe98 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlDispatchException+0x122:
fffff800`02eaa662 410fb60c24      movzx   ecx,byte ptr [r12] ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7cb69 to fffff80002e7d600

STACK_TEXT:  
fffff880`0335fb78 fffff800`02e7cb69 : 00000000`0000000a fffff880`00ece824 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0335fb80 fffff800`02e7b7e0 : 00000000`000000d7 00000000`00000040 fffff800`02fccb2c fffff800`02e5a387 : nt!KiBugCheckDispatch+0x69
fffff880`0335fcc0 fffff800`02eaa662 : fffff880`00ece824 fffff880`0335fe98 fffff880`03360cf8 fffff880`00eba000 : nt!KiPageFault+0x260
fffff880`0335fe50 fffff800`02eb78df : fffff880`03360cf8 fffff880`03360560 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x122
fffff880`03360530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!RtlDispatchException+122

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xD3_VRF_nt!RtlDispatchException+122

BUCKET_ID:  X64_0xD3_VRF_nt!RtlDispatchException+122

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

I suggest you turn Driver Verifier off and lets see what your system does.

Install these 2 drivers:

Drivers and Downloads

Drivers and Downloads

See if the problem goes away.