Windows 10 Windows error 0x000001d3

Neemobeer

Cloud Security Engineer

Staff member

Joined

Jul 4, 2015

Messages

8,998

• Nov 1, 2016

• #2

As far I know 1D3 isn't a valid bug check code. My debugger wouldn't even load the dump file, maybe kemical will have better luck. I did see it struggle to load symbols for the wireless driver qualcomm atheros extensible wireless lan device driver Qcamain10x64. I would start by updating this driver it's pretty old.

 

Upvote 0 Downvote

cbeardsley

New Member

Joined

Nov 1, 2016

Messages

6

• Nov 1, 2016

• Thread Author
• #3

Thanks. I'm not all that technical but I'm pretty sure it is to do with the wireless device drivers as you suggest. The thing is though, when I search for updates online (with the built in search function) it says there are no newer updates for this device. If I search manually, how would I find an update that the device itself didn't find, if that makes sense! Thanks in advance

 

Upvote 0 Downvote

Neemobeer

Cloud Security Engineer

Staff member

Joined

Jul 4, 2015

Messages

8,998

• Nov 1, 2016

• #4

There is a driver from 01/11/2016 here
ASUSTeK Computer Inc. -Support- Driver & Tools - E200HA

 

Upvote 0 Downvote

cbeardsley

New Member

Joined

Nov 1, 2016

Messages

6

• Nov 1, 2016

• Thread Author
• #5

Great. Will give that a try. Thanks

 

Upvote 0 Downvote

cbeardsley

New Member

Joined

Nov 1, 2016

Messages

6

• Nov 1, 2016

• Thread Author
• #6

Well I've spent around 4 hours trying to get that download to work. It works fine to download the driver installer but when the install wizard is finsihed there is no update to the driver. Completely baffled! Tried all sorts of ways to install the thing and whenever I go in to check the driver it's the same old thing sitting there from 2015

 

Upvote 0 Downvote

Neemobeer

Cloud Security Engineer

Staff member

Joined

Jul 4, 2015

Messages

8,998

• Nov 1, 2016

• #7

You can delete the driver from an elevated command prompt

• Type pnputil -e
• Locate the wireless driver and make note of the oem##.inf name
• Type pnputil -f -d oem##.inf
• Try re-installing the newer driver or from the same command prompt you can type cd C:\pathtonewdriver.inf
• pnputil -a C:\pathtonew*.inf and that should install it

 

Upvote 0 Downvote

cbeardsley

New Member

Joined

Nov 1, 2016

Messages

6

• Nov 1, 2016

• Thread Author
• #8

On point 2, do you mean the current (old one)?

Maybe just me being stupid but I can't get C:\....
It starts with C:\windows\system32 as default. Am I in the wrong place?

 

Upvote 0 Downvote

Neemobeer

Cloud Security Engineer

Staff member

Joined

Jul 4, 2015

Messages

8,998

• Nov 1, 2016

• #9

pnputil will list out all the drivers, for point 2 you just specific the file name oem##.inf for the current driver.

 

Upvote 0 Downvote

cbeardsley

New Member

Joined

Nov 1, 2016

Messages

6

• Nov 1, 2016

• Thread Author
• #10

It gave me the error message:
Adding the driver package failed: Invalid INF passed as parameter

 

Upvote 0 Downvote

kemical

Essential Member

Joined

Aug 28, 2007

Messages

36,176

• Nov 1, 2016

• #11

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1D3, {3ce, 0, 0, 0}

Probably caused by : Qcamain10x64.sys ( Qcamain10x64+114c6e )

Followup:     MachineOwner
---------

Hi,
as Neemobeer correctly say's it does look like this driver is to blame (although something else might be causing it to crash).

This driver is also known as the Qualcom Atheros driver as well as Killer suite and when you install it or un-install it you must turn off any security apps you have running. Also when re-installing right click on the driver and run as admin.

I also see your running McAFEE which is known to cause issues from time to time. Please remove and just use the on board Defender as it's ultra stable and probably far better than McAFEE.

You also have some Asus drivers dating from 2009:
ASMMAP64.sys Thu Jul 2 10:13:26 2009: ATK Hotkey ATK0101 ACPI UTILITY Please update:
ASUSTeK Computer Inc. -Support- Driver & Tools - E200HA

 

Upvote 0 Downvote

Solution

kemical

Essential Member

Joined

Aug 28, 2007

Messages

36,176

• Nov 1, 2016

• #12

I downloaded the update for your driver and it looks like one and the same as your already running.
File version: 11.0.0.10212

If you look in the uninstall programs area you should be able to see what version you have installed.

 

Upvote 0 Downvote