W7 BSOD 0x000001e

bokasi · 24 Sep 2010

just ran driver verifier and keep getting bsod's so i had to disable it..

this time i have the dumps though when it crashed with verifier on. (i hope)

strange thing though.. i couldnt get it to pipe the output to verifier.txt when i tried before as a test

Jonathan_King · 25 Sep 2010

Hi there,

Could you please follow these directions?

https://www.sevenforums.com/crashes-d...tructions.html

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a0e50
Debug session time: Fri Sep 24 23:30:01.855 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:13.447
Loading Kernel Symbols
...............................................................
.....................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {6, 2, 0, fffff800030f32b3}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

3: kd> !analyze -v;lmtsmn;.bugcheck;.logclose;q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000006, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800030f32b3, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330b0e0
 0000000000000006 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`030f32b3 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff8e

TRAP_FRAME:  fffff880033a7ae0 -- (.trap 0xfffff880033a7ae0)
.trap 0xfffff880033a7ae0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004f3dbb0 rbx=0000000000000000 rcx=fffffa8004ea3aa8
rdx=fffff70001080034 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000340a8ca rsp=fffff880033a7c70 rbp=0007ffffffffffff
 r8=0000000000000003  r9=0000000000000000 r10=0000000000000000
r11=fffffa8004ea3890 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt! ?? ::NNGAKEGL::`string'+0x1b984:
fffff800`0340a8ca e8c1c2c7ff      call    nt!KiCheckForKernelApcDelivery (fffff800`03086b90)
.trap
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d2ca9 to fffff800030d3740

STACK_TEXT:  
fffff880`033a7528 fffff800`030d2ca9 : 00000000`0000000a 00000000`00000006 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`033a7530 fffff800`030d1920 : 00000000`00000000 fffff980`02714ee0 00000000`00000000 fffff880`033a7710 : nt!KiBugCheckDispatch+0x69
fffff880`033a7670 fffff800`030f32b3 : fffff980`02714ee0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`033a7800 fffff800`030b00c7 : 00000000`00000006 fffff880`00000000 fffff880`033a7900 fffff800`00000000 : nt!IopCompleteRequest+0xae3
fffff880`033a78d0 fffff800`03086bb5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033a7950 fffff800`030eec44 : fffffa80`04ea3890 fffff800`03104381 fffff800`03260440 fffff880`033a7ad0 : nt!KiCheckForKernelApcDelivery+0x25
fffff880`033a7980 fffff800`030d182e : 00000000`00000008 fffffa80`0980d670 fffff680`00000000 00001f80`01083c28 : nt!MmAccessFault+0x1844
fffff880`033a7ae0 fffff800`0340a8ca : 00000000`00000000 00000000`00000000 fffffa80`04ea3890 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`033a7c70 fffff800`033ec5db : 00000000`00000000 00000000`002f0000 fffffa80`00000001 00000000`00000b00 : nt! ?? ::NNGAKEGL::`string'+0x1b984
fffff880`033a7d30 fffff800`030d2993 : 00000000`00000000 00000000`00002e3e fffffa80`04ea3890 00000000`000006c7 : nt!NtUnmapViewOfSection+0x5f
fffff880`033a7d80 fffff800`030cef30 : fffff800`034acb39 00000000`00000000 00000000`002f00f8 00000000`00100000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033a7f18 fffff800`034acb39 : 00000000`00000000 00000000`002f00f8 00000000`00100000 fffff880`033a82d8 : nt!KiServiceLinkage
fffff880`033a7f20 fffff800`034acc7c : ffffffff`80000160 00000000`00100000 00000000`002f0000 ffffffff`8000016c : nt!MmCheckSystemImage+0x319
fffff880`033a8050 fffff800`034ace97 : ffffffff`80000160 00001f80`00000001 fffff880`033a8338 fffff880`033a8200 : nt!MiCreateSectionForDriver+0xcc
fffff880`033a8100 fffff800`034b873a : 00000000`00000000 fffff880`033a82d8 fffffa80`04f3db60 00000000`00000000 : nt!MiObtainSectionForDriver+0xd7
fffff880`033a8160 fffff800`034bb35d : fffff880`033a82d8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23a
fffff880`033a8280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopLoadDriver+0x44d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`030d1920 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260

Followup: MachineOwner

CarlTR6 · 25 Sep 2010

bokasi said:

just ran driver verifier and keep getting bsod's so i had to disable it..

this time i have the dumps though when it crashed with verifier on. (i hope)

strange thing though.. i couldnt get it to pipe the output to verifier.txt when i tried before as a test

One of these dumps is a Driver Verifier enabled dumps. Driver Verifier will trigger a crash and generate a dump when it encounters a faulty driver. Hopefully, the dumps points out the offending driver. Unfortunately, your dump pointed to a Windows core system driver, which is very likely not the cause. This usually indicates a hardware problem. The other dump indicates memory corruption.

bokasi · 27 Sep 2010

Here is the perfmon report and the other stuff..

zigzag3143 · 27 Sep 2010

bokasi said:

Here is the perfmon report and the other stuff..

Hi Bokasi and welcome

10 of 16 crashes point to memory exceptions with your video driver being number one. Even the driver verifier enabled dump has the memory exception.

