Constant BSOD, tried almost everything

hgwng · 08 Jun 2011

Hi guys, i've been constantly getting a BSOD over the past 3 days, mostly regarding ntoskrnl.exe. this is after i tried a repair install. I'm extremely frustrated

and have done the following already

1. after the repair install, removed all files that were causing bsods, like afterburner, daemon tools etc which were giving me bsods. this removed bsod caused by them

2. ntoskrnl.exe then kept causing bsods, so i ran chkdsk /f, memtest 4.2 overnight (16 runs with no errors) and also sfc /scannow, which said it found errors but was not able to fix them. startup repair from the disk and from the repair your computer selection when i press F8 also did not work

3. today i did used acronis true image home to restore my system to before i did a repair install. this only made things worse as now i get bsod after windows boot and i'm at the desktop, all caused by ntoskrnl except for one which was caused by norton.

4. replaced the existing ntoskrnl with the one from windows installation disk.

my system specs are
i5-750 @ 4GHz
msi P55 GD65
team xtreem 2x2gb 1600 CL8 ram
msi 5870 lightning
corsair HX750
samsung F3 1tb
windows 7 ultimate 64 bit

i will try reverting back to stock clocks tomorrow as i'm very tired now, but i doubt it's my OC that's causing it as it's been rock stable ever since i finalised it. also while reinstalling my gpu drivers yesterday (tried 11.5, 11.5a & 11.5b) all seemed to have some problem and could not display 1080p after rebooting to complete installation. I did run driver sweeper prior to installation. i can't run perfmon in safe mode cos it says path not found and i can't try it in normal mode as things can't even finish loading before a bsod.

what do you think guys? i'm at my wits end.

zigzag3143 · 08 Jun 2011

hgwng said:

Hi guys, i've been constantly getting a BSOD over the past 3 days, mostly regarding ntoskrnl.exe. this is after i tried a repair install. I'm extremely frustrated

and have done the following already

1. after the repair install, removed all files that were causing bsods, like afterburner, daemon tools etc which were giving me bsods. this removed bsod caused by them

2. ntoskrnl.exe then kept causing bsods, so i ran chkdsk /f, memtest 4.2 overnight (16 runs with no errors) and also sfc /scannow, which said it found errors but was not able to fix them. startup repair from the disk and from the repair your computer selection when i press F8 also did not work

3. today i did used acronis true image home to restore my system to before i did a repair install. this only made things worse as now i get bsod after windows boot and i'm at the desktop, all caused by ntoskrnl except for one which was caused by norton.

4. replaced the existing ntoskrnl with the one from windows installation disk.

my system specs are
i5-750 @ 4GHz
msi P55 GD65
team xtreem 2x2gb 1600 CL8 ram
msi 5870 lightning
corsair HX750
samsung F3 1tb
windows 7 ultimate 64 bit

i will try reverting back to stock clocks tomorrow as i'm very tired now, but i doubt it's my OC that's causing it as it's been rock stable ever since i finalised it. also while reinstalling my gpu drivers yesterday (tried 11.5, 11.5a & 11.5b) all seemed to have some problem and could not display 1080p after rebooting to complete installation. I did run driver sweeper prior to installation. i can't run perfmon in safe mode cos it says path not found and i can't try it in normal mode as things can't even finish loading before a bsod.

what do you think guys? i'm at my wits end.

Memory corruption caused by your Symantec. Remove and replace with Microsoft Security Essentials.

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Virus, Spyware & Malware Protection | Microsoft Security Essentials

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060911-31917-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02804000 PsLoadedModuleList = 0xfffff800`02a41e50
Debug session time: Wed Jun  8 12:17:14.099 2011 (GMT-4)
System Uptime: 0 days 0:09:41.989
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8000289c3f8, ffffffffffffffff, 0}

Probably caused by : memory_corruption ( nt!MiResolveProtoPteFault+278 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000289c3f8, The address that the exception occurred at
Arg3: ffffffffffffffff, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


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

FAULTING_IP: 
nt!MiResolveProtoPteFault+278
fffff800`0289c3f8 4c8b9c24b0000000 mov     r11,qword ptr [rsp+0B0h]

EXCEPTION_PARAMETER1:  ffffffffffffffff

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aac0e0
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  mmc.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800028b5a17 to fffff80002875f00

