Windows 7 Random BSOD During Idle and Browser Use After Windows Update

[joel7223]

I get a random bsod when my computer is idle, or when I sometimes plug in a usb flash drive but mostly when I am just surfing the internet on any browser. I can play a resource heavy game like Civilization V for hours and there is no problem.

I used memtest, and seatools for my harddrive but no errors or problems found. I also used SFC, re-installed windows (upgrade win 7). After I re-installed windows the problem didn't come back until I downloaded all the updates.
View attachment 100910-28626-01.dmp

Thanks for any help.

 

[TorrentG]

Hey there, welcome.

Not such an easy stop here, as most drivers aren't able to be seen. I would disable the page file, reboot. Then run this command from an elevated command prompt:

chkdsk /r

Reboot and let it complete. Then when back to desktop, re-enable the page file.

Post new crash dumps if and as they happen.

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


Loading Dump File [C:\Downloads\100910-28626-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`03054e50
Debug session time: Sat Oct  9 10:16:51.014 2010 (UTC - 4:00)
System Uptime: 0 days 0:24:04.762
Loading Kernel Symbols
................................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
..Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 30, 0, 0}

*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000001
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000001
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

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

1: 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: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007a5e6f0 -- (.trap 0xfffff88007a5e6f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f6bdb1 rsp=fffff88007a5e880 rbp=fffff88007a5e8c0
 r8=fffff80002e17000  r9=0000000000000001 r10=0000000fffffffff
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nt!MiResolvePageFileFault+0x10c1:
fffff800`02f6bdb1 8b4830          mov     ecx,dword ptr [rax+30h] ds:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e33b7a to fffff80002e87740

STACK_TEXT:  
fffff880`07a5e588 fffff800`02e33b7a : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`07a5e590 fffff800`02e8582e : 00000000`00000000 00000000`2a300000 fffffa80`06598a00 fffff880`009e7180 : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`07a5e6f0 fffff800`02f6bdb1 : 00000000`0006c5ad 00000000`00000000 00000000`000000ad fffffa80`03905ad0 : nt!KiPageFault+0x16e
fffff880`07a5e880 fffff800`02efdbec : 000007fe`f5c11698 fffff683`ff7ae088 fffffa80`063b9ec8 00000000`00000011 : nt!MiResolvePageFileFault+0x10c1
fffff880`07a5e9b0 fffff800`02ea1743 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36946
fffff880`07a5eac0 fffff800`02e8582e : 00000000`00000000 00000000`00000000 fffffa80`063b9b01 00000000`02c5c02c : nt!MmAccessFault+0x343
fffff880`07a5ec20 000007fe`f5c5325d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0338f000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f5c5325d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`02e33b7a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

Followup: MachineOwner

The USB flash drive could be causing this. Leave it away and unattached from the machine.

 

[joel7223]

Thanks for your help.

I followed all of your steps. Here is the latest crash dump:
View attachment 100910-20030-01.dmp

 

[joel7223]

here are some more dump files:
View attachment 100910-19687-01.dmpView attachment 100910-23166-01.dmpView attachment 100910-17986-01.dmpView attachment 100910-31652-01.dmpView attachment 100910-34008-01.dmpView attachment 100910-28563-01.dmp

I got a bunch of different messages lately on the bsod, such as system service exception, page fault in non paged area, quota underflow.

 

[TorrentG]

Now I can see all drivers.

1) Type systeminfo in command prompt then press enter. It will show you the number of Realtek lan. If it's 8111, download and install from the following link. If anything else, search the left side of the link for the number:

Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009

Link Removed

2) From an elevated command prompt, run the following command for each and every hard drive partition letter on the system, changing C: to match each time:

chkdsk /r C:

3) If issues persist, please post a new crash dump but then also begin testing memory with Memtest86+, overnight or until errors show. If errors do show, then replace the RAM.

 

[joel7223]

Now, I am getting tens of thousands of errors almost immediately (it would easily reach hundreds of thousands if giving the chance), whereas a few days ago I got zero errors while testing them simultaneously for 1 hour and 40 mins. I took one stick of ram out yesterday and it ran fine all day and this morning. Then I tested my computer by plugging in a usb flash drive again and it goes haywire.

I built this computer almost 2 months ago and it has been fine until recently. If my motherboard is bad could that cause errors during the memtest? It seems strange that both ram sticks would die at the same time to this extent. Also, another recent problem I get is the video card not being recognized when I boot up sometimes (3 long beeps - continuous, blank screen). I switched to an old pci video card and it does the same thing. I can't even boot up windows anymore.

At this point I think I have to RMA something but not sure if it is just my ram that is the problem or possibly my motherboard? I was thinking I could just buy two new sticks of ram as well since I have the free slots for it, but I don't want to jump the gun yet with spending more money than I need to.

Thanks for helping me!!

 

[TorrentG]

Then I tested my computer by plugging in a usb flash drive again and it goes haywire.

Keep that USB drive out and away from the machine. It could be defective, adding to the difficulties you're experiencing. Let's keep it totally out of the mix.

Other than that, set the optimized values in the bios settings and save.

Test the memory again to see if there are errors.

 

[DarKBuzz]

I have a Machine Running Win7 Enterprise. I get random Freeze's. I got the following error the last time it froze. KErnal Data inpage error Stop:0x0000007A (0xc041670f0,0xc000018s,0x3ee76860,0x82cfeab6) Hoping someone can help identify the issue.

 

[TorrentG]

I have a Machine Running Win7 Enterprise. I get random Freeze's. I got the following error the last time it froze. KErnal Data inpage error Stop:0x0000007A (0xc041670f0,0xc000018s,0x3ee76860,0x82cfeab6) Hoping someone can help identify the issue.

Please create your own thread and post the crash dumps.