BSOD, after signin into user.

JMH · 18 Feb 2012

Keep us posted please.

a77wolves · 30 Mar 2012

Its happen more now.

writhziden · 31 Mar 2012

Possible out of date drivers:

Code:

VMNetSrv	fffff880`0582a000	fffff880`0583f000	Wed Jan 24 05:05:46 2007 (45b74b9a)	0001712b		VMNetSrv.sys
vmm	fffff880`04398000	fffff880`043e5000	Sun Feb 18 01:11:21 2007 (45d80a29)	0004b4b7		vmm.sys

If you fill in your system specs by following System Info - See Your System Specs, we can help you find those drivers. For now, the best we can do is:
VMNetSrv.sys
vmm.sys
The https://www.sevenforums.com/crashes-d...tructions.html may also help.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\a77wolves\033012-38282-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 Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eace90
Debug session time: Fri Mar 30 14:29:51.210 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:59.739
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 6c6c, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46585 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000006c6c
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TERA-Launcher.

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800bb64900 -- (.trap 0xfffff8800bb64900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000006c6c rbx=0000000000000000 rcx=0000000000000002
rdx=0720000000000003 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d06478 rsp=fffff8800bb64a90 rbp=fffff8800bb64b40
 r8=fffff8800bb64b98  r9=fffff6fb40001d90 r10=fffff680003b2398
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiCheckVirtualAddress+0xc8:
fffff800`02d06478 488b08          mov     rcx,qword ptr [rax] ds:4af0:00000000`00006c6c=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7a62e to fffff80002ce7640

STACK_TEXT:  
fffff880`0bb64798 fffff800`02c7a62e : 00000000`0000001a 00000000`00041287 00000000`00006c6c 00000000`00000000 : nt!KeBugCheckEx
fffff880`0bb647a0 fffff800`02ce576e : 00000000`00000000 00000000`00006c6c fffffa80`08847a00 fffffa80`06a1a230 : nt! ?? ::FNODOBFM::`string'+0x46585
fffff880`0bb64900 fffff800`02d06478 : fffffa80`082dcaa0 ffffffff`ffffffff 00000000`00000000 fffff880`0bb64b40 : nt!KiPageFault+0x16e
fffff880`0bb64a90 fffff800`02cf4869 : 00000000`00000000 00000000`00000000 fffff880`0bb64c20 fffff680`00006180 : nt!MiCheckVirtualAddress+0xc8
fffff880`0bb64ac0 fffff800`02ce576e : 00000000`00000008 00000000`76473529 00000000`001de201 00000000`00000000 : nt!MmAccessFault+0x249
fffff880`0bb64c20 00000000`76473529 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018ee70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76473529


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46585
fffff800`02c7a62e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46585

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46585

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

Possible causes are Memory problems... Drivers...

If you are overclocking any hardware, please stop.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
- Click the Start Menu
- Type verifier in Search programs and files (do not hit enter)
- Right click verifier and click Run as administrator
- Put a tick in Create custom settings (for code developers) and click next
- Put a tick in Select individual settings from a full list and click next
- Set up the individual settings as in the image and click next
  Attachment 205148
- Put a tick in Select driver names from a list
- Put a tick next to all non-Microsoft drivers.
- Click Finish.
- Restart your computer.
If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

a77wolves · 31 Mar 2012

I have posted my specs

writhziden · 31 Mar 2012

Thank you, that will make it easier to provide help as we go along. :) Proceed with the memory testing and Verifier steps and post back any new crash reports once you've experienced a few crashes.