Windows 7: BSOD 10-30 times a day.

ChubbyMouse · 29 Aug 2013

This is really too much, whatever I do on this computer it will BSOD, even while AFK.

I cannot really do anything making my computer useless.
I happen to experience 3 BSOD while making this new thread.
Here I attached all the information needed.

Processor: Intel Core 2 Duo E7500 2.93 GHz
Ram: 3Gb
System Type: 32 Bit
Windows Edition: Home Premium

Arc · 29 Aug 2013

Hello ChubbyMouse.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Install the 314.22 WHQL of the nvidia display driver as mentioned below.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

Let us know the results.
________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {81792468, 2, 0, 82ee71ac}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+1cf )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 81792468, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82ee71ac, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fae84c
Unable to read MiSystemVaType memory at 82f8de20
 81792468 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+1cf
82ee71ac 8b38            mov     edi,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  9e4636f4 -- (.trap 0xffffffff9e4636f4)
ErrCode = 00000000
eax=81792468 ebx=85b39c90 ecx=00000000 edx=0808a3a0 esi=0a000000 edi=9e4637a0
eip=82ee71ac esp=9e463768 ebp=9e4637a0 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiIdentifyPfn+0x1cf:
82ee71ac 8b38            mov     edi,dword ptr [eax]  ds:0023:81792468=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82ee71ac to 82e85b7f

STACK_TEXT:  
9e4636f4 82ee71ac badb0d00 0808a3a0 00000002 nt!KiTrap0E+0x1b3
9e4637a0 82e76bdc 85b39c90 85b39000 9e463844 nt!MiIdentifyPfn+0x1cf
9e4637c8 830c526d 00b39060 b05c95cc 9e463858 nt!MmQueryPfnList+0xa6
9e463810 8307ab5c 00000001 b05c954c 00000000 nt!PfpPfnPrioRequest+0xde
9e463890 83066827 00000000 00000001 9e463cd0 nt!PfQuerySuperfetchInformation+0xea
9e463d00 83075fab 0000004f 00000000 00000000 nt!ExpQuerySystemInformation+0x2477
9e463d1c 82e828c6 0000004f 0098f250 00000014 nt!NtQuerySystemInformation+0x76
9e463d1c 778170f4 0000004f 0098f250 00000014 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0098d110 00000000 00000000 00000000 00000000 0x778170f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+1cf
82ee71ac 8b38            mov     edi,dword ptr [eax]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiIdentifyPfn+1cf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  51db7a63

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiIdentifyPfn+1cf

BUCKET_ID:  0xA_nt!MiIdentifyPfn+1cf

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