Help me plzzz... BSOD Windows 7 x64

yamamma · 16 Jan 2011

Hi,
i'm still new in using windows 7... juz building a new system/PC.... but recently, my windows 7 x64 always bluescreen error especially when I try to play STAR WARS: Force Unleashed 2 and Pro Evo Soccer 2011. this are the msg that i got after recover from it.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002DBEA4A
BCP3: FFFFF880021ABFE0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011711-20857-01.dmp
C:\Users\******\AppData\Local\Temp\WER-36785-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

*Please help me to encounter this problem. I also attached the .dmp file. Really hope that there is somebody can give me solutions.

yamamma · 17 Jan 2011

This is the latest BSOD that i got....

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041287
BCP2: 0000000000000030
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011711-33665-01.dmp
C:\Users\******\AppData\Local\Temp\WER-48391-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

*Please somebody help me.... I'm total lost here....~

wish · 17 Jan 2011

Hi,
For troubleshooting purpose, I would recommend you to uninstall Avast and replace it with MSE.
You may go back to Avast after the BSOD problem have gone.
http://www.microsoft.com/security_essentials/

Then update this driver:
L1C62x64.sys Wed Oct 21 02:11:29 2009 → Atheros L1c PCI-E Gigabit Ethernet
cpuz_x64.sys Tue Oct 07 12:44:27 2008 → CPU-Z

Make sure to do the suggestion above. If the problem persist then test your RAM:
RAM - Test with Memtest86+

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02816000 PsLoadedModuleList = 0xfffff800`02a53e50
Debug session time: Sat Jan 15 21:38:21.647 2011 (GMT-8)
System Uptime: 0 days 1:25:27.937
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800028a940b, fffff8800733cf80, 0}

Probably caused by : hardware ( nt!RtlFindClearBits+2bb )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800028a940b, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800733cf80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nt!RtlFindClearBits+2bb
fffff800`028a940b 0000            add     byte ptr [rax],al

CONTEXT:  fffff8800733cf80 -- (.cxr 0xfffff8800733cf80)
rax=000000000000005f rbx=0000000000001800 rcx=0000000000000147
rdx=0000000000008000 rsi=0000000000000147 rdi=0000000000000000
rip=fffff800028a940b rsp=fffff8800733d950 rbp=0000000000000200
 r8=00000000000017c7  r9=fffff70000000d00 r10=fffff70000000328
r11=0000000000006800 r12=fffff70000000000 r13=fffff70000000000
r14=8000000000000000 r15=0000000000000147
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!RtlFindClearBits+0x2bb:
fffff800`028a940b 0000            add     byte ptr [rax],al ds:002b:00000000`0000005f=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!RtlFindClearBits+2bb
fffff800`028a940b 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800028a940b

STACK_TEXT:  
fffff880`0733d950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlFindClearBits+0x2bb


