One suggestion: please be patient.
Security Software (this is just to check that you have security software and it is working properly; nothing needs to be done with this at this time):
Code:
avgcsrva.exe c:\program files (x86)\avg\avg2012\avgcsrva.exe 524 8 200 1380 3/31/2012 11:49 AM 12.0.0.1786 507.34 KB (519,520 bytes) 8/15/2011 6:21 AM
avgidsagent.exe c:\program files (x86)\avg\avg2012\avgidsagent.exe 2804 8 200 1380 3/31/2012 11:50 AM 12.0.0.1855 4.23 MB (4,433,248 bytes) 10/12/2011 6:25 AM
avgnsa.exe c:\program files (x86)\avg\avg2012\avgnsa.exe 2300 8 200 1380 3/31/2012 11:49 AM 12.0.0.1883 1.90 MB (1,987,424 bytes) 9/13/2011 10:33 AM
avgtray.exe c:\program files (x86)\avg\avg2012\avgtray.exe 3456 8 200 1380 3/31/2012 11:50 AM 12.0.0.1912 2.30 MB (2,416,480 bytes) 1/24/2012 5:24 PM
avgwdsvc.exe c:\program files (x86)\avg\avg2012\avgwdsvc.exe 1080 8 200 1380 3/31/2012 11:49 AM 12.0.0.1773 188.26 KB (192,776 bytes) 8/2/2011 6:09 AM
Possible out of date driver:
Code:
LVUSBS64 fffff880`06d0e000 fffff880`06d18980 Thu Oct 11 19:39:40 2007 (470ed05c) 0001c010 LVUSBS64.sys
LVUSBS64.sys
Code:
-
Loading Dump File [D:\Kingston\BSODDmpFiles\angeloberdugo13\Windows_NT6_BSOD_jcgriff2\033112-23634-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03648650
Debug session time: Fri Mar 30 20:18:18.524 2012 (UTC - 6:00)
System Uptime: 0 days 3:58:39.820
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff800045fa760, 2, 0, fffff8000357061a}
Probably caused by : ntkrnlmp.exe ( nt!PpmPerfRecordUtility+2a )
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: fffff800045fa760, 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: fffff8000357061a, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b2100
fffff800045fa760
CURRENT_IRQL: 2
FAULTING_IP:
nt!PpmPerfRecordUtility+2a
fffff800`0357061a 4c8ba1e0480000 mov r12,qword ptr [rcx+48E0h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff80004ccf140 -- (.trap 0xfffff80004ccf140)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800035f5e80 rbx=0000000000000000 rcx=fffff800035f5e80
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000357061a rsp=fffff80004ccf2d0 rbp=fffffa8007788650
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=fffff80004ccf338 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!PpmPerfRecordUtility+0x2a:
fffff800`0357061a 4c8ba1e0480000 mov r12,qword ptr [rcx+48E0h] ds:fffff800`035fa760=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034802e9 to fffff80003480d40
STACK_TEXT:
fffff800`04cceff8 fffff800`034802e9 : 00000000`0000000a fffff800`045fa760 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`04ccf000 fffff800`0347ef60 : 00000000`00000000 fffffa80`0bac7010 fffff800`04ccf3d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04ccf140 fffff800`0357061a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff800`04ccf2d0 fffff800`03570a1b : fffff800`00000000 fffff880`0f5a30d6 fffff800`04ccf400 fffffa80`0abe7000 : nt!PpmPerfRecordUtility+0x2a
fffff800`04ccf340 fffff800`03531cac : 00000000`00000000 00000000`00100100 fffff800`035f5e80 fffff800`04ccf4c0 : nt!PpmCheckRecordAllUtility+0xfb
fffff800`04ccf3d0 fffff800`035715a0 : 00000000`002e16db fffff800`04ccf4c0 00000000`00000202 fffff800`0348642a : nt!PpmCheckRun+0x8c
fffff800`04ccf400 fffff800`0348ba6c : fffff800`00000010 fffff800`00000000 00000002`40ab0000 00000000`00000004 : nt!PpmCheckStart+0x40
fffff800`04ccf430 fffff800`0348b906 : fffffa80`0d07dc68 fffffa80`0d07dc68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04ccf4a0 fffff800`0348b7ee : 00000021`57473254 fffff800`04ccfb18 00000000`000e01ab fffff800`035f97e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04ccfaf0 fffff800`0348b5d7 : 0000000a`122c20c4 0000000a`000e01ab 0000000a`122c2078 00000000`000000aa : nt!KiTimerExpiration+0x1be
fffff800`04ccfb90 fffff800`03478a6a : fffff800`035f5e80 fffff800`03603cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04ccfc40 00000000`00000000 : fffff800`04cd0000 fffff800`04cca000 fffff800`04ccfc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PpmPerfRecordUtility+2a
fffff800`0357061a 4c8ba1e0480000 mov r12,qword ptr [rcx+48E0h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!PpmPerfRecordUtility+2a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2
FAILURE_BUCKET_ID: X64_0xA_nt!PpmPerfRecordUtility+2a
BUCKET_ID: X64_0xA_nt!PpmPerfRecordUtility+2a
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\angeloberdugo13\Windows_NT6_BSOD_jcgriff2\032712-53102-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0340c000 PsLoadedModuleList = 0xfffff800`03650650
Debug session time: Mon Mar 26 20:17:05.133 2012 (UTC - 6:00)
System Uptime: 0 days 6:31:38.039
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {471a835c, 2, 0, fffff8801016369f}
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1669f )
Followup: MachineOwner
---------
2: 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: 00000000471a835c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8801016369f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ba100
00000000471a835c
CURRENT_IRQL: 2
FAULTING_IP:
Rt64win7+1669f
fffff880`1016369f 33c0 xor eax,eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800339a670 -- (.trap 0xfffff8800339a670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000024 rbx=0000000000000000 rcx=fffffa800afb2868
rdx=0000000000000077 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8801016369f rsp=fffff8800339a800 rbp=0000000000000000
r8=0000000000003fff r9=0000000000000000 r10=fffff88005a6a940
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
Rt64win7+0x1669f:
fffff880`1016369f 33c0 xor eax,eax
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034882e9 to fffff80003488d40
STACK_TEXT:
fffff880`0339a528 fffff800`034882e9 : 00000000`0000000a 00000000`471a835c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0339a530 fffff800`03486f60 : fffffa80`0b1d3402 00000000`00000002 00000000`00000000 fffffa80`0afaf000 : nt!KiBugCheckDispatch+0x69
fffff880`0339a670 fffff880`1016369f : fffffa80`0afaf000 00000000`00000001 fffffa80`0afb2868 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0339a800 fffffa80`0afaf000 : 00000000`00000001 fffffa80`0afb2868 00000000`00000000 00000000`00000001 : Rt64win7+0x1669f
fffff880`0339a808 00000000`00000001 : fffffa80`0afb2868 00000000`00000000 00000000`00000001 00000000`00000006 : 0xfffffa80`0afaf000
fffff880`0339a810 fffffa80`0afb2868 : 00000000`00000000 00000000`00000001 00000000`00000006 00000000`2ace3402 : 0x1
fffff880`0339a818 00000000`00000000 : 00000000`00000001 00000000`00000006 00000000`2ace3402 ffff0000`00000000 : 0xfffffa80`0afb2868
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+1669f
fffff880`1016369f 33c0 xor eax,eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Rt64win7+1669f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ecd0a98
FAILURE_BUCKET_ID: X64_0xD1_Rt64win7+1669f
BUCKET_ID: X64_0xD1_Rt64win7+1669f
Followup: MachineOwner
---------
- Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
- Caused by your Ethernet driver.
Re-install or install the latest Ethernet driver from MSI Global ? Mainboard - H67MA-E45 -> Win7 64 -> Realtek PCI-E Ethernet Drivers and see if it resolves the problem. Your driver is either outdated or corrupted. Also, install/re-install the Realtek High Definition Audio Driver since they use the same resources. Either one being corrupted or out of date could cause the problem in your second crash.