Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD Vista Sp2 when computer starts

  • Please log in to reply
No replies to this topic



  • Members
  • 1 posts
  • Local time:05:45 AM

Posted 06 September 2009 - 11:52 AM


First, would you excuse for my language as I'm french.
Impossible for me to find help on french forums... and I'm getting crazy !

Here's my problem :
I bought a Dell computer (inspiron 530) on Ebay.
The first time I started it, I had 4 short continuing bips. I restarted and it was OK. I made updates > vista sp2 and still do updates (+ Avast free antivirus)
But since 3 months I have this computer, I always have the 4 continuing bips or BSOD when I start or indication that "Windows couldn't start normaly" (of course, it never success in trying to repair...)
No problem when it accepts to start, it works great.
At the beginning, I thought It was a memory problem (even if I never found what meaned the 4 bips) so I bought 4 X 1 GB Crucial Ballisitx to change the original ones.
I also change the Power for a 650W Corsair.
But I still have descripted problems... I tried everything : dell diagnostics, memtest, one, two, three or four memory modules...
Today, I found the Windbg tool and would greatly appreciate help !!!
Here's copy of the last crash :


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.

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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82234000 PsLoadedModuleList = 0x8234bc70
Debug session time: Sun Sep 6 17:36:04.009 2009 (GMT+2)
System Uptime: 0 days 0:01:54.696
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8229011f, 80399c38, 80399934}

Probably caused by : memory_corruption ( nt!MiMapPagesForZeroPageThread+aa )

Followup: MachineOwner

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

This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
Arg1: c0000005, The exception code that was not handled
Arg2: 8229011f, The address that the exception occurred at
Arg3: 80399c38, Exception Record Address
Arg4: 80399934, Context Record Address

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas tre en tat

8229011f 8a520e mov dl,byte ptr [edx+0Eh]

EXCEPTION_RECORD: 80399c38 -- (.exr 0xffffffff80399c38)
ExceptionAddress: 8229011f (nt!MiMapPagesForZeroPageThread+0x000000aa)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 3f3f3f4d
Attempt to read from address 3f3f3f4d

CONTEXT: 80399934 -- (.cxr 0xffffffff80399934)
eax=fd924243 ebx=00000000 ecx=0000001c edx=3f3f3f3f esi=c0401930 edi=00000963
eip=8229011f esp=80399d00 ebp=80399d20 iopl=0 ov up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a87
8229011f 8a520e mov dl,byte ptr [edx+0Eh] ds:0023:3f3f3f4d=??
Resetting default scope





ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%08lx emploie l'adresse m moire 0x%08lx. La m moire ne peut pas tre en tat



READ_ADDRESS: GetPointerFromAddress: unable to read from 8236b868
Unable to read MiSystemVaType memory at 8234b420

8229011f 8a520e mov dl,byte ptr [edx+0Eh]


LAST_CONTROL_TRANSFER: from 8228fcca to 8229011f

80399d20 8228fcca 3f3f3f3f 00000100 8427b0a0 nt!MiMapPagesForZeroPageThread+0xaa
80399d74 8238d372 80399dc0 82409c42 80810738 nt!MmZeroPageThread+0x2c0
80399d7c 82409c42 80810738 dc73c62f 00000000 nt!Phase1Initialization+0x12
80399dc0 82272efe 8238d360 80810738 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_NAME: nt!MiMapPagesForZeroPageThread+aa




STACK_COMMAND: .cxr 0xffffffff80399934 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x7E_nt!MiMapPagesForZeroPageThread+aa

BUCKET_ID: 0x7E_nt!MiMapPagesForZeroPageThread+aa

Followup: MachineOwner

Best regards from France, Sebastien.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users