Frequent BSODs after power outage

Memory corruption probably caused by a driver you have drivers from as far back as 2001



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

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

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.

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.

Old drivers

Code:

PS2.sys    6/4/2001 9:59:59 AM        
PxHelp20.sys    3/12/2008 9:57:44 PM      
evbdx.sys    12/31/2008 12:06:23 PM       
bxvbdx.sys    2/13/2009 6:10:59 PM        
b57nd60x.sys    4/26/2009 7:15:34 AM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Thanks zigzag3143! I updated my post maybe you can re-check it. I will try all of that right now and I will update you if there is still BSODs in my PC.

radicalsniper said:

Thanks zigzag3143! I updated my post maybe you can re-check it. I will try all of that right now and I will update you if there is still BSODs in my PC.

Good job and good luck

Are you still there zigzag? Can you help me with those? I'm having a hard time finding those drivers..

radicalsniper said:

Are you still there zigzag? Can you help me with those? I'm having a hard time finding those drivers..

Related to PS2.sys Related to Hewlett-Packard Company.

Related to PxHelp20.sys Px Engine Device Driver for Windows 2000/XP

Related to evbdx.sys NetXtreme II 10 GigE VBD from Broadcom Corporation.

Related to bxvbdx.sys NetXtreme II GigE VBD from Broadcom Corporation.

And when I restarted my PC, it immediately crashed. It says ksbus.sys I think. I restarted it 2 times and still that error appeared. But when I tried Safe mode, it booted successfully and I removed Driver Verifier settings.. But sad to say, there was no Dump file saved.

Am I in the right direction?


EDIT: Thanks for those drivers!

radicalsniper said:

And when I restarted my PC, it immediately crashed. It says ksbus.sys I think. I restarted it 2 times and still that error appeared. But when I tried Safe mode, it booted successfully and I removed Driver Verifier settings.. But sad to say, there was no Dump file saved.

Am I in the right direction?


EDIT: Thanks for those drivers!

There might be a log in event viewer


Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

Here..

radicalsniper said:

Here..

You appear to be infected