Randomly Reboots BSOD for months!

[Mkkl]

Hi there
I have some trouble with my pc,
It's crashing and rebooting randomly especially when playing games.
This has been going on for months and several times I thought I had the solution but then it started again. I tried three different types of OS: XP, Vista and currently 7. Replaced my PSU with an Antec TruePower 750, replaced my ram several times and tested them, no luck. Updated my drivers by hand with removing them first and updating through driver updaters. My ATI Hd4850 goes no higher than 65 degrees celcius which is pretty low for these kind of cards I think. My CPU is not warmer than 50 degrees celsius. I read something about broken capcitors but I looked and couldn't find anything. I raised the voltage on my RAM by 0.1 it seemed to help for a few days, and it only happens when i'm using more than 1 stick of RAM. I'm thinking my motherboards is broken , but it's not very nice when you find out the replaced hardware wasn't faulty and you spent 100 bucks on it, so I would really be sure of it before replacing .
And o yeah I checked everything for rootkits,spyware, malware and virusses. Do you guys have any suggestions? Here are my minidumps and Specs:

Antec truePower 550
Ati Sapphire HD4850
Kingston KVR800D2N5K2/4G
E8400 Intel Core 2Duo

Crashes:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f7ce39, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008866eb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+0
fffff800`02f7ce39 488b4910        mov     rcx,qword ptr [rcx+10h]

CONTEXT:  fffff88008866eb0 -- (.cxr 0xfffff88008866eb0)
Unable to read context, Win32 error 0n30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c8aa3a to fffff88003c3a9c2

STACK_TEXT:  
fffff800`00b9cc58 fffff800`02c8aa3a : 00000000`002cd0a9 fffffa80`0311c698 fffff800`02e03c40 00000000`00000001 : 0xfffff880`03c3a9c2
fffff800`00b9cc60 00000000`002cd0a9 : fffffa80`0311c698 fffff800`02e03c40 00000000`00000001 fffff800`02df5e80 : 0xfffff800`02c8aa3a
fffff800`00b9cc68 fffffa80`0311c698 : fffff800`02e03c40 00000000`00000001 fffff800`02df5e80 fffff800`02c88697 : 0x2cd0a9
fffff800`00b9cc70 fffff800`02e03c40 : 00000000`00000001 fffff800`02df5e80 fffff800`02c88697 00000001`4793fa73 : 0xfffffa80`0311c698
fffff800`00b9cc78 00000000`00000001 : fffff800`02df5e80 fffff800`02c88697 00000001`4793fa73 00000001`0001d480 : 0xfffff800`02e03c40
fffff800`00b9cc80 fffff800`02df5e80 : fffff800`02c88697 00000001`4793fa73 00000001`0001d480 00000001`4793fa73 : 0x1
fffff800`00b9cc88 fffff800`02c88697 : 00000001`4793fa73 00000001`0001d480 00000001`4793fa73 00000000`00000080 : 0xfffff800`02df5e80
fffff800`00b9cc90 00000001`4793fa73 : 00000001`0001d480 00000001`4793fa73 00000000`00000080 fffffa80`0311c600 : 0xfffff800`02c88697
fffff800`00b9cc98 00000001`0001d480 : 00000001`4793fa73 00000000`00000080 fffffa80`0311c600 400000c2`400000c1 : 0x1`4793fa73
fffff800`00b9cca0 00000001`4793fa73 : 00000000`00000080 fffffa80`0311c600 400000c2`400000c1 fffff800`400000c3 : 0x1`0001d480
fffff800`00b9cca8 00000000`00000080 : fffffa80`0311c600 400000c2`400000c1 fffff800`400000c3 00000000`ea4db85b : 0x1`4793fa73
fffff800`00b9ccb0 fffffa80`0311c600 : 400000c2`400000c1 fffff800`400000c3 00000000`ea4db85b fffff800`00b96080 : 0x80
fffff800`00b9ccb8 400000c2`400000c1 : fffff800`400000c3 00000000`ea4db85b fffff800`00b96080 fffffa80`018c7740 : 0xfffffa80`0311c600
fffff800`00b9ccc0 fffff800`400000c3 : 00000000`ea4db85b fffff800`00b96080 fffffa80`018c7740 00000000`00000000 : 0x400000c2`400000c1
fffff800`00b9ccc8 00000000`ea4db85b : fffff800`00b96080 fffffa80`018c7740 00000000`00000000 0000051d`c93063b0 : 0xfffff800`400000c3
fffff800`00b9ccd0 fffff800`00b96080 : fffffa80`018c7740 00000000`00000000 0000051d`c93063b0 0000051d`c93071ed : 0xea4db85b
fffff800`00b9ccd8 fffffa80`018c7740 : 00000000`00000000 0000051d`c93063b0 0000051d`c93071ed fffff800`02c831a2 : 0xfffff800`00b96080
fffff800`00b9cce0 00000000`00000000 : 0000051d`c93063b0 0000051d`c93071ed fffff800`02c831a2 fffff800`00b96080 : 0xfffffa80`018c7740


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner




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: fffff8060196cd3c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800185944c, address which referenced memory

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 fffff8060196cd3c 

CURRENT_IRQL:  0

FAULTING_IP: 
+0
fffff880`0185944c ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from fffff80002c8c469 to fffff80002c8cf00

