BSOD rare? 1e error?

vexedbredrin · 20 Jul 2010

Howdy folks.
if you can take the time to go over my issue id be very grateful.
ive had this hp pavillion desktop for no more than two months, pretty much the whole time ive been trying to avoid taking it back to the shop, (as i already made about 4 journeys with other complications) anyway, not sure where to start other than here;
this is the error code i got:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072010-18345-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-34008-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

when i try to search for WER-34008-0.sysdata.xml, its not on my pc anywhere?
theres only one other exact error report (in english) on google... the others are in japanese, and again, id be really grateful for any help... thanks in advance.

richc46 · 20 Jul 2010

Follow these instructions:
https://www.sevenforums.com/crashes-d...tructions.html

These are the usual causes of BC 1E
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

To other members, I will be on a travel status, so feel free to help this member.

vexedbredrin · 21 Jul 2010

ok thanks, so heres the files:
Attachment 86520

richc46 · 21 Jul 2010

Something was not done correctly, the mini dump (the most important file) is not there. I think that you did not run as adminsitrator. Read the instructions, again.

vexedbredrin · 21 Jul 2010

second attempt
Attachment 86546
that should be good...

Jonathan_King · 21 Jul 2010

The most straightforward reading of your dumo is that your Atheros network adapter drivers are the cause. They are outdated, so try to find an update.

If that doesn't work, disable the real-time prtotection of Malwarebytes, and remove AVG with this tool: http://download.avg.com/filedir/util...removerx64.exe

Replace them with MSE: http://www.microsoft.com/security_essentials

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 21 00:21:48.561 2010 (UTC - 4:00)
System Uptime: 1 days 8:53:22.449
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+103 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

vexedbredrin · 21 Jul 2010

I appreciate your time, thanks a lot, im pretty sure its the driver as i had the same problem before i had avg or malwarebytes on my system.

Jonathan_King · 21 Jul 2010

Sure, go ahead and update it. If the problem persists, you know to remove the anti-virus.

Good luck, we will be awaiting update. :)

vexedbredrin · 21 Jul 2010

I'm pretty sure its the driver as i had the same problem before i had avg or malwarebytes on my system.
However, should i even have atheros drivers for a belkin wireless G network adapter? i searched a list of Atheros Network Driver Downloads, and belkin wasnt there?
also, im using a dongle.. arent atheros drivers for wireless cards or wouldnt it make a difference?

Jonathan_King · 21 Jul 2010

vexedbredrin said:

I'm pretty sure its the driver as i had the same problem before i had avg or malwarebytes on my system.
However, should i even have atheros drivers for a belkin wireless G network adapter?
also, im using a dongle.. arent atheros drivers for wireless cards or wouldnt it make a difference?
so close yet so far..

Apparently your Belkin card used those drivers. See this snip from your msinfo32.sys:

Attachment 86556