FOLLOWUP_IP: 
nt!RtlFindClearBits+2bb
fffff800`028a940b 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!RtlFindClearBits+2bb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800733cf80 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

yamamma · 17 Jan 2011

Okay then.... I will try it first.... thx for the reply... really appreciate that... at least hav some idea to workaround...... will give feedback afterward....~:)

yamamma · 17 Jan 2011

The latest that i've got is blue screen saying MEMORY_MANAGEMENT (while playing games)..... then in cmos screen it try to lower my DRAM from 1333 to 1066..... stuck in starting windows screen and went back to cmos screen, lower DRAM from 1066 to 800..... then I try get into bios to change back to default..... and do the MEMTEST86+..... and got stuck in the middle of scanning.

SO, I turn my PC "off" manually...... just leave it for a while.... and turn it ON back... and did the MEMTEST86+ again... but this time, it passed the scanning with no errors........ (Weird for me...)

Now, i'm in windows just stop playing games coz got tired of the BSOD....

My question is.... Is it becoz of the motherboard itself that cannot manage the memory properly(from my thinking = bios).... or have problem with the RAM itself.....???

wish · 17 Jan 2011

yamamma said:

The latest that i've got is blue screen saying MEMORY_MANAGEMENT (while playing games)..... then in cmos screen it try to lower my DRAM from 1333 to 1066..... stuck in starting windows screen and went back to cmos screen, lower DRAM from 1066 to 800..... then I try get into bios to change back to default..... and do the MEMTEST86+..... and got stuck in the middle of scanning.

SO, I turn my PC "off" manually...... just leave it for a while.... and turn it ON back... and did the MEMTEST86+ again... but this time, it passed the scanning with no errors........ (Weird for me...)

Now, i'm in windows just stop playing games coz got tired of the BSOD....

My question is.... Is it becoz of the motherboard itself that cannot manage the memory properly(from my thinking = bios).... or have problem with the RAM itself.....???

Yes, there is a possibility that your motherboard is defect.
Load setup Bios into factory default.
Then set auto settings for the RAM timing and voltage.

yamamma · 18 Jan 2011

Just got back from PC shop that i bought all the stuff... for warranty claim... but when they made the troubleshooting.... everything was fine... no BSOD... so no warranty claiming for me.... hhhmmm.... then after do all the Windows re-Installation..... and install all the drivers..... while watching youtube.... i got another BSOD.... and the msg are like this:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFFA804D36E1F4
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF880049F6770
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011911-25365-01.dmp
C:\Users\Ya Mamma\AppData\Local\Temp\WER-46394-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

* Did I make any mistakes while installing the drivers..... wonder why is this happening.....~ (really2 feelin' down right now.... new system/PC with a lot of BSOD)

zigzag3143 · 18 Jan 2011

yamamma said:

Just got back from PC shop that i bought all the stuff... for warranty claim... but when they made the troubleshooting.... everything was fine... no BSOD... so no warranty claiming for me.... hhhmmm.... then after do all the Windows re-Installation..... and install all the drivers..... while watching youtube.... i got another BSOD.... and the msg are like this:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: FFFFFA804D36E1F4
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF880049F6770
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\011911-25365-01.dmp
C:\Users\Ya Mamma\AppData\Local\Temp\WER-46394-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

* Did I make any mistakes while installing the drivers..... wonder why is this happening.....~ (really2 feelin' down right now.... new system/PC with a lot of BSOD)

This one was caused by your video driver use these to remove completely and re-install a fresh copy

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

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\latest minidump\011911-25365-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02850000 PsLoadedModuleList = 0xfffff800`02a8de50
Debug session time: Tue Jan 18 12:09:33.218 2011 (GMT-5)
System Uptime: 0 days 4:23:00.998
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa804d36e1f4, 2, 1, fffff880049f6770}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+3cd770 )

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: fffffa804d36e1f4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880049f6770, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af80e0
 fffffa804d36e1f4 

CURRENT_IRQL:  2

