BSOD after windows reinstall.

#1
I recently reformatted and reinstalled windows 7, but now I keep getting random BSOD's. I have no idea what is causing it except for maybe something driver related.
 


Attachments

#2
RAM is the problem as it is set so wrong in the bios. Load 'optimized defaults' to set the memory right:

400 Mhz 6-6-6-18 1.8v
 


#3
Now when I go into the bios options my computer keeps crashing. It also crashes when windows is booting most of the time, but when I get past that it is somewhat stable. I don't know what to do.
 


#4
I would keep trying untill reflashing bios.

In your motherboard manual, look for this "Optimized defaults" setting so you know where it is in the bios setup exactly. Then enter bios and load defaults.
 


#5
I managed to get fully through all the settings and I didn't see an optimized defaults setting anywhere, is there any other names it might go under?

Also most of the time it crashes pretty instantly so I have no chance to do anything.
 


#6
Optimized defaults : yes, can come under different names, consult your motherboard manual. If you can't reset the bios you may want to simply reflash it.

I would also run bootable memtest Memtest86+ - Advanced Memory Diagnostic Tool. to see how many passes it'll do before crashes, and watch if it actually detects any errors.

The problem might also come from the Power Supply.
 


#7
I don't have any manuals :\
Could it possibly be Load Setup Defaults?
 


#8
I don't have any manuals :\
Could it possibly be Load Setup Defaults?
That's it, Load Setup Defaults. Don't forget to save before you exit the bios setup.

If it crashes again after you load defaults, reattach your CPU-Z current settings.
 


Captain Jack

Extraordinary Member
#10
Hello and Welcome !

Few basics things uninstall ESET use this article ESET Knowledgebase - How do I manually uninstall my ESET security product? until we finish our troubleshooting until then you could use Microsoft Security Essentials

Run a Hardware Diagnostic Hardware Diagnostic !! (Hard drive especially) because the dump blames IDE/ATAPI Port Driver i.e atapi.sys

Update the driver AGRSM.sys Mon Nov 10 20:26:37 2008 - SoftModem Device Driver

Bugcheck:

Code:
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 856e2908, Physical Device Object of the stack
Arg3: 8296aae0, Functional Device Object of the stack
Arg4: 87063990, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  87063990

DEVICE_OBJECT: 856e2908

DRIVER_OBJECT: 856dfdb8

IMAGE_NAME:  atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf13

MODULE_NAME: atapi

FAULTING_MODULE: 8a311000 atapi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82880054 to 82920d10
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.