Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Before and After Clean Win7 Install


26 Jan 2013   #1
GrimmShado

Windows 7 Home Premium 64bit
 
 
BSOD Before and After Clean Win7 Install

Hi all,

I do a fresh install of Win7 every 6 months or so. I started getting BSOD a little over a month ago after 6 months of no problems. I have not installed any new programs for at least 2 months before the BSOD started. This is the first time I have gotten a BSOD on this laptop ever. I have been getting a BSOD about twice a week. They seemed to happen randomly: while playing games, surfing the web, streaming video, running MSE antivirus. I ran memtest86 for about a dozen passes with no errors. I got a SSD yesterday and I was hoping the BSOD would go away after a fresh install. After installing Win7, SP1, and drivers, I did windows updates. They downloaded fine, but as soon as they started installing, I got a BSOD for memory management. I tried installing the updates again and got a BSOD for irql not less or equal.

I appreciate any help, thanks!


My System SpecsSystem Spec
.

26 Jan 2013   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Hello & Welcome to SF.

Hard to say anything with one dump file as it still points towards memory being the issue.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000021e80, 6830000179ca9867, fffff68000029e80}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+330bc )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000021e80
Arg3: 6830000179ca9867
Arg4: fffff68000029e80

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002a77ca6 to fffff80002ad0640

STACK_TEXT:  
fffff880`041287a8 fffff800`02a77ca6 : 00000000`0000001a 00000000`00000403 fffff680`00021e80 68300001`79ca9867 : nt!KeBugCheckEx
fffff880`041287b0 fffff800`02b02627 : 00000000`00000000 fffff680`00021e80 fffffa80`05bbeb30 2aaaaaaa`aaaaaaab : nt! ?? ::FNODOBFM::`string'+0x330bc
fffff880`04128960 fffff800`02abdaef : fffffa80`00000000 00000000`0441cfff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`04128b20 fffff800`02acf8d3 : ffffffff`ffffffff 00000000`03f5e9b8 00000000`03f5e9b0 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`04128c20 00000000`775114fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03f5e978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775114fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+330bc
fffff800`02a77ca6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+330bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+330bc

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+330bc

Followup: MachineOwner
---------
Please run memtest again in the following manner:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.
My System SpecsSystem Spec
28 Jan 2013   #3
GrimmShado

Windows 7 Home Premium 64bit
 
 

I ran memtest for each of the two sticks alone in each of the two ram slots, like the instructions said, for 10-12 passes and it reported no errors. I got another bsod earlier right as I was restarting my laptop. When the bsod came up, my laptop restarted almost immediately and it didn't dump any of the crash info. I'm starting to get scared that it's gonna be a problem that I can't fix and I'll have to get a new laptop.
My System SpecsSystem Spec
.


28 Jan 2013   #4
GrimmShado

Windows 7 Home Premium 64bit
 
 

I got another bsod as I was trying to do windows update again. It appears to be stuck on the screen and the "dumping physical memory to disk" is stuck at 15. It's for memory management and the stop says 0x0000001A (0x0000000000005003, 0xFFFFF70001080000, 0x0000000000000566, 0x0000056800008AC).
My System SpecsSystem Spec
28 Jan 2013   #5
GrimmShado

Windows 7 Home Premium 64bit
 
 

And another bsod while doing windows updates. This time it's irql not less or equal and it appears to be stuck again at "collecting data for crash dump." The stop says 0x0000000A (0xFFFFF80082F0D918, 0x0000000000000002, 0x0000000000000000, 0xFFFFF80002CE2BA5)
My System SpecsSystem Spec
28 Jan 2013   #6
GrimmShado

Windows 7 Home Premium 64bit
 
 

Had another BSOD. Just rebooted my laptop and then left the room to take care of some stuff. When I came back, my laptop had rebooted and I found that dialogue box saying there was a crash and a new minidump. I have attached it.
My System SpecsSystem Spec
28 Jan 2013   #7
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Please follow this:
Quote   Quote: Originally Posted by writhziden View Post
If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
Perform a System File Check:
  1. Click on the start
  2. Type CMD on Search
  3. Left click and Run as Administrator
  4. Type SFC /scannow
Full tutorial here:Disk Check on your hard drive for file system errors and bad sectors on it:Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.
Daemon Tools:

Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

As an alternative, many people recommend the use of Total Mounter or Magic ISO
My System SpecsSystem Spec
29 Jan 2013   #8
GrimmShado

Windows 7 Home Premium 64bit
 
 

I have the latest SSD firmware, BIOS, and chipset drivers. I'm not sure about the HD controller drivers/SATA drivers, but if it's the thing listed under IDE ATA/ATAPI controllers in device manager, then I have the latest drivers for that too. I just tried doing a system file check and got a bsod. I don't know if you wanted everything that the SF diagnostic tool pulls, but I attached just the minidump from the latest bsod.
My System SpecsSystem Spec
29 Jan 2013   #9
GrimmShado

Windows 7 Home Premium 64bit
 
 

System file check reported no integrity violations.
My System SpecsSystem Spec
29 Jan 2013   #10
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

I've requested a friend to take a look.
Please wait for a reply.
My System SpecsSystem Spec
Reply

 BSOD Before and After Clean Win7 Install




Thread Tools



Similar help and support threads for2: BSOD Before and After Clean Win7 Install
Thread Forum
BSOD even after clean Win7 re-install BSOD Help and Support
Solved random BSOD clean win7 64bit install, need your help guys BSOD Help and Support
BSOD when trying to do clean install a Win7 ultimate 64bit BSOD Help and Support
Solved BSOD after completing clean install win7 64 BSOD Help and Support
Solved BSOD when attempting to clean install Win7 64bit Professional BSOD Help and Support
Win7 64bit BSOD - clean install BSOD Help and Support
Win7 7100 Clean Install - BSOD BAD_POOL_HEADER Installation & Setup

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:04 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App