Firstly, I am glad that I found you, in my country we used to say well I came :))
now the problem...
I'm enthusiastic to figure out some problems, and I'm a little old to start from the beginning to learn about the subject BOSD...so I need help of experts ...
going up randomly, sometimes during the day, sometimes once a week ...blue screen comes on more often.
Windows 7 ultimate x64 (with all updates)
System Spec already filed
Gigabyte GA-EP35C-DS3R
OCZ Gold XTC OCZ3G13331G 2x1gb
Sapphire Radeon HD 3870 512MB GDDR4
The major contributor to these crashes is the nlndis.sys (netlimiter driver). Remove it to test.
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\102910-22573-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`0328ee50
Debug session time: Fri Oct 29 06:09:40.149 2010 (GMT-4)
System Uptime: 0 days 23:41:38.663
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image nlndis.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nlndis.sys
*** ERROR: Module load completed but symbols could not be loaded for nlndis.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffffa8005195bc2, fffff880039ee968, fffff880039ee1d0}
Probably caused by : nlndis.sys ( nlndis+19b0 )
Followup: MachineOwner
---------
0: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffffa8005195bc2, The address that the exception occurred at
Arg3: fffff880039ee968, Exception Record Address
Arg4: fffff880039ee1d0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
+19b0
fffffa80`05195bc2 16 ???
EXCEPTION_RECORD: fffff880039ee968 -- (.exr 0xfffff880039ee968)
ExceptionAddress: fffffa8005195bc2
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880039ee1d0 -- (.cxr 0xfffff880039ee1d0)
rax=0000000000000000 rbx=fffffa80050a7cb0 rcx=fffffa80050a7cb0
rdx=fffffa80050a7cb0 rsi=fffff880039eec68 rdi=fffffa80050a5650
rip=fffffa8005195bc2 rsp=fffff880039eeba8 rbp=0000000000000001
r8=0000000000000001 r9=fffffa80050a7cb0 r10=0000000000000002
r11=fffffa80050a5550 r12=0000000000000002 r13=fffffa80050a7c40
r14=fffffa8004d75100 r15=0000000000000002
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
fffffa80`05195bc2 16 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER: from fffff88005c6d9b0 to fffffa8005195bc2
FAILED_INSTRUCTION_ADDRESS:
+19b0
fffffa80`05195bc2 16 ???
STACK_TEXT:
fffff880`039eeba8 fffff880`05c6d9b0 : 00000000`00000001 fffffa80`051677f0 fffffa80`050a7cb0 00000000`00000000 : 0xfffffa80`05195bc2
fffff880`039eebb0 00000000`00000001 : fffffa80`051677f0 fffffa80`050a7cb0 00000000`00000000 fffffa80`04d941a0 : nlndis+0x19b0
fffff880`039eebb8 fffffa80`051677f0 : fffffa80`050a7cb0 00000000`00000000 fffffa80`04d941a0 fffff880`0193fbe0 : 0x1
fffff880`039eebc0 fffffa80`050a7cb0 : 00000000`00000000 fffffa80`04d941a0 fffff880`0193fbe0 00000000`00000000 : 0xfffffa80`051677f0
fffff880`039eebc8 00000000`00000000 : fffffa80`04d941a0 fffff880`0193fbe0 00000000`00000000 fffffa80`050a7cb0 : 0xfffffa80`050a7cb0
FOLLOWUP_IP:
nlndis+19b0
fffff880`05c6d9b0 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nlndis+19b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nlndis
IMAGE_NAME: nlndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c779fad
STACK_COMMAND: .cxr 0xfffff880039ee1d0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_nlndis+19b0
BUCKET_ID: X64_0x7E_BAD_IP_nlndis+19b0
Followup: MachineOwner
---------
0: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffffa8005195bc2, The address that the exception occurred at
Arg3: fffff880039ee968, Exception Record Address
Arg4: fffff880039ee1d0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
+19b0
fffffa80`05195bc2 16 ???
EXCEPTION_RECORD: fffff880039ee968 -- (.exr 0xfffff880039ee968)
ExceptionAddress: fffffa8005195bc2
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880039ee1d0 -- (.cxr 0xfffff880039ee1d0)
rax=0000000000000000 rbx=fffffa80050a7cb0 rcx=fffffa80050a7cb0
rdx=fffffa80050a7cb0 rsi=fffff880039eec68 rdi=fffffa80050a5650
rip=fffffa8005195bc2 rsp=fffff880039eeba8 rbp=0000000000000001
r8=0000000000000001 r9=fffffa80050a7cb0 r10=0000000000000002
r11=fffffa80050a5550 r12=0000000000000002 r13=fffffa80050a7c40
r14=fffffa8004d75100 r15=0000000000000002
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
fffffa80`05195bc2 16 ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER: from fffff88005c6d9b0 to fffffa8005195bc2
FAILED_INSTRUCTION_ADDRESS:
+19b0
fffffa80`05195bc2 16 ???
STACK_TEXT:
fffff880`039eeba8 fffff880`05c6d9b0 : 00000000`00000001 fffffa80`051677f0 fffffa80`050a7cb0 00000000`00000000 : 0xfffffa80`05195bc2
fffff880`039eebb0 00000000`00000001 : fffffa80`051677f0 fffffa80`050a7cb0 00000000`00000000 fffffa80`04d941a0 : nlndis+0x19b0
fffff880`039eebb8 fffffa80`051677f0 : fffffa80`050a7cb0 00000000`00000000 fffffa80`04d941a0 fffff880`0193fbe0 : 0x1
fffff880`039eebc0 fffffa80`050a7cb0 : 00000000`00000000 fffffa80`04d941a0 fffff880`0193fbe0 00000000`00000000 : 0xfffffa80`051677f0
fffff880`039eebc8 00000000`00000000 : fffffa80`04d941a0 fffff880`0193fbe0 00000000`00000000 fffffa80`050a7cb0 : 0xfffffa80`050a7cb0
FOLLOWUP_IP:
nlndis+19b0
fffff880`05c6d9b0 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nlndis+19b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nlndis
IMAGE_NAME: nlndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c779fad
STACK_COMMAND: .cxr 0xfffff880039ee1d0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_nlndis+19b0
BUCKET_ID: X64_0x7E_BAD_IP_nlndis+19b0
Followup: MachineOwner
---------
You should also remove any HD virtualization software.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
Quote