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
Key to BSOD on Windows 7 Computer:


Restart the desktop


You were playing a game when suddenly an error message popped up? You can try to reboot your system to see if this problem could be a glitch. Many errors can be fixed by a simple reboot as it is not impossible that the system malfunctions after long-time working. What it needs is just a break and a restart. If you can't reboot it normally, you can force reboot it.


System Restore - BSOD on Windows 7 Computer


System Restore can return your PC's system files and programs to a time when everything was working fine, potentially preventing hours of troubleshooting headaches. It won't affect your documents, pictures, or other data. Please back up important changes(files, documents) before you perform system restore.

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

Don't Panic!

How to Fix BSOD on Windows 7 Computer with SmartPCFixer?

1. Download Error Fixer. Install it on your computer.




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




3. The Repair part is done, the speed of your computer will be much higher than before and the errors have been removed. You can also use other functions in SmartPCFixer. Like dll downloading, windows updating and print spooler error repair.




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

Download SmartPCFixer Now - Fix Errors & Speed Up Your System

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

SmartPCFixer cleaned up my PC with a couple of simple steps. The process is SUPER easy and the results couldn't be better. Now my PC starts right up and doesn't show those annoying BSOD on Windows 7 Computer error messages anymore. You have a life-long customer SmartPCFixer thanks.

by Marie Sherman Jul.19th

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


Hot Downloads