Occasional BSOD

[wangster]

Can somebody check this out for me? I recently built a new computer and finally installed Windows 7. After about 2 weeks of Vista, I had gone back to XP because my old P4 couldn't handle Vista too well.

Well, got a new computer and decided to install Windows 7 Ultimate x64 after hearing many good things about it.

Here I am. A few days of Win7 and a few BSOD's already...

I'd appreciate it if somebody could pinpoint what's causing the error.


I had copied the text portion of the pop-up window upon reboot. Here they are.

==========
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: 0000000000041790
BCP2: FFFFFA800154FDA0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040510-15444-01.dmp
C:\Users\Hyung Kyun Wang\AppData\Local\Temp\WER-20280-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
==========
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: 50
BCP1: FFFFD8800A132BC8
BCP2: 0000000000000001
BCP3: FFFFF80002AE3ADF
BCP4: 0000000000000007
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040610-17238-01.dmp
C:\Users\Hyung Kyun Wang\AppData\Local\Temp\WER-24242-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

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

 

[Jonathan_King]

Welcome!

I suggest testing your memory. Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

In addition, try running a system files check. Open an elevated command prompt and enter sfc /scannow.

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_dump_filez.zip\040610-17238-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
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`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Tue Apr  6 09:56:02.199 2010 (GMT-4)
System Uptime: 0 days 6:05:16.635
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8800a132bc8, 1, fffff80002ae3adf, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KeRemoveQueueEx+31f )

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: ffffd8800a132bc8, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ae3adf, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
 ffffd8800a132bc8 

FAULTING_IP: 
nt!KeRemoveQueueEx+31f
fffff800`02ae3adf 4c8918          mov     qword ptr [rax],r11

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a132850 -- (.trap 0xfffff8800a132850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd8800a132bc8 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ae3adf rsp=fffff8800a1329e0 rbp=0000000000000000
 r8=fffffa8008d6f5a8  r9=0000000000000000 r10=fffffffffffffffb
r11=0000000000000102 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeRemoveQueueEx+0x31f:
fffff800`02ae3adf 4c8918          mov     qword ptr [rax],r11 ds:ffffd880`0a132bc8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b56b19 to fffff80002ad8f00

STACK_TEXT:  
fffff880`0a1326e8 fffff800`02b56b19 : 00000000`00000050 ffffd880`0a132bc8 00000000`00000001 fffff880`0a132850 : nt!KeBugCheckEx
fffff880`0a1326f0 fffff800`02ad6fee : 00000000`00000001 00000033`07550f95 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`0a132850 fffff800`02ae3adf : 00000000`00000000 00000000`00000000 00000000`000000e7 fffff800`02aeb342 : nt!KiPageFault+0x16e
fffff880`0a1329e0 fffff800`02dd16d7 : fffffa80`08e2c700 fffff880`0a132bc8 fffff880`0a132ca0 0016019f`00000002 : nt!KeRemoveQueueEx+0x31f
fffff880`0a132a90 fffff800`02ae9296 : fffff880`00000000 fffff880`0a132ba8 fffff880`0a132bc8 fffff800`000e0001 : nt!IoRemoveIoCompletion+0x47
fffff880`0a132b20 fffff800`02ad8153 : fffffa80`0913fb60 00000000`7ef64000 00000000`00000000 fffffa80`0a9405d0 : nt!NtWaitForWorkViaWorkerFactory+0x285
fffff880`0a132c20 00000000`77a017ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`073ee218 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a017ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeRemoveQueueEx+31f
fffff800`02ae3adf 4c8918          mov     qword ptr [rax],r11

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeRemoveQueueEx+31f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x50_nt!KeRemoveQueueEx+31f

BUCKET_ID:  X64_0x50_nt!KeRemoveQueueEx+31f

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

 

[wangster]

Thank you for the quick response. Does MemTest fix my ram or could I have bad memory? Will MemTest tell me if I have bad ram and if it tells me so, is it a valid reason to ask Newegg for exchange?

 

[wangster]

By the way, if admin sees this, I hope you install a mobile ug in for the forums... Is it vBulletin?

 

[Jonathan_King]

Yes, this is vBulletin.

If Memtest turns up errors, borrow some RAM from a friend and test it in your machine, just to make sure it is not your motherboard.

If the borrowed RAM works, return your RAM to Newegg for a refund or replacement.

 

[wangster]

I bought DDR 3 1600 (PC3 12800) ram and my motherboard says it supports it. When I take a look at the POST screen (it's too fast for me but I think I read it right) , it looks like it's reading it as PC3 1333.

Could this be the reason for BSOD reboots?

 

[Jonathan_King]

Probably not. Unless Memtest is turning up errors in the very beginning, I wouldn't think that's your problem.

 

[wangster]

Holy Sh**! 3 minutes into MemTest+ and 672 errors... Bad memory? Would you recommend that I use 1 stick to check each slot and them run the test again and again for each of my 4 memory sticks in each slot? Are there any tools to check if it's the motherboard or the memory?

 

[wangster]

Few minutes later... Already over 1200 errors....

 

[Lebon14]

Yes, you have one oor multiple dead modules.
Try this : open your case and remove all but one memory unit. Boot onto Windows. If no BSOD opens after a while, you have a good tick of RAM. Repeat with the other modules. Alternatively, you can run Memtest and run it on all your sticks. Like that, you can detect bad sticks of RAM.

 

[wangster]

I just shut it off after a few hours. I am going to try to run Memtest on each one of sticks tonight. Hopefully I can find the bad memory and get it replaced.

 

[karlsnooks]

Holy Sh**! 3 minutes into MemTest+ and 672 errors... Bad memory? Would you recommend that I use 1 stick to check each slot and them run the test again and again for each of my 4 memory sticks in each slot? Are there any tools to check if it's the motherboard or the memory?

Valid approach.

 

[wangster]

Well, it turns out I have one bad memory.

RAM #1 in slot 1 = No Errors
RAM #2 in slot 1 = Over 1,000 Errors
RAM #3 in slot 1 = No Errors
RAM #4 in slot 1 = No Errors

Put RAM #2 & #3 in its original packaging...

RAM #1 & RAM #4 in slots 1&2 = No Errors
RAM #1 & RAM #4 in slots 3&4 = No Errors

So I think it's safe to say that it was the RAM. Filing an RMA now.

Thank you guys for helping figure it out.

By the way, is the debugger tool something I can easily get? I don't think I can understand in full what it tells me but Google's one of my best friends.

Also, thank you for pointing out Memtest. I didn't know about it but looks like I'll be running it every time I get new RAM.

 

[Jonathan_King]

That was some good diagnostic work, wangster. Well done.

Yes, the Windows Debugging Tools are freely available to anyone who wants to download them. See here: http://www.sevenforums.com/crash-lo...intermediate-configuring-debugging-tools.html

If you need any help, I can give you some basic tips to get you stated. Feel free to PM me, or IM me at one of these addresses:

jonathanking09 at live dot com.

jonathanking09 at yahoo dot com

jonathanking09 at aol dot com (AIM)

And if you use Google Talk, my address is natalyabennettathotmaildotcom at gmail dot com (don't ask )

 

[karlsnooks]

wangster,
Nice work. Glad to hear that you located the problem and that we could be of assistance.

 

[wangster]

That was some good diagnostic work, wangster. Well done.

Yes, the Windows Debugging Tools are freely available to anyone who wants to download them. See here: http://www.sevenforums.com/crash-lo...intermediate-configuring-debugging-tools.html

If you need any help, I can give you some basic tips to get you stated. Feel free to PM me, or IM me at one of these addresses:

jonathanking09 at live dot com.

jonathanking09 at yahoo dot com

jonathanking09 at aol dot com (AIM)

And if you use Google Talk, my address is natalyabennettathotmaildotcom at gmail dot com (don't ask )

I went to the link you provided for the debugger, saw all that code in blue and just closed the browser window. Intimidating...

wangster,
Nice work. Glad to hear that you located the problem and that we could be of assistance.

Thank you.

 

[wangster]

Well, this thread was my first post in this forum. Came to this place after doing my first Win7 install. Thanks to you guys, I RMA'd the bad ram, received the replacement last week and haven't had a blue screen error yet. Thank you again.

 

[Jonathan_King]

I'm glad to hear it.

Thanks for reporting back, and let us know if you need anything else.