BSOD playing EQ2 new nvidia geforce installed


  1. Posts : 4
    Windows 7
       #1

    BSOD playing EQ2 new nvidia geforce installed


    Hi

    I have windows seven and a couple of weeks ago I installed a new NVIDIA GeForce Video card. Starting about 2 days ago my computer crashed to the BSOD randomly while playing EQ2, sometimes it crashed right away sometimes after a couple of hours but it crashes multiple times per day.

    I have tried playing the game in XP mode, I have checked and as far as I can see the onboard video has been disable.

    When I reboot this is what I get when I click on the box to learn about the crash

    BCCode: a
    BCP1: 9BB16ABB
    BCP2: 00000002
    BCP3: 00000000
    BCP4: 83088DE2
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
    Files that help describe the problem:
    C:\Windows\Minidump\010712-12433-01.dmp
    C:\Users\Chris\AppData\Local\Temp\WER-24882-0.sysdata.xml
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Unfortunately, the information provided is a bit vague. Please read and follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information so we may better assist you.
      My Computer


  3. Posts : 4
    Windows 7
    Thread Starter
       #3

    My dump files


    Hi I have uploaded my dump files and Health report, I have named the file Health report. I have also added my system information to my profile. I hope this helps.
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Code:
    1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010412-19546-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83055000 PsLoadedModuleList = 0x8319e4d0 Debug session time: Wed Jan 4 18:15:22.093 2012 (UTC - 7:00) System Uptime: 0 days 2:17:14.544 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {43ee02, 1c, 1, 83023c54} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 0043ee02, memory referenced Arg2: 0000001c, IRQL Arg3: 00000001, 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: 83023c54, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831be848 Unable to read MiSystemVaType memory at 8319de20 0043ee02 CURRENT_IRQL: 1c FAULTING_IP: hal!HalBeginSystemInterrupt+62 83023c54 c20c00 ret 0Ch CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 8317cb9c -- (.trap 0xffffffff8317cb9c) ErrCode = 00000002 eax=0021f701 ebx=8317cd20 ecx=8317cc20 edx=000000d1 esi=dac1eb75 edi=91c973f6 eip=83023c54 esp=8317cc10 ebp=8317cc28 iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 hal!HalBeginSystemInterrupt+0x62: 83023c54 c20c00 ret 0Ch Resetting default scope LAST_CONTROL_TRANSFER: from 83023c54 to 830965fb STACK_TEXT: 8317cb9c 83023c54 badb0d00 000000d1 00000002 nt!KiTrap0E+0x2cf 8317cc28 91c973f6 badb0d00 00000000 00000000 hal!HalBeginSystemInterrupt+0x62 8317cc98 830d537f 85ae02d8 83189380 8317fc00 amdppm!C1Halt+0x4 8317cd20 830cce0d 00000000 0000000e 00000000 nt!PoIdle+0x524 8317cd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 91c973f6 c3 ret SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0xA_amdppm!C1Halt+4 BUCKET_ID: 0xA_amdppm!C1Halt+4 Followup: MachineOwner ---------
    2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010512-21824-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83006000 PsLoadedModuleList = 0x8314f4d0 Debug session time: Thu Jan 5 08:58:10.918 2012 (UTC - 7:00) System Uptime: 0 days 14:42:13.354 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {660ae96d, 1c, 0, 83080ed7} Probably caused by : hardware ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 660ae96d, memory referenced Arg2: 0000001c, IRQL Arg3: 00000000, 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: 83080ed7, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 8316f848 Unable to read MiSystemVaType memory at 8314ee20 660ae96d CURRENT_IRQL: 1c FAULTING_IP: nt!KeUpdateSystemTime+5c1 83080ed7 1283668b0866 adc al,byte ptr [ebx+66088B66h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 8312db4c -- (.trap 0xffffffff8312db4c) ErrCode = 00000000 eax=8312fb70 ebx=00025e07 ecx=00000001 edx=00000000 esi=00000001 edi=8312dbf8 eip=83080ed7 esp=8312dbc0 ebp=8312dc14 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 nt!KeUpdateSystemTime+0x5c1: 83080ed7 1283668b0866 adc al,byte ptr [ebx+66088B66h] ds:0023:660ae96d=?? Resetting default scope MISALIGNED_IP: nt!KeUpdateSystemTime+5c1 83080ed7 1283668b0866 adc al,byte ptr [ebx+66088B66h] LAST_CONTROL_TRANSFER: from 83080ed7 to 830475fb STACK_TEXT: 8312db4c 83080ed7 badb0d00 00000000 00002710 nt!KiTrap0E+0x2cf 8312dc14 83085c17 00000002 00000002 000000d1 nt!KeUpdateSystemTime+0x5c1 8312dc14 9247f3f6 00000002 00000002 000000d1 nt!KeUpdateSystemTimeAssist+0x13 8312dc98 8308637f 85a83030 8313a380 83130c00 amdppm!C1Halt+0x4 8312dd20 8307de0d 00000000 0000000e 00000000 nt!PoIdle+0x524 8312dd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 9247f3f6 c3 ret SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner ---------
    3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010612-24133-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8303a000 PsLoadedModuleList = 0x831834d0 Debug session time: Fri Jan 6 11:22:59.955 2012 (UTC - 7:00) System Uptime: 0 days 1:47:16.391 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 1d, 8, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: 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: 00000000, memory referenced Arg2: 0000001d, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 00000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 831a3848 Unable to read MiSystemVaType memory at 83182e20 00000000 CURRENT_IRQL: 1d FAULTING_IP: +3831376131306165 00000000 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 83161ba0 -- (.trap 0xffffffff83161ba0) ErrCode = 00000010 eax=001c7e01 ebx=83161d20 ecx=83161c20 edx=000000e1 esi=563b09ef edi=91ea63f6 eip=00000000 esp=83161c14 ebp=83161c28 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 00000000 to 8307b5fb FAILED_INSTRUCTION_ADDRESS: +3831376131306165 00000000 ?? ??? STACK_TEXT: 83161ba0 00000000 badb0d00 000000e1 fc6278b0 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 83161c10 8301daa7 83161c28 00000000 00000002 0x0 83161c10 91ea63f6 83161c28 00000000 00000002 hal!HalpIpiHandler+0x14f 83161c98 830ba37f 87c1ad18 8316e380 83164c00 amdppm!C1Halt+0x4 83161d20 830b1e0d 00000000 0000000e 00000000 nt!PoIdle+0x524 83161d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 91ea63f6 c3 ret SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_amdppm!C1Halt+4 BUCKET_ID: 0xD1_CODE_AV_NULL_IP_amdppm!C1Halt+4 Followup: MachineOwner ---------
    4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010612-22791-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83042000 PsLoadedModuleList = 0x8318b4d0 Debug session time: Fri Jan 6 11:54:31.857 2012 (UTC - 7:00) System Uptime: 0 days 0:30:54.293 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {2710, 1c, 1, 8300d811} Probably caused by : hardware ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 00002710, memory referenced Arg2: 0000001c, IRQL Arg3: 00000001, 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: 8300d811, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831ab848 Unable to read MiSystemVaType memory at 8318ae20 00002710 CURRENT_IRQL: 1c FAULTING_IP: hal!Dr_Hpetro_a+4d 8300d811 0000 add byte ptr [eax],al CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 83169bac -- (.trap 0xffffffff83169bac) ErrCode = 00000002 eax=00002710 ebx=00000000 ecx=ff8bcccc edx=000000d1 esi=88f39c6b edi=91ee03f6 eip=8300d811 esp=83169c20 ebp=83169c28 iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 hal!Dr_Hpetro_a+0x4d: 8300d811 0000 add byte ptr [eax],al ds:0023:00002710=?? Resetting default scope MISALIGNED_IP: hal!Dr_Hpetro_a+4d 8300d811 0000 add byte ptr [eax],al LAST_CONTROL_TRANSFER: from 8300d811 to 830835fb STACK_TEXT: 83169bac 8300d811 badb0d00 000000d1 830bcf2b nt!KiTrap0E+0x2cf 83169c28 91ee03f6 badb0d00 00000000 00000000 hal!Dr_Hpetro_a+0x4d 83169c98 830c237f 87f91880 83176380 8316cc00 amdppm!C1Halt+0x4 83169d20 830b9e0d 00000000 0000000e 00000000 nt!PoIdle+0x524 83169d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 91ee03f6 c3 ret SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner ---------
    5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010612-22042-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8301f000 PsLoadedModuleList = 0x831684d0 Debug session time: Fri Jan 6 12:12:24.588 2012 (UTC - 7:00) System Uptime: 0 days 0:17:15.024 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {31ef315a, 1d, 8, 31ef315a} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: 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: 31ef315a, memory referenced Arg2: 0000001d, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 31ef315a, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 83188848 Unable to read MiSystemVaType memory at 83167e20 31ef315a CURRENT_IRQL: 1d FAULTING_IP: +3831376131306165 31ef315a ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 83146ba0 -- (.trap 0xffffffff83146ba0) ErrCode = 00000010 eax=001e3501 ebx=83146d20 ecx=83146c20 edx=000000e1 esi=93eb86bc edi=917063f6 eip=31ef315a esp=83146c14 ebp=83146c28 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 31ef315a ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 31ef315a to 830605fb FAILED_INSTRUCTION_ADDRESS: +3831376131306165 31ef315a ?? ??? STACK_TEXT: 83146ba0 31ef315a badb0d00 000000e1 68ec0990 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 83146c10 8344baa7 83146c28 00000000 8344ba02 0x31ef315a 83146c10 917063f6 83146c28 00000000 8344ba02 hal!HalpIpiHandler+0x14f 83146c98 8309f37f 85d49750 83153380 83149c00 amdppm!C1Halt+0x4 83146d20 83096e0d 00000000 0000000e 00000000 nt!PoIdle+0x524 83146d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 917063f6 c3 ret SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_amdppm!C1Halt+4 BUCKET_ID: 0xD1_CODE_AV_BAD_IP_amdppm!C1Halt+4 Followup: MachineOwner ---------
    6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010612-20904-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8303b000 PsLoadedModuleList = 0x831844d0 Debug session time: Fri Jan 6 12:58:38.997 2012 (UTC - 7:00) System Uptime: 0 days 0:45:16.433 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 1d, 8, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: 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: 00000000, memory referenced Arg2: 0000001d, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 00000000, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 831a4848 Unable to read MiSystemVaType memory at 83183e20 00000000 CURRENT_IRQL: 1d FAULTING_IP: +3831376131306165 00000000 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 83162ba0 -- (.trap 0xffffffff83162ba0) ErrCode = 00000010 eax=00189701 ebx=83162d20 ecx=83162c20 edx=000000e1 esi=90c39538 edi=91ef23f6 eip=00000000 esp=83162c14 ebp=83162c28 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 00000000 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 00000000 to 8307c5fb FAILED_INSTRUCTION_ADDRESS: +3831376131306165 00000000 ?? ??? STACK_TEXT: 83162ba0 00000000 badb0d00 000000e1 531e79f0 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 83162c10 8301eaa7 83162c28 00000000 867ac402 0x0 83162c10 91ef23f6 83162c28 00000000 867ac402 hal!HalpIpiHandler+0x14f 83162c98 830bb37f 87e09030 8316f380 83165c00 amdppm!C1Halt+0x4 83162d20 830b2e0d 00000000 0000000e 00000000 nt!PoIdle+0x524 83162d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 91ef23f6 c3 ret SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0xD1_CODE_AV_NULL_IP_amdppm!C1Halt+4 BUCKET_ID: 0xD1_CODE_AV_NULL_IP_amdppm!C1Halt+4 Followup: MachineOwner ---------
    7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010612-15678-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83053000 PsLoadedModuleList = 0x8319c4d0 Debug session time: Fri Jan 6 19:22:27.718 2012 (UTC - 7:00) System Uptime: 0 days 2:34:16.170 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {d, 0, 0, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8301e69e to 83094d3b STACK_TEXT: 8317abb4 8301e69e badb0d00 0001c257 edd91add nt!KiSystemFatalException+0xf 8317ac28 917e23f6 badb0d00 00000000 00000000 hal!HalpHpetClockInterrupt+0x6a 8317ac98 830d337f 865cd4b8 83187380 8317dc00 amdppm!C1Halt+0x4 8317ad20 830cae0d 00000000 0000000e 00000000 nt!PoIdle+0x524 8317ad24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 917e23f6 c3 ret SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0x7f_d_amdppm!C1Halt+4 BUCKET_ID: 0x7f_d_amdppm!C1Halt+4 Followup: MachineOwner ---------
    8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010712-12433-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8300f000 PsLoadedModuleList = 0x831584d0 Debug session time: Sat Jan 7 08:05:14.103 2012 (UTC - 7:00) System Uptime: 0 days 1:39:22.415 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {9bb16abb, 2, 0, 83088de2} Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+1c4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 9bb16abb, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, 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: 83088de2, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 83178848 Unable to read MiSystemVaType memory at 83157e20 9bb16abb CURRENT_IRQL: 2 FAULTING_IP: nt!KiTimerExpiration+1c4 83088de2 324c243b xor cl,byte ptr [esp+3Bh] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: EverQuest2.exe TRAP_FRAME: 8078aedc -- (.trap 0xffffffff8078aedc) ErrCode = 00000000 eax=85ae1dd8 ebx=8313ce48 ecx=00000001 edx=85bdd828 esi=8313ce4c edi=8313b680 eip=83088de2 esp=8078af50 ebp=8078afac iopl=0 nv up ei ng nz ac pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297 nt!KiTimerExpiration+0x1c4: 83088de2 324c243b xor cl,byte ptr [esp+3Bh] ss:0010:8078af8b=c0 Resetting default scope LAST_CONTROL_TRANSFER: from 83088de2 to 830505fb STACK_TEXT: 8078aedc 83088de2 badb0d00 85bdd828 00000000 nt!KiTrap0E+0x2cf 8078afac 8308700e 0005d4fb 99358d34 00000000 nt!KiTimerExpiration+0x1c4 8078aff4 830867dc 99358ce4 00000000 00000000 nt!KiRetireDpcList+0xcb 8078aff8 99358ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c WARNING: Frame IP not in any known module. Following frames may be wrong. 830867dc 00000000 0000001a 00d6850f bb830000 0x99358ce4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTimerExpiration+1c4 83088de2 324c243b xor cl,byte ptr [esp+3Bh] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiTimerExpiration+1c4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4 FAILURE_BUCKET_ID: 0xA_nt!KiTimerExpiration+1c4 BUCKET_ID: 0xA_nt!KiTimerExpiration+1c4 Followup: MachineOwner ---------
    9. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010712-12854-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83013000 PsLoadedModuleList = 0x8315c4d0 Debug session time: Sat Jan 7 11:10:14.026 2012 (UTC - 7:00) System Uptime: 0 days 2:12:23.478 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {2710, 1c, 1, 834277b1} Probably caused by : hardware ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: 00002710, memory referenced Arg2: 0000001c, IRQL Arg3: 00000001, 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: 834277b1, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8317c848 Unable to read MiSystemVaType memory at 8315be20 00002710 CURRENT_IRQL: 1c FAULTING_IP: hal!HalpHpetClockInterrupt+17d 834277b1 0100 add dword ptr [eax],eax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 8313abac -- (.trap 0xffffffff8313abac) ErrCode = 00000002 eax=00002710 ebx=00000000 ecx=00000000 edx=000000d1 esi=1c84e782 edi=918223f6 eip=834277b1 esp=8313ac20 ebp=8313ac28 iopl=0 nv up ei ng nz ac pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297 hal!HalpHpetClockInterrupt+0x17d: 834277b1 0100 add dword ptr [eax],eax ds:0023:00002710=???????? Resetting default scope MISALIGNED_IP: hal!HalpHpetClockInterrupt+17d 834277b1 0100 add dword ptr [eax],eax LAST_CONTROL_TRANSFER: from 834277b1 to 830545fb STACK_TEXT: 8313abac 834277b1 badb0d00 000000d1 8308df2b nt!KiTrap0E+0x2cf 8313ac28 918223f6 badb0d00 00000000 00000000 hal!HalpHpetClockInterrupt+0x17d 8313ac98 8309337f 85e08a00 83147380 8313dc00 amdppm!C1Halt+0x4 8313ad20 8308ae0d 00000000 0000000e 00000000 nt!PoIdle+0x524 8313ad24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 918223f6 c3 ret SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner ---------
    10. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010712-11559-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83004000 PsLoadedModuleList = 0x8314d4d0 Debug session time: Sat Jan 7 12:31:53.059 2012 (UTC - 7:00) System Uptime: 0 days 1:20:39.510 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {d, 0, 0, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 1d LAST_CONTROL_TRANSFER: from cdc47490 to 83045d3b STACK_TEXT: 8312bba0 cdc47490 badb0d00 000000e1 449268b0 nt!KiSystemFatalException+0xf WARNING: Frame IP not in any known module. Following frames may be wrong. 8312bc10 83430aa7 8312bc28 00000000 83430a02 0xcdc47490 8312bc10 917ec3f6 8312bc28 00000000 83430a02 hal!HalpIpiHandler+0x14f 8312bc98 8308437f 85904948 83138380 8312ec00 amdppm!C1Halt+0x4 8312bd20 8307be0d 00000000 0000000e 00000000 nt!PoIdle+0x524 8312bd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 917ec3f6 c3 ret SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0x7f_d_amdppm!C1Halt+4 BUCKET_ID: 0x7f_d_amdppm!C1Halt+4 Followup: MachineOwner ---------
    11. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\axlwwrose\Windows_NT6_BSOD_jcgriff2\010712-10732-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x83038000 PsLoadedModuleList = 0x831814d0 Debug session time: Sat Jan 7 16:42:46.273 2012 (UTC - 7:00) System Uptime: 0 days 0:34:49.709 Loading Kernel Symbols ............................................................... ................................................................ .......... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {1c, 2, 8, 1c} Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf ) Followup: MachineOwner --------- 0: 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: 0000001c, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: 0000001c, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 831a1848 Unable to read MiSystemVaType memory at 83180e20 0000001c CURRENT_IRQL: 2 FAULTING_IP: +3831376131306165 0000001c ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 8315fbb0 -- (.trap 0xffffffff8315fbb0) ErrCode = 00000010 eax=83163000 ebx=8315fd20 ecx=00000001 edx=00000000 esi=a349e06c edi=9182e3f6 eip=0000001c esp=8315fc24 ebp=8300372a iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 0000001c ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from 0000001c to 830795fb FAILED_INSTRUCTION_ADDRESS: +3831376131306165 0000001c ?? ??? STACK_TEXT: 8315fbb0 0000001c badb0d00 00000000 9182e3f6 nt!KiTrap0E+0x2cf WARNING: Frame IP not in any known module. Following frames may be wrong. 8315fc20 00000000 8315fd20 9182e3f6 badb0d00 0x1c STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+2cf 830795fb 833d44c7198300 cmp dword ptr [nt!KiFreezeFlag (8319c744)],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap0E+2cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4 FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+2cf BUCKET_ID: 0xD1_CODE_AV_BAD_IP_nt!KiTrap0E+2cf Followup: MachineOwner ---------
    Update the following drivers first (see Driver Reference and Manufacturers).
    Code:
    ASACPI	9183e000	9183f420	Thu Aug 12 20:52:52 2004 (411c2d04)	00004aa7		ASACPI.sys
    nvm62x32	918f2000	91946c80	Fri Oct 17 15:00:39 2008 (48f8fcf7)	000610af		nvm62x32.sys
    ASACPI.SYS is a known BSOD problem on Windows 7. Update the driver by:
    1. Going to the Asus motherboard support site
    When you reach the website:
    2. Scroll down the page and click Utilities
    3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
    4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
    5. Download and install the driver.
    6. After installation is complete, verify that it installed correctly.
    a. Click Start Menu
    b. Click My Computer
    c. Go to C:\WIndows\System32\drivers\
    d. Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

    Thanks to JMH and zigzag3143 for the above information.

    Also, if you are overclocking anything, stop! Reset BIOS to default settings and turn off any overclocking within its appropriate software within Windows.
      My Computer


  5. Posts : 4
    Windows 7
    Thread Starter
       #5

    Thanks, how do I know if I'm overclocking?
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #6

    axlwwrose said:
    Thanks, how do I know if I'm overclocking?
    You would know if you were because you would have had to set it up. There are some programs that do it automatically, but I did not see them in your report, so you should be fine.
      My Computer


  7. Posts : 4
    Windows 7
    Thread Starter
       #7

    EQ2 Client Application has stopped working


    Thank you for your help I was able to successfully download and install an updated version of ASACPI.SYS I could not find a newer verson of the nvm62x32.

    Anyway I was able to play EQ2 for quite a while after fixing this problem, however now I get an EQ2 Client Application has stopped working error and my comp freezes.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    If you still need help with the problem in your latest post, please provide us with your Event Viewer administrative logs by following these steps:
    1. Click Start Menu
    2. Type eventvwr into Search programs and files (do not hit enter)
    3. Right click eventvwr.exe and click Run as administrator
    4. Expand Custom Views
    5. Click Administrative Events
    6. Right click Administrative Events
    7. Save all Events in Custom View As...
    8. Save them in a folder where you will remember which folder and save as Errors.evtx
    9. Go to where you saved Errors.evtx
    10. Right click Errors.evtx -> send to -> compressed (zipped) folder
    11. Upload the .zip file here.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:27.
Find Us