I think given the number of BSOD's and different causes I would have to start thinking hardware. I would first test your memory

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

I would (if the memory passes) re-install the video driver.

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

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

Then if you are overclocking stop. If you are running a RAID, update its driver.

Most of your drivers are up to date so I wouldnt bother.

Let us know if the crashes continue.

Ken J

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\090710-14086-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03058e50
Debug session time: Tue Sep  7 02:15:44.603 2010 (GMT-4)
System Uptime: 0 days 2:16:36.805
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88002ea350a, fffff88006274a40, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182 )

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

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

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

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::CloseOneAllocation+182
fffff880`02ea350a 48894108        mov     qword ptr [rcx+8],rax

CONTEXT:  fffff88006274a40 -- (.cxr 0xfffff88006274a40)
rax=fffff8a0022fc598 rbx=fffffa8008c9a950 rcx=dffff8a0022fc598
rdx=fffffa8008f7b000 rsi=fffff8a0022276e0 rdi=fffffa8008fa3000
rip=fffff88002ea350a rsp=fffff88006275420 rbp=0000000000000000
 r8=fffffa8008fa43d8  r9=0000000000000001 r10=fffffffffffffffb
r11=fffff880062753f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffff8a00214beb0
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x182:
fffff880`02ea350a 48894108        mov     qword ptr [rcx+8],rax ds:002b:dffff8a0`022fc5a0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88002ea350a

STACK_TEXT:  
fffff880`06275420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x182


FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182
fffff880`02ea350a 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff88006274a40 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182

BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+182

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

bokasi · 28 Sep 2010

just had another crash again after using driver sweeper and reinstalling the gfx driver

i did the memtest before for 8 passes and it was fine with no errors. no overclocking has been done and im not running RAID at all..

i ran furmark too and put the gfx card to a stress test and that was fine too...

Jonathan_King · 28 Sep 2010

Do you have access to another graphics card?

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Lancaster\092810-16052-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03258e50
Debug session time: Mon Sep 27 22:55:43.997 2010 (UTC - 4:00)
System Uptime: 0 days 13:08:26.573
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88010d17986, fffff880064b5d60, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+46 )

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

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

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

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!VidMmDestroyAllocation+46
fffff880`10d17986 49894108        mov     qword ptr [r9+8],rax

CONTEXT:  fffff880064b5d60 -- (.cxr 0xfffff880064b5d60)
.cxr 0xfffff880064b5d60
rax=fffff8a00282aea0 rbx=fffff8a00282aea0 rcx=fffffa8009916000
rdx=fffff8a00106e4e0 rsi=fffff8a00106e4e0 rdi=fefff8a00282aea0
rip=fffff88010d17986 rsp=fffff880064b6730 rbp=fffffa8009916000
 r8=fffff8a00c456a40  r9=fefff8a00282aea0 r10=0000000000000000
r11=fffff880044f5120 r12=fffff8a000d85800 r13=fffff8a009a9f990
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgmms1!VidMmDestroyAllocation+0x46:
fffff880`10d17986 49894108        mov     qword ptr [r9+8],rax ds:002b:fefff8a0`0282aea8=????????????????
.cxr
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88010d17986

STACK_TEXT:  
fffff880`064b6730 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidMmDestroyAllocation+0x46


FOLLOWUP_IP: 
dxgmms1!VidMmDestroyAllocation+46
fffff880`10d17986 49894108        mov     qword ptr [r9+8],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VidMmDestroyAllocation+46

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff880064b5d60 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmDestroyAllocation+46

BUCKET_ID:  X64_0x3B_dxgmms1!VidMmDestroyAllocation+46

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

bokasi · 08 Oct 2010

"Main Bios Check sum error" not sure if this error is related to my current problem.

Not sure if this error appears in the report attached as well, please let me know

thank you

Jonathan_King · 08 Oct 2010

The only thing solid pointed to was your Linksys NIC drivers. Try installing these ones: http://homedownloads.cisco.com/downl...7_3.0.10.0.zip

Please enable driver verifier, if the problem continues: Driver Verifier - Enable and Disable

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 01:38:26.726 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:16.303
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct  7 09:23:29.997 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:46.199
BugCheck 3B, {c0000005, fffff8000308f83e, fffff8800a8d7d10, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopAllocateIrpPrivate+ce )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  IAStorDataMgrS
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 00:35:11.690 2010 (UTC - 4:00)
System Uptime: 0 days 21:13:07.688
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for netr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28ux.sys
Probably caused by : netr28ux.sys ( netr28ux+6755f )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct  4 09:31:48.172 2010 (UTC - 4:00)
System Uptime: 0 days 13:12:56.050
BugCheck 3B, {c0000005, fffff960002a06b9, fffff8800b155770, 0}
Probably caused by : win32k.sys ( win32k!PopThreadGuardedObject+19 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  msnmsgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Oct  3 10:31:03.390 2010 (UTC - 4:00)
System Uptime: 0 days 6:16:15.967
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

bokasi · 14 Oct 2010

I have unplugged my graphic card for 3 days, reinstalled driver for my network adapter, however, i am still getting BSOD and Main BIOS check sum error