Random BSODs

[majkl]

Hi, I would greatly appreciate any help with solving my BSODs related PC issues. I get blue screens randomly when browsing the internet, playing WoW, watching videos, even got one when I was AFK.
In the attachment there are specs of my computer exported from msinfo32, as well as some of the last minidumps. When I viewed them in BlueScreenView, I noticed that they are caused mostly by ntoskrnl.exe, with various error messages (MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION etc.)
Thanks in advance

 

[zigzag3143]

Hi, I would greatly appreciate any help with solving my BSODs related PC issues. I get blue screens randomly when browsing the internet, playing WoW, watching videos, even got one when I was AFK.
In the attachment there are specs of my computer exported from msinfo32, as well as some of the last minidumps. When I viewed them in BlueScreenView, I noticed that they are caused mostly by ntoskrnl.exe, with various error messages (MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION etc.)
Thanks in advance

Memory corruption probably caused by a driver. You do realize that you have driver verifier running right?

I would run memtest after turning verifier off, then re-enable verifier and run it to catch which driver.


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

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[majkl]

Thanks for quick reply.
I will try memtest and post back with results.
As for the driver verifier, I tried it to find out which driver is the cause of my crashes, and then turned it off using Start -> verifier.exe /reset, but I guess I messed something...

 

[zigzag3143]

Thanks for quick reply.
I will try memtest and post back with results.
As for the driver verifier, I tried it to find out which driver is the cause of my crashes, and then turned it off using Start -> verifier.exe /reset, but I guess I messed something...

Good luck

 

[majkl]

OK, I am sorry I haven't posted earlier, but I was busy with school.
I let memtest run overnight (like 10 passes), and no errors were detected. But I didn't manage to test the sticks independently, I wasn't sure which settings to modify, so I didn't change anything. I took a picture for you.
Also, I zipped some new minidumps.
Thanks for helping.
Regards, Majkl
PS I don't know where you found that I had verifier turned on, could you please check again? I tried the reset command line option multiple times, but just to be sure.

 

[zigzag3143]

OK, I am sorry I haven't posted earlier, but I was busy with school.
I let memtest run overnight (like 10 passes), and no errors were detected. But I didn't manage to test the sticks independently, I wasn't sure which settings to modify, so I didn't change anything. I took a picture for you.
Also, I zipped some new minidumps.
Thanks for helping.
Regards, Majkl
PS I don't know where you found that I had verifier turned on, could you please check again? I tried the reset command line option multiple times, but just to be sure.

Memory corruption verifier not enabled so driver was not named

 

[majkl]

Well I guess that now I should move to step 2: driver verifier?

 

[zigzag3143]

Well I guess that now I should move to step 2: driver verifier?

good idea

 

[majkl]

I had a crash with driver verifier enabled.
Now I turn it off? And how do I give you the results, please?

 

[zigzag3143]

I had a crash with driver verifier enabled.
Now I turn it off? And how do I give you the results, please?

Yes. Turn it off and upload the dmp file

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.

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.

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.

 

[majkl]

This is my dmp after a crash with verifier enabled

 

[zigzag3143]

This is my dmp after a crash with verifier enabled

Driver verifier was not enabled for this DMP. It was blamed on memory corruption.

These were caused by a memory corruption Please run these two tests to verify your memory and find which driver is causing the problem.


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

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[majkl]

I am a bit confused here. Memtest told me there were no errors. It ran over night for approximately 10 hours.
As far as driver verifier is concerned, I am completely lost. I did everything that was in your tutorial step by step, waited for crash, even checked that it was enabled afret reboot (I looked at verifier -> display settings). Then I posted the one dmp it produced. If it says my verifier was off, maybe there is a super secret option somewhere to enable dumps with verifier?

 

[zigzag3143]

I am a bit confused here. Memtest told me there were no errors. It ran over night for approximately 10 hours.
As far as driver verifier is concerned, I am completely lost. I did everything that was in your tutorial step by step, waited for crash, even checked that it was enabled afret reboot (I looked at verifier -> display settings). Then I posted the one dmp it produced. If it says my verifier was off, maybe there is a super secret option somewhere to enable dumps with verifier?

No super secret switch. If you type verifier /query it will tell you which drivers it is verifying. If none it is off.

 

[majkl]

When I type verifier /query, the terminal just pops and disappears right away, so I cannot read it. But I guess that it should tell me the same thing as the display existing settings option in the gui...
Anyway, I am going to try again now

 

[majkl]

I got this... If it is not enabled now, then I really will cry