Frequent BSODs after power outage

[radicalsniper]

Random BSODs after power outage, usually when playing games. When I sleep and wake up in the morning, there is no BSODs happening until there is a power outage again. Help me please..
- x86 (32-bit) or x64 ? x86
- the original installed OS on the system? Original OS
- an OEM or full retail version? OEM
- What is the age of system (hardware)? I really don't know..
- What is the age of OS installation (have you re-installed the OS?) 5 Months I think. But I am sure that it is not more than a year old.

 

[zigzag3143]

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.

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.

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

[B][COLOR=Red]PS2.sys    6/4/2001[/COLOR][/B] 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

 

[radicalsniper]

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.

 

[zigzag3143]

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

 

[radicalsniper]

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

 

[zigzag3143]

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.

 

[radicalsniper]

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!

 

[zigzag3143]

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.

 

[radicalsniper]

Here..

 

[zigzag3143]

Here..

You appear to be infected

 

[radicalsniper]

Will reformatting my pc solve the problem?

 

[zigzag3143]

Will reformatting my pc solve the problem?

If it is NOT hardware, but software, or malware, it should.

 

[radicalsniper]

Just had a system scan. Yeah, I had 2 viruses removed. No BSODs now because there is now power outage (I think). Will update you if my PC will crash. Reformatting my PC is a last resort, right?.. :\

 

[zigzag3143]

Just had a system scan. Yeah, I had 2 viruses removed. No BSODs now because there is now power outage (I think). Will update you if my PC will crash. Reformatting my PC is a last resort, right?.. :\

Just to be sure re-run malwarebytes.

 

[radicalsniper]

I ran Malwarebytes and the full scan said that there are no malwares found. I just got 3 BSODs now and here is the Minidump files. Could you please look at it what is the cause?

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\radicalsniper\032112-20812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83c44000 PsLoadedModuleList = 0x83d84230
Debug session time: Wed Mar 21 04:58:05.404 2012 (UTC - 6:00)
System Uptime: 0 days 0:03:16.294
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8793ad40, Terminating object
Arg3: 8793aeac, Process image file name
Arg4: 83e35f10, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: 8793ad40

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 00000000 

EXCEPTION_CODE: (Win32) 0xff (255) - The extended attributes are inconsistent.

BUGCHECK_STR:  0xF4_FF

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
8e3dac9c 83f17a1d 000000f4 00000003 8793ad40 nt!KeBugCheckEx+0x1e
8e3dacc0 83e6a91f 83e35f10 8793aeac 8793afb0 nt!PspCatchCriticalBreak+0x71
8e3dacf0 83e5d4c0 8793ad40 87cbab50 000000ff nt!PspTerminateAllThreads+0x2d
8e3dad24 83c7985a 00000090 000000ff 000ae3dc nt!NtTerminateProcess+0x1a2
8e3dad24 77057094 00000090 000000ff 000ae3dc nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
000ae3dc 00000000 00000000 00000000 00000000 0x77057094


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4_FF_IMAGE_wininit.exe

BUCKET_ID:  0xF4_FF_IMAGE_wininit.exe

Followup: MachineOwner
---------

Check for hard disk file system corruption and Windows corruption:

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

 

[radicalsniper]

I tried what you said, and a BSOD occured here is the DMP file. I will try it again 1 more time and see if it will permanently solve my problem. Thanks for your help.

 

[radicalsniper]

Just got 5 BSODs. It kept on saying dxgmms.sys. Please help me I can't take these bsods anymore..

 

[writhziden]

Do the following hardware checks:

• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • 
    Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

 

[radicalsniper]

Furmark said it was an error. Currently downloading DirectX. VMT said that there were no errors... and also downloading prime95.. will update you. THanks for your help

EDIT: Furmark: Requires an OPEN GL 2.0.. I am using integrated graphics. Intel gma 3100