Frequent BSOD on fresh install multiple errors

[essenbe]

How are things going now?

 

[Rhin0]

has been idle since last BSOD. Attempting Windows updates again now, so far no new bsod

EDIT: source of last blue screen still unknown , was able to successfully install all windows updates except 3 security updates, which makes me really happy considering to this point i'd bluescreen when attempting any update or they would fail and revert, making progress atleast

 

[essenbe]

Koolkat will probably be on later and read the dump file, but there is a good possibility your problems are in bios settings and ram timings.

 

[Rhin0]

ive been researching this particular mobo and it seems VERY common to have the default ram timings cause bsod. you might of hit it right on the head essenbe, looks like I should set my timings to manual, just as you said 9-9-9-24-2t but im not going to jump the gun just yet, ill wait for the dmp to be read.

im wondering now if the errors I got while doing memory diagnostic were do to the timing, and I don't have a bad stick afterall.

 

[essenbe]

If you will look at the CPUz shots you provided, that's what it shows. The memory tab shows what the ram and timings are running at now. The SPD tab shows what the ram was manufacturered to run at. The different timings are for running it at different frequencies. What it is telling you is that your ram is not running anywhere near what it was manufactured to run at.

 

[Rhin0]

lol im such a novice, so after taking another look in cpu-z I relize im in single channel, It then occurs to me this is because I only have 1 damn stick installed xD. The other stick was removed after memory diagnostics pointed to it as causing errors. so now my cpu-z shows correct readings (I went ahead and set them manually (9-9-9-24-2t) aswell as the over to 1.50v. I suppose I should now run memory diagnostic overnight and hopefully no errors occur with the manually set timing, doubt it but hey why the hell not lol

 

[koolkat77]

These Drivers need sorting, either update or should be removed completely.
jswpslwfx.sys Thu May 15 16:28:50 2008
AsUpIO.sys Mon Jul 6 08:21:38 2009
ASACPI.sys Thu Jul 16 09:31:29 2009
Other than that I would continue to diagnose hardware with Steve.

[FONT="Lucida Console"]Debug session time: Thu Jul 25 01:00:00.249 2013 (UTC + 6:00)
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
System Uptime: 0 days 0:13:34.623
Probably caused by : ntkrnlmp.exe ( nt!RtlImageNtHeaderEx+3f )
BugCheck 1E, {ffffffffc0000005, fffff800030a732f, 0, 7efa0000}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Bugcheck code 0000001E
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!RtlImageNtHeaderEx+3f
BiosVersion = 1502   
BiosReleaseDate = 11/14/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[Rhin0]

alright that's my next step then, but I havnt the slightest idea how to remove them or update them for that matter

the bottom 2 are asus related but im not finding anything @ asus for them the top one is a d-link related driver which I have no d-link products regardless cant find anything @dlink on that one, would love to remove them but not sure how to locate them.

 

[koolkat77]

Uninstall or change a program - Microsoft Windows Help

To perform a clean install of a driver, You can follow this tutorial:

How to Clean Left Over Driver Files with Driver Sweeper​

 

[Rhin0]

awesome hate having to have my hand held xD hopefully this will resolve it

 

[Rhin0]

none of these are supported by driver sweeper, no idea how I have a d-link driver, anything that had to do with asus was removed using revo, yet when searching the registry they show up, possibly just from the event.sys file? heres a ss used find feature in regedit...
1 is a AsUpIO.sys search
2 is ASACPI.sys
3 is jswpslwfx.sys

looks like the jswpslwfx can be updated or removed but the 2 asus drivers idk how to get to those....

 

[essenbe]

The ones related to Asus Utilities should be removed by uninstalling the utilities. If not go to C:/Windows/system32/drivers and do a search in the top right corner. When you find the driver, such as AsUpIO.sys , rename it to AsUpIO.bak. Then it won't load.

 

[Rhin0]

2 of the 3 were there the AsUpIO.sys was not, steps are clear from here. If issues persist with these drivers get them updated somehow, if hardware issues continue replace ram, or I have a mobo issue. all the help is very much appreciated

Edit: found the AsUpIO.sys C:\Windows\SysWOW64\drivers\

 

[essenbe]

Keep in touch and let us know how it works out for you. We do know a few more tricks.

 

[Rhin0]

jswpslwfx.sys updated via network card driver reinstallation
the other 2 drivers were converted to .bak for now. we will see, as for the ram ill run memory diagnostic overnight and see if the timing fixed the errors I previously received.

 

[essenbe]

Sounds good. let us know.

 

[Rhin0]

Got same error from stick 1 must be bad

 

[Rhin0]

removed bad stick after it tested with errors. all was well until bsod 10 minutes ago
sf file attatched

 

[essenbe]

Rhin0, I'm sure Koolkat will be back to read the dump files. But have you tested the 'good' stick of ram in the slot that tested bad? A motherboard can have bad dimm slots. The idea of testing ram is testing the sticks, but also testing the dimm slots themselves. I know what a pain this can be. I can't begin to tell you how many hours I've spent testing hardware over the years. But, unfortunately, that is the only way to help determine what is wrong on a hardware level. I would also suggest if you bought those 2 sticks as a pair, you RMA the pair and get a new pair. Ram sets are tested at the factory to work together. 2 sticks of the same kind and brand from different batches won't necessarily work well together.

 

[Rhin0]

ya 2 sticks 2 slots have fully cross tested and cleared this stick in both slots once 22passes no errors in the slot the bad stick was in, and the other slot went 14passes and 87% of the 15th

Edit: roger on the sets, I intended to buy a new set asap, rma is something that honestly didn't occur to me I do still have the recipt however its been more than 2 years not sure if they are still covered.
contacting corsair deffinatly worth a shot

having the stick test with no errors in both slots leads me to belive the dimm slots are ok, aswell as the stick. the slot that went 15passes is the empty one