STACK_TEXT:  
fffff800`00b9c1b8 fffff800`02c8c469 : 00000000`0000000a fffff806`0196cd3c 00000000`00000002 00000000`00000001 : 0xfffff800`02c8cf00
fffff800`00b9c1c0 00000000`0000000a : fffff806`0196cd3c 00000000`00000002 00000000`00000001 fffff880`0185944c : 0xfffff800`02c8c469
fffff800`00b9c1c8 fffff806`0196cd3c : 00000000`00000002 00000000`00000001 fffff880`0185944c 00000000`00000000 : 0xa
fffff800`00b9c1d0 00000000`00000002 : 00000000`00000001 fffff880`0185944c 00000000`00000000 00000000`00000000 : 0xfffff806`0196cd3c
fffff800`00b9c1d8 00000000`00000001 : fffff880`0185944c 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffff800`00b9c1e0 fffff880`0185944c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff800`00b9c1e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0185944c


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner



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: fffffa0003aedf60, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ccd1c2, address which referenced memory

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 fffffa0003aedf60 

CURRENT_IRQL:  0

FAULTING_IP: 
+0
fffff800`02ccd1c2 48894108        mov     qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff80002cc8469 to fffff80002cc8f00

STACK_TEXT:  
fffff800`00ba23f8 fffff800`02cc8469 : 00000000`0000000a fffffa00`03aedf60 00000000`00000002 00000000`00000001 : 0xfffff800`02cc8f00
fffff800`00ba2400 00000000`0000000a : fffffa00`03aedf60 00000000`00000002 00000000`00000001 fffff800`02ccd1c2 : 0xfffff800`02cc8469
fffff800`00ba2408 fffffa00`03aedf60 : 00000000`00000002 00000000`00000001 fffff800`02ccd1c2 00000000`00000001 : 0xa
fffff800`00ba2410 00000000`00000002 : 00000000`00000001 fffff800`02ccd1c2 00000000`00000001 00000000`00000000 : 0xfffffa00`03aedf60
fffff800`00ba2418 00000000`00000001 : fffff800`02ccd1c2 00000000`00000001 00000000`00000000 00000000`00000000 : 0x2
fffff800`00ba2420 fffff800`02ccd1c2 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff800`00ba2428 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`02ccd1c2
fffff800`00ba2430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner

 

[IggyAZ]

Welcome and you have a good start with the minidump.
You never said what motherboard you have.
If you go into your Control Panel: System: Device Manager: Do you see any exclamation points next to any of the devices?

Hope to hear from you soon.

 

[Mkkl]

ahaha, yeah that's a little stupid forgot the most important almost,
It's an MSI Neo3-FR 1.0
And by the way, when it crashes sometimes a very shrieking sound and a little bit like ( i dont know the word) when you turn on the radio and it's not on a channel. ( hope you know what I mean. And tonight I had a few pixels that were red green and yellow that appeared when it crashed within my game screen.

And I don't have any exclamation point in the device manager.

 

[Mkkl]

???

 

[Lordbob75]

Mkkl, can you post the minidump as a .zip please? Yours did not correctly analyze it I think.

Also, you mentioned that this BSoDs only happen with more than one stick of RAM? Can you test that please?
If that is the case, switch the sticks up. If you have two sticks and it works fine with one, then crashes with the second, then remove the first module and try to boot with just the second. If it still crashes, that is a bad RAM stick.

Also, run MemTest86+: http://www.sevenforums.com/crash-lockup-debug-how/53854-check-your-ram.html

~Lordbob

 

[Mkkl]

Yeah well I checked eveyone of them, I tried 6 different ones , with 4 of them brand new and all sorts of combinations sticks had no errors after a turn or 6

 

[Lordbob75]

Yeah well I checked eveyone of them, I tried 6 different ones , with 4 of them brand new and all sorts of combinations sticks had no errors after a turn or 6

No errors after what?
Sorry, just don't know what you mean.

~Lordbob

 

