Random BSOD on Windows 7 Professional 64bit. I'm not sure where to start on this. I have checked drivers and updated BIOS etc but problem seems to remain. Sometimes nothing happens and all is fine for days and then all of a sudden BSOD's are everywhere for a while and then disappear again. Would the DMP file from the most recent BSOD help? If so, how do I get it to anyone that might be interested? <object height="1" id="plugin0" style=";z-index:1000;" type="application/x-dgnria" width="1"><param name="tabId" value="{EF81AAEB-AE01-419B-B7FF-733C354AE77A}" /></object>

Have you checked your RAM? That can cause random failures. Google MemTest, it is free I think and a good tester.

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible. You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking. If you are overclocking stop. (chances are if you dont know if you are, you are not) To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure: * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine. * Zip up the copy. * Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply. To ensure minidumps are enabled: * Go to Start, in the Search Box type: sysdm.cpl, press Enter. * Under the Advanced tab, click on the Startup and Recovery Settings... button. * Ensure that Automatically restart is unchecked. * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies). * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump. * OK your way out. * Reboot if changes have been made. Please also run MSinfo32 and upload the output as well. To run MSinfo32 please go to start>run>MSinfo32 Go to "file" "save" and upload the saved file with the DMPS (Instructions for XP, Vista, Win 7, Win 8)MS-MVP 2010, 2011, 2012 Team ZigZag

Have you checked your RAM? That can cause random failures. Google MemTest, it is free I think and a good tester.

We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible. You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking. If you are overclocking stop. (chances are if you dont know if you are, you are not) To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure: * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine. * Zip up the copy. * Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply. To ensure minidumps are enabled: * Go to Start, in the Search Box type: sysdm.cpl, press Enter. * Under the Advanced tab, click on the Startup and Recovery Settings... button. * Ensure that Automatically restart is unchecked. * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies). * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump. * OK your way out. * Reboot if changes have been made. Please also run MSinfo32 and upload the output as well. To run MSinfo32 please go to start>run>MSinfo32 Go to "file" "save" and upload the saved file with the DMPS (Instructions for XP, Vista, Win 7, Win 8)MS-MVP 2010, 2011, 2012 Team ZigZag

Hi whenever it happens check the even viewer. you can run who crashed software as well to verify the root cause. Is it a laptop or desktop if it is a desktop check your RAM. As you mentioned that sometimes it works fine so there are possiblites that RAM could be the root cause if it is a desktop unplug all the wire connected to the computer and open your system unite , don't touch any component just check the RAM to make sure it's properly fixed in slots sometiems RAM is not properly fixed in the slots or not locked .

Hi whenever it happens check the even viewer. you can run who crashed software as well to verify the root cause. Is it a laptop or desktop if it is a desktop check your RAM. As you mentioned that sometimes it works fine so there are possiblites that RAM could be the root cause if it is a desktop unplug all the wire connected to the computer and open your system unite , don't touch any component just check the RAM to make sure it's properly fixed in slots sometiems RAM is not properly fixed in the slots or not locked .

Hi, According to the BSOD issue, you can refer to Bug Check Code Reference (Windows Debuggers). To check the this issue, please locate the dump file in the \Windows\Minidump folder and upload it so that we can analyze it. Hope this helps Vincent Wang TechNet Community Support

<object height="1" id="plugin0" style=";z-index:1000;" type="application/x-dgnria" width="1"><param name="tabId" value="{36C3B188-6DDB-43E0-BD65-9E758E7A11BC}" /></object> Ok, I have posted the minidump files at this link: http://www.njduispecialists.com/minidumpfiles.zip The above files were saved with the setting of "Kernel memory dump." I have changed the setting to 256KB as per your instructions. I am not overclocking at this time, all normal/default settings as far as I can tell. Here is the link for the Msinfo32 saved file: http://www.njduispecialists.com/systeminfo.zip

Hi, According to the BSOD issue, you can refer to Bug Check Code Reference (Windows Debuggers). To check the this issue, please locate the dump file in the \Windows\Minidump folder and upload it so that we can analyze it. Hope this helps Vincent Wang TechNet Community Support

<object height="1" id="plugin0" style=";z-index:1000;" type="application/x-dgnria" width="1"><param name="tabId" value="{36C3B188-6DDB-43E0-BD65-9E758E7A11BC}" /></object> Ok, I have posted the minidump files at this link: http://www.njduispecialists.com/minidumpfiles.zip The above files were saved with the setting of "Kernel memory dump." I have changed the setting to 256KB as per your instructions. I am not overclocking at this time, all normal/default settings as far as I can tell. Here is the link for the Msinfo32 saved file: http://www.njduispecialists.com/systeminfo.zip

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem. *Dont forget to upload any further DMP files (especially those when verifier is running) *If you are overclocking anything reset to default before running these tests. In other words STOP!!! If you dont know what this means you probably arent 1-Memtest. *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org *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. 2-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. *I'd suggest that you first backup your data 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). *In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . 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 "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. *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. *Further Reading "http://support.microsoft.com/kb/244617"MS-MVP 2010, 2011, 2012 Team ZigZag

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem. *Dont forget to upload any further DMP files (especially those when verifier is running) *If you are overclocking anything reset to default before running these tests. In other words STOP!!! If you dont know what this means you probably arent 1-Memtest. *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org *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. 2-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. *I'd suggest that you first backup your data 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). *In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . 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 "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. *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. *Further Reading "http://support.microsoft.com/kb/244617"MS-MVP 2010, 2011, 2012 Team ZigZag

I have not had a chance to run the memtest yet, however, I did try your verifier idea. The system did go to BSOD within about 3 minutes of login. BSOD appeared to freeze and no minidump file was created. I tried it a few more times but the same thing happen, no dump file and BSOD appeared to freeze on the "Initializing disk for crash dump..." step. Not sure if that helps? I am going to try and get the memtest86 done in the next day or so. I ended up doing a system restore and got be back to where I began at least.

I have got the memtest done, one stick continually comes up with errors. I am going to RMA that stick and hopefully that solves the problem. Running with 16GB currently and system is stable, no signs of impending BSOD yet. Might have been just the stick I think.

Can you turn off verifier (type verifier /reset) and upload the DMP files that happened while it was on. If one stick showed any errors can you run memtest with the known good stick and test all the mobo slots so we will know if it is the stick or mobo slot. MS-MVP 2010, 2011, 2012 Team ZigZag

I cannot get BSOD to produce any dump files from those crashes still. I have tested all slots with all four sticks and the same stick comes up bad no matter what slot while the remaining 3 sticks are good no matter what slot. I sent for RMA to G.Skill, has lifetime warranty should not be an issue.

Kyle Good job and good luckMS-MVP 2010, 2011, 2012 Team ZigZag

Kyle Good job and good luckMS-MVP 2010, 2011, 2012 Team ZigZag

The RMA stick is back and in service again. That was the entire problem, just a bad stick. Back up to full 32GB for about three weeks now and not one single problem. Thank you to everyone for the assistance.

KD Glad you are working. You would be surprised how many times it is RAMMS-MVP 2010, 2011, 2012 Team ZigZag