Random BSOD playing WoW

[jeroenlucassen]

Hi all,

I read the instructions and will attach my dump files and report as a zip file.

I build my system myself, but the last few weeks i keep getting BSOD.

AMD quad core
Asus motherboard
8 gb Geil memory
Asus GPU

The dump file shows ntoskrnl is the driver causing the BSOD
Another dump file says ElRawDSK causes BSOD

Both offcourse are drivers, but i dont know how to fix this problem.
Really need some help

Thx in advance

 

[zigzag3143]

Related to dddskx64.sys RawDisk Driver. Allows write access to files and raw disk sectors for user mode applications in Windows 2000, XP, 2003, Vista, 2008. from EldoS Corporation. Yours is from 2008 and needs to be updated or removed

Also Related to SSPORT.sys 32bit Port Contention Driver from Samsung Electronics.Yours is from 2005 and needs the same


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
http://www.carrona.org/dvrref.php

 

[jeroenlucassen]

Maybe a noob question, but can i just go to my system32/drivers folder and delete the drivers you mentioned before?

 

[zigzag3143]

Maybe a noob question, but can i just go to my system32/drivers folder and delete the drivers you mentioned before?

Just to be safe try renaming them to *.bak so they cant load, and that way if the system needs it all you would have to do is rename them back

 

[jeroenlucassen]

Ok, i deleted the SSport.sys file. The other driver, dddskx64.sys i cant find on my system.
I had another BSOD just now, caused by yet another driver Bleu screen viewer says.

I attached a new dump file, hope this is usefull.

 

[zigzag3143]

Ok, i deleted the SSport.sys file. The other driver, dddskx64.sys i cant find on my system.
I had another BSOD just now, caused by yet another driver Bleu screen viewer says.

I attached a new dump file, hope this is usefull.

Old drivers still present (see snip)

This crash was related to hardware

124 Error for desktops not under warranty. If you are at all uncomfortabe dont do it.


This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).


Remove ALL power and reseat all cards, memory and cables (on both ends) - actually remove and replace - do not just snug.

Make sure the system has adequate ventilation - add a small fan blowing into intakes.

Carefully inspect the motherboard and other cards for damage. Pay attention to the fatal hardware error implication.You may need a real computer shop (not leeks and peeks at a BestBuy or other BigBox stores) or the System maker's Support.

Check the processor seatting, heat sink, and the compound between the processor and
the heat sink which are common causes.

There have been a few instances where Norton/Symantec and other antivirus/security
programs have caused this error.

BCCode: 124 0x00000124

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug
check indicates that a fatal hardware error has occurred. This bug check uses the error
data that is provided by the Windows Hardware Error Architecture (WHEA).

0x00000124 <-- read this link
http://www.faultwire.com/solutions-...rectable-hardware-error-0x00000124-*1289.html

 

[jeroenlucassen]

Thanks for the comment zigzag.

Since i build the system myself, im gonna take it apart completely, and then rebuild it. I doubt there is a heat problem, but i will check nonetheless. I have a coolermaster tower with 3 chassis fans and a watercooled tower on the cpu, with fan. My cpu rarely goes above 45 degrees C and my motherboard is always 25 degrees C. As shown in Bios. I will reaply the heatsink on my cpu, specially add some new cooling pasta.

This evening i got a new BOSD. But this time AVG, my virus scanner popped up with an unknown error after the BSOD reboot. I have seen this before but not too many times. I completly removed AVG, to see if this makes any difference.

Again i will add the new dump files. Tonight it was ntoskrnl driver that caused the crash, at least thats what Blue Screen Viewer tells me.

Also i heared a faulty RAM card could be the problem here. I have 4x4 GB Geil Dragonmasters in my system, i will swap out pairs of two to see if that helps. I already checked these cards for faults, found nothing though.

Thanks again for the reply, hope i get this problem solved soon.

Jeroen

 

[zigzag3143]

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted

PLEASE RUN THESE TWO TESTS



These crashes were caused by memory corruption/exception (Cx05) probably a driver.
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 a 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-7 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.

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

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[jeroenlucassen]

Hi all,

I took my system completely apart, and then rebuild it again. Found two things that where not as it should be. First, my powersupply draws fresh air from the bottom of my tower. Since we have cats, i placed the tower on a box, so the front fan doesnt suck up all the cat hairs . By placing the tower on a box, half of the air intake of the powersupply was blocked and mostly covered with dust.

Second was more worrying. I took the coolerblock of my cpu, but after reinstalling it i noticed these strange clamps used to tighten the coolerblock on the cpu, where not fastened at all. Might be over time the screws losened up, not sure.

Cleaned the whole system and rebuild it. If i get more BSOD i will start on doing memtests, and driver verifier. I have to wait for the weekend before i have enough spare time to do so anyway.

For now, the system seems stable, no chrasses till now. If the BSOD return i will get back to you guys, for now thanks allot for your time and effort!

Jeroen.