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: Random BSOD, Windows 7 Ultimate x64

27 Feb 2012   #1

Windows 7 Ultimate x64
Random BSOD, Windows 7 Ultimate x64

Hi all,
I am having random BSOD. Ran Windows Memory Diagnostic and it found no errors. BIOS updated. Drivers updated as far as I know.

Here is the details from the last crash:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Attached are the minidumps as instructed as well as system configuration file.

Thanks in advance.

My System SpecsSystem Spec
27 Feb 2012   #2

Win 7 Ultimate 64-bit. SP1.

1. McAfee is a frequent cause of BSOD's.
I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST!

Microsoft Security Essentials - Free Antivirus for Windows

2. Please run the update readiness tool and then update to SP-1

Ensure you install the correct 64 or 32 bit option for your system)
Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

3. These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have Raid > update its Driver.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Using Driver Verifier to identify issues with Windows drivers for advanced users

My System SpecsSystem Spec

 Random BSOD, Windows 7 Ultimate x64

Thread Tools

Similar help and support threads
Thread Forum
Random BSOD after installing windows 7 ultimate x64 and drivers...
Hello! I installed multiple windows 7 ultimate X64 but the BSOD is still remaining ... After I install a windows 7 ultimate x64 and the drivers BSOD randomly retunrs ... after 10 min, after 25, but continuosly ... I attached the diagnostic tools report... Thans for helping in advance...
BSOD Help and Support
Windows 7 ultimate 64-bit BSOD at random
Ive been having an issue with BSOD for about a month or two now. Everything was working fine before then. The only thing new installed and/or replaced was about 6 months ago i had to replace my Power supply. Its 100% random some days i can jump on play for 2-3 hours no issue, and the next day jump...
BSOD Help and Support
Windows 7 Ultimate , Random BSOD
Hey guys i hope i came to the right place to figure out this blue screen error. I'm really starting to think maybe it's a mobo issue? .. Anyways heres my story.. Please bare with me. I built this PC about a month ago the following are my current specs. AsRock N61P-S Motherboard. AMD...
BSOD Help and Support
Windows 7 Ultimate x64 Random BSOD
Greetings, I have been plagued by these random BSOD's for 6 months or so now, but have simply put up with it. Time has come when I can stand it no longer! :o I have some Minidump files if someone wouldn't mind looking at them - I am clueless when it comes to debugging. :( Thanks in advance...
BSOD Help and Support
Windows 7 Ultimate x64 random BSOD
Hi! I have gotten random BSOD's ever since I installed the os for the first time on my computer. It looks like ntoskrnl.exe crashes the most. Can anyone see what they make out of these minidump's? Btw. I fixed the Clonecd problem causing the BSOD (outdated app.) Thanks for any help!
BSOD Help and Support

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 08:39.
Twitter Facebook Google+