Windows 7: Multiple BSODs--Detective work needed

Red Dino · 13 May 2011

My son purchased this computer in early April 2011 to use mostly for gaming and Scratch. It was without a box, just the unit and keyboard. Good price, but maybe you get what you pay for...

Looking more closely at the computer's operating software configuration and dates of installation, I suspect that the computer has been "worked on" but not fixed.

Everything worked fine until he downloaded and played the latest release of Minecraft. Lots of BSOD from there forward with both Minecraft and Sims 3. (These, Scratch, and Internet Explorer are all he uses the computer for.)

We've downloaded and installed updated drivers for everything that we can find. Usually things will work fine for a couple of days after a new driver is installed, high fives all around! Then, the BSODs start up again, always during game play until recently when he's had a few while on the internet.

My son likes his computer very much, but wishes to resolve its problems!

Thanks in advance for your time and concern.

wish · 13 May 2011

Hello Red Dino,
You've uploaded the wrong files. Not the jcgriff.exe but the output folder that we need.
Blue Screen of Death (BSOD) Posting Instructions

Red Dino · 13 May 2011

Sorry, here's the correct file.

wish · 13 May 2011

There are 33 dump files in 2 months since first Windows installation.
It seems to be hardware failure but 3rd driver or software may also causing problem.
Few dumps related to USB driver so you need to update this driver:

Code:

RtsUStor.sys Tue Jul 20 01:43:03 2010 → Realtek USB Card Reader

See if the problem persist, then perform RAM test for at least 7 passes:
RAM - Test with Memtest86+

Log

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a0c000 PsLoadedModuleList = 0xfffff800`02c49e50
Debug session time: Thu May 12 13:53:14.633 2011 (GMT-8)
System Uptime: 0 days 0:20:47.022
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 210001, 0, fffff70001080000}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000000210001
Arg3: 0000000000000000
Arg4: fffff70001080000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ad13b3 to fffff80002a7c740

STACK_TEXT:  
fffff880`02a59888 fffff800`02ad13b3 : 00000000`0000001a 00000000`00041284 00000000`00210001 00000000`00000000 : nt!KeBugCheckEx
fffff880`02a59890 fffff800`02aad445 : fffff700`01080000 00000000`00000061 fffffa80`02350e00 00000000`00000228 : nt! ?? ::FNODOBFM::`string'+0x4a83
fffff880`02a598d0 fffff800`02a4fc13 : ffffffff`00000000 00000000`0023ffff fffffa80`00000000 fffffa80`05711060 : nt!MiDeleteVirtualAddresses+0x4cc
fffff880`02a59a90 fffff800`02d5fabf : fffff8a0`09e97060 00000000`00000001 00000000`00000000 fffffa80`05711060 : nt!MmCleanProcessAddressSpace+0x62f
fffff880`02a59ae0 fffff800`02d3895b : 00000000`c0000139 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`02a59ba0 fffff800`02a7b993 : fffffa80`05707b30 00000000`c0000139 00000000`77b64501 fffffa80`05711060 : nt!NtTerminateProcess+0x25b
fffff880`02a59c20 00000000`77a7f97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0023f388 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a7f97a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4a83
fffff800`02ad13b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4a83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4cc791bd

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83

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

Red Dino · 13 May 2011

Thank you. We have downloaded the driver you suggested and are testing it now. If things aren't better we will run the memtest. It may be a day or two until we can get back to you with the results, but we will let you know what happened.

Thanks again for your advice.

wish · 14 May 2011

You're welcome.
Just take your time and let us know the result

Red Dino · 17 May 2011

Hi, just wanted to update you before I close this thread...We were able to update the driver, but it did not improve the situation, so we went ahead with using Memtest. Sure enough, right away the system failed. Then we followed the advice in the tutorial, took sticks out and tested different configurations. Two of the four slots appear to have problems, so we put 2gb of Ram in each working slot, ran Memtest and everything worked fine. Since then, my son has logged many hours of Minecraft time and has not had a BSOD once. Someday, maybe he can get some 4gb sticks of Ram and maximize the two working slots, but until then, he is very, very happy to have a working computer!

Thanks so much for your help!

Windows 7: Multiple BSODs--Detective work needed

Multiple BSODs--Detective work needed problems?