Home > Blog

BSOD on Windows 7 Computer

Question:
Original title: Helpppppppp solve problem
 
 
Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
Copyright (c) Microsoft Corporation.
All rights reserved.


Loading Dump File [C:\Windows\Minidump\021613-21606-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x83240000 PsLoadedModuleList = 0x833894d0
Debug session time: Sat Feb 16 10:04:53.404 2013 (UTC + 1:00)
System Uptime: 0 days 0:03:09.277
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, 68e7ffec, 2, 1, 8329e0c7

Probably caused by : memory_corruption ( nt!MmZeroPageThread+2e1 )

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

0: 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: 68e7ffec, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8329e0c7, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 833a9848
Unable to read MiSystemVaType memory at 83388e20
 68e7ffec 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmZeroPageThread+2e1
8329e0c7 f00fba2800      lock bts dword ptr [eax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFFFFF8078B000

TRAP_FRAME:  80786c4c -- (.trap 0xffffffff80786c4c)
ErrCode = 00000002
eax=68e7ffec ebx=68e7ffec ecx=851fe502 edx=00000000 esi=68e7ffe4 edi=ff05ffff
eip=8329e0c7 esp=80786cc0 ebp=80786d44 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MmZeroPageThread+0x2e1:
8329e0c7 f00fba2800      lock bts dword ptr [eax],0   ds:0023:68e7ffec=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8329e0c7 to 83280c7b

STACK_TEXT:  
80786c4c 8329e0c7 badb0d00 00000000 8320eba9 nt!KiTrap0E+0x2cf
80786d44 833cc4cd 00000000 80786d90 8344905d nt!MmZeroPageThread+0x2e1
80786d50 8344905d 8080a458 bb7197f1 00000000 nt!Phase1Initialization+0x14
80786d90 832f0529 833cc4b9 8080a458 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmZeroPageThread+2e1
8329e0c7 f00fba2800      lock bts dword ptr [eax],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmZeroPageThread+2e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  50e793e8

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

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

0: 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: 68e7ffec, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 8329e0c7, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 833a9848
Unable to read MiSystemVaType memory at 83388e20
 68e7ffec 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmZeroPageThread+2e1
8329e0c7 f00fba2800      lock bts dword ptr [eax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFFFFF8078B000

TRAP_FRAME:  80786c4c -- (.trap 0xffffffff80786c4c)
ErrCode = 00000002
eax=68e7ffec ebx=68e7ffec ecx=851fe502 edx=00000000 esi=68e7ffe4 edi=ff05ffff
eip=8329e0c7 esp=80786cc0 ebp=80786d44 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MmZeroPageThread+0x2e1:
8329e0c7 f00fba2800      lock bts dword ptr [eax],0   ds:0023:68e7ffec=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8329e0c7 to 83280c7b

STACK_TEXT:  
80786c4c 8329e0c7 badb0d00 00000000 8320eba9 nt!KiTrap0E+0x2cf
80786d44 833cc4cd 00000000 80786d90 8344905d nt!MmZeroPageThread+0x2e1
80786d50 8344905d 8080a458 bb7197f1 00000000 nt!Phase1Initialization+0x14
80786d90 832f0529 833cc4b9 8080a458 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmZeroPageThread+2e1
8329e0c7 f00fba2800      lock bts dword ptr [eax],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmZeroPageThread+2e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  50e793e8

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

BUCKET_ID:  0xA_nt!MmZeroPageThread+2e1

Followup: MachineOwner
Solution to BSOD on Windows 7 Computer:


Use the Sfc tool to repair - BSOD on Windows 7 Computer


sfc is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. This article describes how to run the System File Checker tool (SFC.exe) to scan your system files and to repair missing or corrupted system files. If a Windows Resource Protection (WRP) file is missing or is corrupted, Windows may not behave as expected. For instance, some Windows functions may not work, or Windows may crash.

For Windows 8 or Windows 8.1

  • Open an elevated command prompt. To do this, do the following as your appropriate:
  • Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.

Windows vista, Windows 7, or Windows 10

  • To do this, click Start, type Command Prompt or cmd in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, enter the password, or press Allow.
  • At the command prompt, type the following command, and then press ENTER:
  • sfc /scannow
  • The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache.
  • The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows.
  • Note: Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished.
After the process is finished, you may receive one of the following messages:
  • Windows Resource Protection did not find any integrity violations.
  • This means that you do not have any missing or corrupted system files.

Check if hardware is working properly


If you still receive BSOD on Windows 7 Computer error message after you perform a clean installation of your Operating System, it's certain that this problem should be caused by a bad hardware. You can test each piece of hardware devices and find out and then replace the problematic one.

Still didn't fix it? BSOD on Windows 7 Computer

Don't Worry!

How to Fix BSOD on Windows 7 Computer with SmartPCFixer?

Video Tutorial: How to Fix BSOD on Windows 7 Computer?

1. Click the button to download Error Fixer . Install it on your computer.  Open it, and it will perform a scan for your computer. The errors will be shown in the scan result.




2. After the scan is done, you can see the errors and problems which need to be repaired.




3. The Fixing part is done, the speed of your computer will be much higher than before and the errors have been removed.




Tagged: BSOD on Windows 7 Computer, dll error fixer, speedy up windows

Download SmartPCFixer Now - Repair Your System & Speed it Up!

What People Say: (About BSOD on Windows 7 Computer)

La cacería salvaje me estaba dando error falta BSOD on Windows 7 Computer. El problema fue resuelto después de descargar este software desde su sitio web! Gracias.

by Walter Watson Jan.13th

SmartPCFixer
A Best Seller in 2015. Good at fixing various computer errors and speeding up Windows.


Hot Downloads