BSOD Every 1h

Hi, My system keeps showing me a BSOD every 30min to 1h all of a sudden. I tried to follow the instruction on making a dump file but for some reason it dose not seem to be generating anything...

I made a video showing me making the dump encase I am doing something wrong.

2012-05-24_0425 - Josh81's library

Please let me know what I am doing wrong so I can go a head and upload the dump file.

Thanks

Try this way...

We do need the 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.

Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
If empty (or non existent) please look in the following folders. C:\windows (the dmp should be called memory.dmp), and C:\windows\LiveKernelReports\Watchdog.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "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.

Ok, I was able to get the minidump file. I have attached it to this post.

Thank You!

Just on a side note, before the BSOD I get an error window say that windows 7 was not able to write to memory or something like that, due to an I/O error.

Dose anyone have any insight on this issue?

* Kaspersky is a frequent cause of BSOD's.

I suggest you remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloa...vremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows


* It wouldn't hurt to run SFC as well.

Note you may need to run it 3 times to fix any problems.
Reboot at the end please.
Let us know the results.

SFC /SCANNOW Command - System File Checker

Ok, I removed Kaspersky and Installed Microsoft Essentials. I did a scan and it did find 1 trojan called: meredrop which it has deleted. I ran the SFC /SCANNOW Command and did not get any errors.

I have since then rebooted, and the error still continues.

Is there anything else I can try to resolve this?

Thanks for taking the time out to help thus far, it is much appreciated!

Referring back to what you said in your Post 4.... you could run Memtest & Verifier if you wish...

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

* If you have a Raid update its Driver.



Memtest.

*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-7 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.

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).

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"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

Still no luck, Memtest did not show me any errors and actually it was able to run for 10h+ without a single bsod (My Pc Usually Crashes Within 1-2h) . So then I thought it might be a system problem (windows) and I went ahead and reformatted my PC with no luck.

I noticed cursial released a firmware update for my 64GB SSD OS driver and I went ahead and upgraded it a few moments ago. Hopefully this fixes the issue but I would really like to get to the bottom of this.

In the meantime is there anything else I would be able to try?

Driver Verifier???
Have you run that yet?