Rather random BSODs occurring

[Blue Wisp]

Hello,

I am currently using a Windows 7 x86 OS in a laptop I had since 2007, 2 GB RAM, everything's cool. It originally came with a Windows Vista Home Premium x86 OS, but after a few troubles I upgraded to Windows 7 Home Premium x86 around late 2010 I believe. It works like a charm.

Lately though I've been getting a really degrading performance, it's like the computer has mood swings of sorts and has good days where it works like the best laptop I ever had or it sometimes work like a complete waste. It's sort of annoying too... I've been suffering various problems ranging from performance problems to - The most important problem - Random BSODs that interrupt my work in the worst possible times.

It ranges from win32k.sys BSODs to MEMORY MANAGEMENT BSODs every now and then, it's... Annoying.

I found out how to do the minidump options two days ago, I activated it and so far I got two BSODs that got successfully dumped, I followed the instructions in the topic above and I got these files as a result attached.

So yeah, if anyone could help me out with my problem, I'd be really thankful.

 

[zigzag3143]

These crashes were caused by memory corruption/exception (Cx05) 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 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.

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






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)

 

[Blue Wisp]

Driver Verifier sounds risky...

I heard about Memtest a while ago, how long would the process take?

 

[zigzag3143]

Which verifier or memtest? You need to do both.

 

[Blue Wisp]

I left Memtest running the whole night last night, and this morning I found it with... 19 passes and 0 errors.
So I guess all I have left to do is Driver Verifier yes? Eh... I'm a bit scared to do it though, specially that part where I may not be able to get my PC back should something go wrong.

 

[writhziden]

If you have a second computer to work with, it is not that risky. We can walk you through getting the computer back and running in the event that Verifier causes problems.