FAULTING_IP: 
atikmdag+3cd770
fffff880`049f6770 48895c2410      mov     qword ptr [rsp+10h],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003bf4390 -- (.trap 0xfffff88003bf4390)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005dc3a40 rbx=0000000000000000 rcx=fffffa800526bd98
rdx=fffffa8003ed7040 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880049f6770 rsp=fffff88003bf4528 rbp=fffffa8003ed7040
 r8=fffff88007cc7400  r9=0000000000000001 r10=fffff88004b050d0
r11=fffff88004b050d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
atikmdag+0x3cd770:
fffff880`049f6770 48895c2410      mov     qword ptr [rsp+10h],rbx ss:0018:fffff880`03bf4538=fffff880049c5974
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028c1469 to fffff800028c1f00

STACK_TEXT:  
fffff880`03bf4248 fffff800`028c1469 : 00000000`0000000a fffffa80`4d36e1f4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03bf4250 fffff800`028c00e0 : fffff880`02d63180 fffffa80`0526a020 fffff800`028cebac 00001f80`00000211 : nt!KiBugCheckDispatch+0x69
fffff880`03bf4390 fffff880`049f6770 : fffff880`049dd8d1 fffffa80`03ed7040 fffff880`049c5974 00000000`00000001 : nt!KiPageFault+0x260
fffff880`03bf4528 fffff880`049dd8d1 : fffffa80`03ed7040 fffff880`049c5974 00000000`00000001 fffff880`03bf4830 : atikmdag+0x3cd770
fffff880`03bf4530 fffffa80`03ed7040 : fffff880`049c5974 00000000`00000001 fffff880`03bf4830 fffffa80`05dc3a40 : atikmdag+0x3b48d1
fffff880`03bf4538 fffff880`049c5974 : 00000000`00000001 fffff880`03bf4830 fffffa80`05dc3a40 fffffa80`0526a020 : 0xfffffa80`03ed7040
fffff880`03bf4540 00000000`00000001 : fffff880`03bf4830 fffffa80`05dc3a40 fffffa80`0526a020 fffff880`07cc7400 : atikmdag+0x39c974
fffff880`03bf4548 fffff880`03bf4830 : fffffa80`05dc3a40 fffffa80`0526a020 fffff880`07cc7400 fffff880`049c60e1 : 0x1
fffff880`03bf4550 fffffa80`05dc3a40 : fffffa80`0526a020 fffff880`07cc7400 fffff880`049c60e1 00000000`00000009 : 0xfffff880`03bf4830
fffff880`03bf4558 fffffa80`0526a020 : fffff880`07cc7400 fffff880`049c60e1 00000000`00000009 fffff880`03bf4670 : 0xfffffa80`05dc3a40
fffff880`03bf4560 fffff880`07cc7400 : fffff880`049c60e1 00000000`00000009 fffff880`03bf4670 fffffa80`0526a020 : 0xfffffa80`0526a020
fffff880`03bf4568 fffff880`049c60e1 : 00000000`00000009 fffff880`03bf4670 fffffa80`0526a020 fffff880`07cc7000 : 0xfffff880`07cc7400
fffff880`03bf4570 00000000`00000009 : fffff880`03bf4670 fffffa80`0526a020 fffff880`07cc7000 fffffa80`05dc3a40 : atikmdag+0x39d0e1
fffff880`03bf4578 fffff880`03bf4670 : fffffa80`0526a020 fffff880`07cc7000 fffffa80`05dc3a40 00000000`00000000 : 0x9
fffff880`03bf4580 fffffa80`0526a020 : fffff880`07cc7000 fffffa80`05dc3a40 00000000`00000000 fffffa80`03ed7040 : 0xfffff880`03bf4670
fffff880`03bf4588 fffff880`07cc7000 : fffffa80`05dc3a40 00000000`00000000 fffffa80`03ed7040 00000000`00000001 : 0xfffffa80`0526a020
fffff880`03bf4590 fffffa80`05dc3a40 : 00000000`00000000 fffffa80`03ed7040 00000000`00000001 00000000`00000000 : 0xfffff880`07cc7000
fffff880`03bf4598 00000000`00000000 : fffffa80`03ed7040 00000000`00000001 00000000`00000000 00000000`13dfe000 : 0xfffffa80`05dc3a40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+3cd770
fffff880`049f6770 48895c2410      mov     qword ptr [rsp+10h],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmdag+3cd770

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ca29946

FAILURE_BUCKET_ID:  X64_0xD1_atikmdag+3cd770

BUCKET_ID:  X64_0xD1_atikmdag+3cd770

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

yamamma · 23 Jan 2011

Thx 4 helpin' me in this issue..... It's end up with one of the memory(RAM) stick gone faulty because of the mobo always auto change the frequency (BIOS default)..... Now I already change my mobo to the NEW one (from ECS to Gigabyte).... and want to claim warranty for the ECS mobo & RAM later on...... So, my advice is... never buy cheap mobo even if you want to use it temporary..... coz it will effect your other components if anything bad happen to your mobo..... and also it will cost you more if something bad like mine happen.....

Thanks again....~