BSoD occur while login pc

Fanyi

New member
Local time
6:45 AM
Messages
4
Hi,

i have just restart pc in a warm boot and it goes BSoD while i login into window.
Could someone please help and check :(
Attached some info file.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
custom build
OS
Window 7 Pro 64bit
The BSOD was caused by some ASUS bloatware.

I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13
13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.
Let us know the result.
____________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800ab00e8c, 0, fffff880091eb988, 2}

*** WARNING: Unable to verify timestamp for IOMap64.sys
*** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys

Could not read faulting driver name
Probably caused by : IOMap64.sys ( IOMap64+1988 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8800ab00e8c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880091eb988, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b8100
GetUlongFromAddress: unable to read from fffff800032b81c0
 fffff8800ab00e8c Nonpaged pool

FAULTING_IP: 
IOMap64+1988
fffff880`091eb988 8b0482          mov     eax,dword ptr [rdx+rax*4]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  GPUTweak.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800a582980 -- (.trap 0xfffff8800a582980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000c03a3 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff8800a800000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880091eb988 rsp=fffff8800a582b10 rbp=fffffa800a691b00
 r8=0000000000000000  r9=fffffa800d09a040 r10=0000000000000001
r11=fffffa800d09a040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
IOMap64+0x1988:
fffff880`091eb988 8b0482          mov     eax,dword ptr [rdx+rax*4] ds:fffff880`0ab00e8c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030fd5e4 to fffff80003080bc0

STACK_TEXT:  
fffff880`0a582818 fffff800`030fd5e4 : 00000000`00000050 fffff880`0ab00e8c 00000000`00000000 fffff880`0a582980 : nt!KeBugCheckEx
fffff880`0a582820 fffff800`0307ecee : 00000000`00000000 fffff880`0ab00e8c fffffa80`20206f00 fffffa80`0cad3cd0 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`0a582980 fffff880`091eb988 : 00000000`20206f49 00000000`00000001 00000000`00000001 00000000`20206f49 : nt!KiPageFault+0x16e
fffff880`0a582b10 00000000`20206f49 : 00000000`00000001 00000000`00000001 00000000`20206f49 fffffa80`0d09a000 : IOMap64+0x1988
fffff880`0a582b18 00000000`00000001 : 00000000`00000001 00000000`20206f49 fffffa80`0d09a000 fffff880`091eb651 : 0x20206f49
fffff880`0a582b20 00000000`00000001 : 00000000`20206f49 fffffa80`0d09a000 fffff880`091eb651 fffffa80`0bffbb30 : 0x1
fffff880`0a582b28 00000000`20206f49 : fffffa80`0d09a000 fffff880`091eb651 fffffa80`0bffbb30 fffff800`03093fbc : 0x1
fffff880`0a582b30 fffffa80`0d09a000 : fffff880`091eb651 fffffa80`0bffbb30 fffff800`03093fbc ffffffff`ffffffff : 0x20206f49
fffff880`0a582b38 fffff880`091eb651 : fffffa80`0bffbb30 fffff800`03093fbc ffffffff`ffffffff 00000000`00000000 : 0xfffffa80`0d09a000
fffff880`0a582b40 fffffa80`0bffbb30 : fffff800`03093fbc ffffffff`ffffffff 00000000`00000000 fffffa80`0d09a040 : IOMap64+0x1651
fffff880`0a582b48 fffff800`03093fbc : ffffffff`ffffffff 00000000`00000000 fffffa80`0d09a040 fffffa80`0cad3de8 : 0xfffffa80`0bffbb30
fffff880`0a582b50 fffff800`0339de67 : fffffa80`0cad3de8 fffffa80`0cf10f20 fffff880`0a582e30 fffffa80`0cad3cd0 : nt!ExAllocatePoolWithQuotaTag+0xbc
fffff880`0a582ba0 fffff800`0339e6c6 : 00000000`0008d200 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0a582cd0 fffff800`0307fe53 : 00000000`72b12450 00000000`0008d2b0 00000000`0008fd20 00000000`7efdb000 : nt!NtDeviceIoControlFile+0x56
fffff880`0a582d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
IOMap64+1988
fffff880`091eb988 8b0482          mov     eax,dword ptr [rdx+rax*4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  IOMap64+1988

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: IOMap64

IMAGE_NAME:  IOMap64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51d28f03

FAILURE_BUCKET_ID:  X64_0x50_IOMap64+1988

BUCKET_ID:  X64_0x50_IOMap64+1988

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_iomap64+1988

FAILURE_ID_HASH:  {df853a00-18b6-da52-21a6-ded611bf8875}

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

2: kd> lmvm IOMap64
start             end                 module name
fffff880`091ea000 fffff880`091f3000   IOMap64  T (no symbols)           
    Loaded symbol image file: IOMap64.sys
    Image path: \??\C:\Windows\system32\drivers\IOMap64.sys
    Image name: IOMap64.sys
    Timestamp:        Tue Jul 02 13:57:47 2013 (51D28F03)
    CheckSum:         00012564
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
Back
Top