Random BSOD on a new computer, Error 0X0000001E.

[Holowcow]

Hello, This is my first BSOD.
Please Help.
I've attached the zip file.
Thank you in advance.

 

[koolkat77]

Hello and welcome Cow

It's hard to say anything with that one dump.

So we'll enable driver verifier to rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Driver Verifier

I'd suggest that you first backup your data 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/Windows 7 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 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
- 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 (an estimate on my part).

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.
Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

 

[Holowcow]

Thanks for your help, I prefer not to use this tool unless I will get another BSOD.
For the meantime everything seems OK.

 

[koolkat77]

Alrighty then.

 

[Holowcow]

Another BSOD

Here is the new zip file.
Thanks

 

[koolkat77]

Sorry to keep you waiting. I just realized I missed this thread from my subscription.

Anyway, the BSoD seems to be caused by

BugCheck C2, {7, 109b, 410041, fffffa80129d3010}
Probably caused by : athurx.sys ( athurx+6d9e )
STOP 0x000000C2: BAD_POOL_CALLER
Usual causes:  Device driver, ?Memory
------------------------------------
6: kd> lmvm athurx
start             end                 module name
fffff880`04414000 fffff880`045f2000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: athurx.sys
    Image name: [COLOR="red"]athurx.sys[/COLOR]
    Timestamp:      [COLOR="Red"]  Wed Apr 20 16:07:45 2011[/COLOR] (4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for driver updates, Source: Driver Reference Table