New
#1
Windows 7 64bit Ultimate BSOD
So I built a new computer, and had various hardware issues. All hardware has been replaced and checked to insure it's good. So I'm not sure why I keep getting these errors.
Please see attached file.
So I built a new computer, and had various hardware issues. All hardware has been replaced and checked to insure it's good. So I'm not sure why I keep getting these errors.
Please see attached file.
Hello aspnerd and welcome to Sevenforums.
* What did you install just after you installed Windows on your new pc?
BSOD Analyse
Cisco & BSOD issues
As far as I'm concerned, people have had problems with Cisco back in the days, it's listed as a Problem Device. Can you uninstall this for a trial? If you spent money on it, contact the costumer service as it's not really my type of expertise.
Best Regards,Code:Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64 ROOT\NET\0000 This device is disabled.
Frederik.
Oh I see, let's proceed to Memtest86+.
Combining your crash dumps and the general view of BSODs culprits, I'd suggest you to have a look at your memory, the sticks. Through decades people have been using the bootable tool called Memtest86+ and it's basically very unique in these manners.
Be sure to check your warranty rules and regulations before opening your case.
* Memtest86+ is USB-ready, and can be booted directly from it. Download the flashdrive wizard.
* To ensure that either your sticks OR your motherboard slots are broken, it's necessary to do the below procedure-
* Pull out all sticks except ONE, scan it.
* If no errors, pull the scanned stick into another slot.
* Proceed like this until you've scanned all sticks individually, and all the slots.
Best Regards,
Frederik.
Have you had any new BSOD since then?
Are you able to catch the newest 3 dumps?
To ensure minidumps are enabled:
* Press Start, in the Search Box type: "sysdm.cpl" (without the quotes), press Enter.
* Select the Advanced tab, click on Startup and Recovery Settings.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information headline select Small memory dump (256 kB) in the dropdown box.
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK till you're out of the dialogue.
* Reboot if changes have been made.
I reset the mini dumps as you have below. It hasn't BSOD, but it's frozen on me several times. Last night, I got 4 of these messages:
the instruction at 0x0000000075C39A7A referenced memory at 0x0000000075C39A7A the required data was not placed into memory because of an i/o error status of 0xc000000e
the same exact message 4 times in a row before the system rebooted.
Let's enable Verifier--
Best Regards,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) - and create a System Repair Disc (Win7) if you don't have a full installation DVD.
You can do this by going to Start...All Programs...Maintenance...Create a System Repair Disc (don't forget to test the disc to make sure it works).
For Vista, you can download the repair discs from different websites. If unable to locate them, shoot me a PM and I'll point you to them.
For Win8, BSOD's are different - and we'll have to adjust how we do this with them.
Also, to ensure that you can recover, here's another couple of additional steps:
- Get to the Safe Mode menu (rapidly tap F8 just before the Windows splash screen comes up). Scroll down to and select "Disable automatic restart on System Failure"
- Get the RED information from this picture (in particular we will need the name of the file that the error occurred in):
Picture of a BSOD
Then, here's the procedure to run Driver Verifier:
- 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 "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ("Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it),
- 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 (an estimate on my part).
Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions.
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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Frederik.
so, it's not creating the mini dump files, so I changed drives...
Alright, if you can get it to crash with or without Verifier enabled, it's cool.
As long as we'll get some crash dumps it's cool.
BTW:
Updating System Specs will give us a better sight of
how your system is put together. It's simply done.
§ Download Speccy
§ |User CP (top of the page)| |Edit System Spec|
§ COPY & PASTE section to section
§ Include Laptop, Desktop information
§ End with |Save Changes|
Best Regards,
Frederik.