New build need help QUICK

[dklhutto]

have asrock 770de motherboard
gtx 460 pny
gskill 2x2gb 10666 8-8-8-21 ddr3 1333
amd 965 be quad core cpu
antec earthwatt 500 watt psu

cant get to run stable freezes blue screen bsod window 7 32bit os did not do clean install of os didnt want loose pitures or ole lady will kill me lol or to reinstall game s and programs but it does run please help

 

[mcnumpty23]

make sure your memory has been set to the correct speed and voltage in the bios

 

[RussK1]

have asrock 770de motherboard
gtx 460 pny
gskill 2x2gb 10666 8-8-8-21 ddr3 1333
amd 965 be quad core cpu
antec earthwatt 500 watt psu

cant get to run stable freezes blue screen bsod window 7 32bit os did not do clean install of os didnt want loose pitures or ole lady will kill me lol or to reinstall game s and programs but it does run please help

http://phyxion.net/Driver-Sweeper/Driver-Sweeper/Version-3-1-0/

enter safe mode and use driver sweeper and wipe all the previous boards drivers and re-install the new boards drivers... this is assuming you can get into windows... if not you'll have to re-install windows. Don't worry, windows will automatically see that there's an existing windows OS and will save everything to the C:Windows old folder... will have to re-dowload/install games and programs but atleast you'll have your pics and such. REMEMBER it is ALWAYS a good idea to do a back up ANYTIME you do a hardware change... IMPERATIVE.

PS - what Asrock 770de is it??

A770DE+

M3A770DE

??

 

[dklhutto]

it is the M3A770DE

and i have done the driver sweep

 

[dklhutto]

and i have finnally got all the timing and voltage set was a trick doing it but cpu-z shows the right settings now need to test and with what do i need to test this rig?

 

[sportsfanboy]

What error are you getting?

 

[mcnumpty23]

test it by doing what you normally do on your pc--or to test it really hard try running prime 95

 

[dklhutto]

i was geting nividia windows kerrnal mode driver thing but havnt seeen that latelysince i did the driver sweep and clean install of nividia drivers now im getting pc lock and have to reset i need away to test what i did with timing to see if that was the proble and another question is my psu under powered

 

[dklhutto]

im think i will try prime 95 is there a quick test to it ?

 

[mcnumpty23]

what is the voltage set to for your ram? my bios always sets 1.5v by default when my ram needs 1.65v to run at 1600mhz

 

[mcnumpty23]

you can stop the prime 95 test any time you want--theres no actual time--ie it doesnt run 10 minutes then stop itself

 

[dklhutto]

what is the voltage set to for your ram? my bios always sets 1.5v by default when my ram needs 1.65v to run at 1600mhz

mine is set to 1.5v and that is what the ram needs and what gskills recommends as std

 

[mcnumpty23]

if thats the manufacturers recommended voltage for the speed you are running the ram at thats ok--you can always run memtest to check the ram a couple of passes normally is enough--errors usually show really quickly

if you have important photos on there you really should get a flash drive and back them up they are so cheap now cos sooner or later you will end up losing them

 

[RussK1]

i was geting nividia windows kerrnal mode driver thing but havnt seeen that latelysince i did the driver sweep and clean install of nividia drivers now im getting pc lock and have to reset i need away to test what i did with timing to see if that was the proble and another question is my psu under powered

Could be your video cards drivers... uninstall the video drivers and re-install the gtx drivers (use driver sweeper). If your timings are 8-8-8-21 @ 1.5v you're good there. Bad drivers for the video card will lock the comp. up so try that.

let us know what happens.

The power supply is fine, a little wimpy but nonetheless alright...

 

[mcnumpty23]

Could be your video cards drivers... uninstall the video drivers and re-install the gtx drivers (use driver sweeper). If your timings are 8-8-8-21 @ 1.5v you're good there. Bad drivers for the video card will lock the comp. up so try that.

let us know what happens.

he already said he did the video driver and driver sweep bit earlier

 

[RussK1]

uninstall and re-install the video drivers... and DON'T run prime95... it's asinine to run it when your comp is already locking up. Find what's causing the lock ups and fix it then run what ever stress programs you want.

Go to the start menu and type in "windows memory diagnostic", select it and reboot.

 