STACK_TEXT:  
fffff880`064f0ef8 fffff800`028b5a17 : 00000000`0000001e ffffffff`c0000005 fffff800`0289c3f8 ffffffff`ffffffff : nt!KeBugCheckEx
fffff880`064f0f00 fffff800`02875542 : fffff880`064f16d8 00000001`0133f860 fffff880`064f1780 f8a0037d`83600400 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`064f15a0 fffff800`02873d12 : 00000000`00000000 00000000`00000000 0000007f`fffffff8 00000000`000008e3 : nt!KiExceptionDispatch+0xc2
fffff880`064f1780 fffff800`0289c3f8 : 00000000`00000000 00000001`0253a860 00000000`00000000 fffffa80`062793f8 : nt!KiStackFault+0x112
fffff880`064f1910 fffff800`02891d9e : 00000000`00000000 000007fe`f78637a0 fffff683`ff7bc318 fffffa80`062793f8 : nt!MiResolveProtoPteFault+0x278
fffff880`064f19b0 fffff800`0288ff23 : 00000000`00000000 000007fe`f78637a0 fffff880`064f1c20 fffff680`00000000 : nt!MiDispatchFault+0x1de
fffff880`064f1ac0 fffff800`02873fee : 00000000`00000008 00000000`00000000 00000000`77550101 00000000`00000080 : nt!MmAccessFault+0x343
fffff880`064f1c20 000007fe`f78637a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0029a6f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f78637a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiResolveProtoPteFault+278
fffff800`0289c3f8 4c8b9c24b0000000 mov     r11,qword ptr [rsp+0B0h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiResolveProtoPteFault+278

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiResolveProtoPteFault+278

BUCKET_ID:  X64_0x1E_nt!MiResolveProtoPteFault+278

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

hgwng · 09 Jun 2011

that's fixed it i think, will continue to monitor the situation. thanks!

zigzag3143 · 09 Jun 2011

hgwng said:

that's fixed it i think, will continue to monitor the situation. thanks!

My pleasure

Ken

hgwng · 10 Jun 2011

hmm, found out that i got a bsod last night when i left my rig on to defrag :/
and also i get this sound like "dun ne ne(in quick succession)" randomly

hgwng · 11 Jun 2011

wtf, i installed dirt 3 and it asked me to install directx 9 and i foolishly clicked yes. i've been having bsods whenever i play games.

zigzag3143 · 11 Jun 2011

hgwng said:

wtf, i installed dirt 3 and it asked me to install directx 9 and i foolishly clicked yes. i've been having bsods whenever i play games.

Well of course these show dirextX as the culprit. I would re-install the video driver and directX. You are of course reaching the point where it might just be easier to re-install windows.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\061111-35162-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03461000 PsLoadedModuleList = 0xfffff800`0369ee50
Debug session time: Sat Jun 11 02:02:00.699 2011 (GMT-4)
System Uptime: 0 days 0:34:16.964
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800401deb0, fffff88005de76d8, fffff88005de6f30}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800401deb0, The address that the exception occurred at
Arg3: fffff88005de76d8, Exception Record Address
Arg4: fffff88005de6f30, Context Record Address

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


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

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c
fffff880`0401deb0 488b16          mov     rdx,qword ptr [rsi]

EXCEPTION_RECORD:  fffff88005de76d8 -- (.exr 0xfffff88005de76d8)
ExceptionAddress: fffff8800401deb0 (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x000000000000041c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88005de6f30 -- (.cxr 0xfffff88005de6f30)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8004576e30 rsi=fffffa8004bd2120 rdi=fffffa8005bd9000
rip=fffff8800401deb0 rsp=fffff88005de7910 rbp=fffffa8004c01368
 r8=fffffa8004ba7a01  r9=0000000000000000 r10=0000000000000000
r11=00000000000001aa r12=0000000000000186 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x41c:
fffff880`0401deb0 488b16          mov     rdx,qword ptr [rsi] ds:002b:fffffa80`04bd2120=fffffa8004aff690
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800037090e0
 ffffffffffffffff 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c
fffff880`0401deb0 488b16          mov     rdx,qword ptr [rsi]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800403865d to fffff8800401deb0

STACK_TEXT:  
fffff880`05de7910 fffff880`0403865d : 00000000`00000000 fffff8a0`106d16b0 fffffa80`00000000 fffffa80`04ba7a30 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x41c
fffff880`05de7ae0 fffff880`04038398 : fffff800`00b96080 fffff880`04037d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05de7cd0 fffff880`04037e96 : 00000000`00000000 fffffa80`06a73350 00000000`00000080 fffffa80`05622410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05de7d00 fffff800`03776166 : 00000000`032d73cf fffffa80`059f9b60 fffffa80`039e9040 fffffa80`059f9b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05de7d40 fffff800`034b1486 : fffff800`0364be80 fffffa80`059f9b60 fffff800`03659c40 fffff880`014182b4 : nt!PspSystemThreadStartup+0x5a
fffff880`05de7d80 00000000`00000000 : fffff880`05de8000 fffff880`05de2000 fffff880`05de7690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

STACK_COMMAND:  .cxr 0xfffff88005de6f30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+41c

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

2: kd> lmvm dxgmms1
start             end                 module name
fffff880`04000000 fffff880`04046000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\99F64A64B8C94E04BB4C7562EDDFA8671\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: C:\Symbols\dxgmms1.sys\4D3FA17446000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Jan 25 23:22:12 2011 (4D3FA174)
    CheckSum:         0004ECED
    ImageSize:        00046000
    File version:     6.1.7600.16748
    Product version:  6.1.7600.16748
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16748
    FileVersion:      6.1.7600.16748 (win7_gdr.110125-1530)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

hgwng · 11 Jun 2011

i uninstalled, ran driver sweeper and reinstalled already. how do i reinstalled directx?

zigzag3143 · 11 Jun 2011

hgwng said:

i uninstalled, ran driver sweeper and reinstalled already. how do i reinstalled directx?

If it is 9 or before Download details: DirectX End-User Runtime Web Installer

hgwng · 11 Jun 2011

Oops, i meant uninstall.