Windows 7 Ultimate 64
-full retail
-system hardware is less than 6 months old
-tried reinstalling OS once
Whenever I need to restart or shutdown the system I get the BSOD and when the system reboots it tells me that windows has just experienced an unexpected crash
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.
Memtest.
RAM - Test with Memtest86+*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.
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.
In addition to JMH's suggestions please remove the applecharger as the most recent crash was caused by it. You can charge using the USB bus by itself.
JMH I let the Memtest86+ run overnight and passed 7 times with no errors. I then turned the verifier on as you instructed and forced the BSOD. (It didn't take long) I had to boot into safe mode as Windows kept freezing otherwise. Here are the dump files. Thankyou for the help. ZigZag I also ensured that the Applecharger service was disabled.
ZigZag I went into the System32 file and deleted all instances of the applecharger.sys/applecharger.exe. Hopefully that will eliminate the apple charger problem. JHM I was finally able to update the raid by completely updating the bios through the @gigabyte program. Here is the latest round of .dmp files. the most current on was today. I still cannot seem to get the verifier to work. Windows freezes ( blank screen) before I can even boot into it. I was able to access safe mode but no BSOD from there. Thanks again for your help.
Most recent crash from 3/10/12 @ 5pm was related to, you guessed it, AppleCharger.
Code:Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\031012-25256-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64 Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03e06000 PsLoadedModuleList = 0xfffff800`0404b670 Debug session time: Fri Mar 9 15:22:58.309 2012 (UTC - 5:00) System Uptime: 0 days 8:43:39.650 BugCheck 1E, {ffffffffc0000005, fffff800041674ea, 0, 4e} *** WARNING: Unable to verify timestamp for AppleCharger.sys *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
ZigZag I deleted and reinstalled itunes, I removed all mention of applecharger from the system32 and system registry, and I disabled the applecharger service through the administrative tools. So far I haven't had anoth BSOD since doin all that. It looks like applecharger is finally gone and the problem is fixed. Why do you think that the applecharger was such a pain to get rid of and why would it cause such a problem? Thankyou for all your help.
The BSOD has returned. It happens every time the computer restarts
Quote