[Mkkl]

after 6 rounds of memtes86+, already used it before posting

 

[Lordbob75]

after 6 rounds of memtes86+, already used it before posting

OH ok.

I still need you to post the dmp

~Lordbob

 

[Mkkl]

Im Sorry for the delay, but the dumps were automatically removed or something so I have got some new ones.

 

[Lordbob75]

Appears to be caused in part by Chrome.

~Lordbob

 

[Mkkl]

Well, maybe these ones but it still happens when Chrome wasn't installed and when it's not on...

 

[Mkkl]

Well, I have a new minidump, everything was fine, then I turned Itunes on, it played a song for a couple of second and then BSOD'd. And the Sound froze. I'll check my audio drivers again.

 

[dsosb]

Device problem solved

I don't know if this might be any help, but I had the same problem with a new build for several weeks. The machine would start in the morning and 15 minutes later it would BSOD. Then randomly during the day the same thing would happen. I tested the RAM and it tested fine with Memtest and nothing was running hot. I had built an identical machine the same day that ran just fine. I was really stumped until...I realized the identical machine was not identical. I had used an older Logitech mouse with the problem machine and the other one had an older Microsoft mouse. I looked for new drivers for the older Logitech and could not find ones the were certified to work with Windows 7. So, I purchased a new Logitech wireless mouse and have not had a problem since. Sometimes it's the little things.

 

[Mkkl]

and another one!

 

[zigzag3143]

and another one!

MKKI


This one was caused by the directx portion of your video driver (dxgmms1.sys).

You need to completely uninstall the video driver and install a fresh copy. Dont use the windows update, go to the mfr web site.

Also run a system file check
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking stop

Let us know the results

Ken

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


Loading Dump File [C:\Users\K\Desktop\021810-21637-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50
Debug session time: Thu Feb 18 09:38:22.040 2010 (GMT-5)
System Uptime: 0 days 3:10:08.664
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {108, 2, 0, fffff80002fb136b}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\021810-21637-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50
Debug session time: Thu Feb 18 09:38:22.040 2010 (GMT-5)
System Uptime: 0 days 3:10:08.664
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
[B]
BugCheck C5, {108, 2, 0, fffff80002fb136b}[/B]

[B]Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSignalRegisteredEvent+e7 )
[/B]
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: 0000000000000108, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002fb136b, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExFreePoolWithTag+2bb
fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff80000ba2610 -- (.trap 0xfffff80000ba2610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffff80002ff7e80
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb136b rsp=fffff80000ba27a8 rbp=0000000000000000
 r8=0000000000005f00  r9=0000000000000150 r10=fffff80002e0c000
r11=0000000000000260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!ExFreePoolWithTag+0x2bb:
fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h] ds:dd50:00000000`00000108=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7d469 to fffff80002e7df00

STACK_TEXT:  
fffff800`00ba24c8 fffff800`02e7d469 : 00000000`0000000a 00000000`00000108 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba24d0 fffff800`02e7c0e0 : fffffa80`03d01b60 fffffa80`043e6878 00000000`00000001 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2610 fffff800`02fb136b : fffff880`03c0b76d fffffa80`06d3dd50 fffffa80`066e4ba8 fffffa80`68536956 : nt!KiPageFault+0x260
fffff800`00ba27a8 fffffa80`066e4410 : fffff880`021c8bd0 fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 : nt!ExFreePoolWithTag+0x2bb
fffff800`00ba2858 fffff880`021c8bd0 : fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 : 0xfffffa80`066e4410
fffff800`00ba2860 fffffa80`066e4ba0 : fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 00000000`00000000 : 0xfffff880`021c8bd0
fffff800`00ba2868 fffff880`03c0c47f : fffffa80`066e4ba0 00000000`00000001 00000000`00000000 fffffa80`07130010 : 0xfffffa80`066e4ba0
fffff800`00ba2870 fffff880`03c097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiSignalRegisteredEvent+0xe7
fffff800`00ba28c0 fffff880`03c08e00 : 00000000`00000000 fffffa80`066e4410 00000000`00000000 fffff800`02ff6e80 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff800`00ba2960 fffff880`03c08c4c : fffffa80`05d13f08 fffffa80`066e4410 fffffa80`05be3f40 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff800`00ba29b0 fffff880`042d21cf : fffffa80`04b55480 fffffa80`00000000 00000000`00000001 00000000`00000004 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff800`00ba2a00 fffffa80`04b55480 : fffffa80`00000000 00000000`00000001 00000000`00000004 fffffa80`05bdb000 : dxgkrnl+0x31cf
fffff800`00ba2a08 fffffa80`00000000 : 00000000`00000001 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 : 0xfffffa80`04b55480
fffff800`00ba2a10 00000000`00000001 : 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 : 0xfffffa80`00000000
fffff800`00ba2a18 00000000`00000004 : fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 : 0x1
fffff800`00ba2a20 fffffa80`05bdb000 : fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 : 0x4
fffff800`00ba2a28 fffff880`03cb7230 : fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 : 0xfffffa80`05bdb000
fffff800`00ba2a30 fffff800`02ff6e80 : 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 : atikmdag+0x1e230
fffff800`00ba2a38 00000000`00000000 : 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 fffff880`03cc441a : nt!KiInitialPCR+0x180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiSignalRegisteredEvent+e7
fffff880`03c0c47f 440fb6de        movzx   r11d,sil

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VidSchiSignalRegisteredEvent+e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7

BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7

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

 ( dxgmms1!VidSchiSignalRegisteredEvent+e7 )

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: 0000000000000108, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002fb136b, address which referenced memory

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


BUGCHECK_STR:  0xC5_2

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExFreePoolWithTag+2bb
fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff80000ba2610 -- (.trap 0xfffff80000ba2610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffff80002ff7e80
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fb136b rsp=fffff80000ba27a8 rbp=0000000000000000
 r8=0000000000005f00  r9=0000000000000150 r10=fffff80002e0c000
r11=0000000000000260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!ExFreePoolWithTag+0x2bb:
fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h] ds:dd50:00000000`00000108=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7d469 to fffff80002e7df00

STACK_TEXT:  
fffff800`00ba24c8 fffff800`02e7d469 : 00000000`0000000a 00000000`00000108 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba24d0 fffff800`02e7c0e0 : fffffa80`03d01b60 fffffa80`043e6878 00000000`00000001 00000000`00000002 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2610 fffff800`02fb136b : fffff880`03c0b76d fffffa80`06d3dd50 fffffa80`066e4ba8 fffffa80`68536956 : nt!KiPageFault+0x260
fffff800`00ba27a8 fffffa80`066e4410 : fffff880`021c8bd0 fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 : nt!ExFreePoolWithTag+0x2bb
fffff800`00ba2858 fffff880`021c8bd0 : fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 : 0xfffffa80`066e4410
fffff800`00ba2860 fffffa80`066e4ba0 : fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 00000000`00000000 : 0xfffff880`021c8bd0
fffff800`00ba2868 fffff880`03c0c47f : fffffa80`066e4ba0 00000000`00000001 00000000`00000000 fffffa80`07130010 : 0xfffffa80`066e4ba0
fffff800`00ba2870 fffff880`03c097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiSignalRegisteredEvent+0xe7
fffff800`00ba28c0 fffff880`03c08e00 : 00000000`00000000 fffffa80`066e4410 00000000`00000000 fffff800`02ff6e80 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff800`00ba2960 fffff880`03c08c4c : fffffa80`05d13f08 fffffa80`066e4410 fffffa80`05be3f40 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff800`00ba29b0 fffff880`042d21cf : fffffa80`04b55480 fffffa80`00000000 00000000`00000001 00000000`00000004 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff800`00ba2a00 fffffa80`04b55480 : fffffa80`00000000 00000000`00000001 00000000`00000004 fffffa80`05bdb000 : dxgkrnl+0x31cf
fffff800`00ba2a08 fffffa80`00000000 : 00000000`00000001 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 : 0xfffffa80`04b55480
fffff800`00ba2a10 00000000`00000001 : 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 : 0xfffffa80`00000000
fffff800`00ba2a18 00000000`00000004 : fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 : 0x1
fffff800`00ba2a20 fffffa80`05bdb000 : fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 : 0x4
fffff800`00ba2a28 fffff880`03cb7230 : fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 : 0xfffffa80`05bdb000
fffff800`00ba2a30 fffff800`02ff6e80 : 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 : atikmdag+0x1e230
fffff800`00ba2a38 00000000`00000000 : 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 fffff880`03cc441a : nt!KiInitialPCR+0x180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiSignalRegisteredEvent+e7
fffff880`03c0c47f 440fb6de        movzx   r11d,sil

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  dxgmms1!VidSchiSignalRegisteredEvent+e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7

BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7

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

 

[Mkkl]

Do you have a recommendation for an uninstall method? Because I hae done it before. Using all kinds of driver uninstaller like driver cleaner and driver sweeper. And what exactly do you mean by don't using the windows update? And I always get my drivers from the Sapphire website. I'm not overclocking and will begin my system file check. Thanks for your reaction!

 

[Mkkl]

I did it but still have BSOD's including these ones