[dklhutto]

last blue screen
memory_management
0x000008e (0x0000411 , 0xc046ab00 , 0x00315AFC , 0xc000003
then reboot then this
0x000008e {0xc0000005, 0x90e73888 , 0xa51bba40 , 0x00000000
afd.sys

 

[RussK1]

last blue screen
memory_management
0x000008e (0x0000411 , 0xc046ab00 , 0x00315AFC , 0xc000003
then reboot then this
0x000008e {0xc0000005, 0x90e73888 , 0xa51bba40 , 0x00000000
afd.sys

Take out the memory and run windows memory diagnostic with one stick at a time. It won't take that long being you only have two sticks. You might have gotten defective memory. The standard for that board is 1600mhz memory, but I don't think it would be a prob running slower memory.

 

[RussK1]

...also note run the memory in different slots, while it is very possible that you have a bad stick you could have a bad socket.

 

[dklhutto]

...also note rum the memory in different slots, while it is very possible that you have a bad stick you could have a bad socket.

well ran memory diagnostic came back cleanwith both sticks in it and asrock motherboard has 4 slot it is recommended to in stall 1600 ram in a2 and b2 slots and have check compatibility ram for this board and is supported for what i have and they are installed in a1 and b2 slots


and this post have new bsod
0x0000008e
0x80000004
0x85960002
0x8e152c1f
0x00000000

 

[RussK1]

well ran memory diagnostic came back cleanwith both sticks in it and asrock motherboard has 4 slot it is recommended to in stall 1600 ram in a2 and b2 slots and have check compatibility ram for this board and is supported for what i have and they are installed in a1 and b2 slots


and this post have new bsod
0x0000008e
0x80000004
0x85960002
0x8e152c1f
0x00000000

run chkdsk and select attempt recovery of bad sectors - reboot. Also what AV are you running?

 

[dklhutto]

run chkdsk and select attempt recovery of bad sectors - reboot. Also what AV are you running?

microsoft essintial for av

 

[RussK1]

microsoft essintial for av

Quoted this from Microsoft's website:

BCCode: 8E 0x0000008E is same as 0x1000008E

Cause
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.
Common exception codes include the following:
0x80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques:
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.
If you do not know the specific cause of the exception, consider the following items:
Hardware incompatibility. Make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If the bug check message lists a driver by name , disable or remove that driver. Also, disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the system by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x1E. You can disable memory caching of the BIOS to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation.
You can resolve BIOS problems by upgrading the system BIOS version

BCCode: 8E 0x000008E 0x1000008E - read this link
http://www.faultwire.com/solutions-fatal_error/KERNEL-MODE-EXCEPTION-NOT-HANDLED-0x0000008E-*1151.html?order=date

 

[dklhutto]

Quoted this from Microsoft's website:

BCCode: 8E 0x0000008E is same as 0x1000008E

Cause
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.
Common exception codes include the following:
0x80000003: STATUS_BREAKPOINT indicates that a breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
Resolving the Problem
If you are not equipped to debug this problem, you should use some basic troubleshooting techniques:
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.
If you do not know the specific cause of the exception, consider the following items:
Hardware incompatibility. Make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
If the bug check message lists a driver by name , disable or remove that driver. Also, disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you have to start the computer by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the system by using the Recovery Console and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x1E. You can disable memory caching of the BIOS to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and .chk files that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation.
You can resolve BIOS problems by upgrading the system BIOS version

BCCode: 8E 0x000008E 0x1000008E - read this link
http://www.faultwire.com/solutions-fatal_error/KERNEL-MODE-EXCEPTION-NOT-HANDLED-0x0000008E-*1151.html?order=date

now im totally lost what to do and what the prob is

 

[RussK1]

now im totally lost what to do and what the prob is

Alright, you did not re-install windows when you changed out your hardware right? If not then I firmly believe that's where the problem lies... you need to get into safe mode and sweep ALL of the drivers and reboot. Once into windows you can install the driver disk that came with the board and install. Repeat the steps for video card. If the Problem persists, take out memory and run with one stick. If this doesn't work, switch video plugs. I'm 90% sure you have a driver problem... it sucks I know, but if you don't want to do a clean install you have no other choice.