Wireless Card Problem (802.11N 300Mbps PCI CARD)

MeveM

MeveM

Bright Spark
Hello again dear PCS members.

Been a while since I was last on here but it seems I've come across a problem with my network card that's been there since day one. I never really bothered to get it fixed with the warrenty while it was active as I simply opted to use a network cable instead. Thought it'd eventually go away :p

So here's my problem, similar to this thread but the fix did not work for me: https://www.pcspecialist.co.uk/forums/showthread.php?11094-Wireless-Card-Problem

My card is: ONBOARD GIGABIT LAN & WIRELESS 802.11N 300Mbps PCI CARD

What I'm experiencing is that 50% of the times I start my PC it gets into windows, tries to load up the internet connection and I get a bluescreen. I can't remember what the bluescreen says nor do I remember how to make it so it doesn't restart before I can read it. It then restarts itself and usually starts working properly again after 1-2 restarts. It then works perfectly fine except for the odd disconnection from the internet. (Very rare).

I have now moved house and the Virgin box is too far away for me to use a network cable. I'm only worried about the reboots in case it damages my PC.

I have tried reinstalling it multiple times, I have tried uninstalling it and letting windows install all the drivers itself without using the CD provided with the card, I also noted about a week ago that there was a windows update that actually included a update for my network card but it did nothing to sort my problem.

Anyone got any ideas?
 
ubuysa

ubuysa

The BSOD Doctor
So we don't know whether the wifi has ever worked?

I know you tried the uninstall suggestion in the other thread but I'm going to ask you to try it again. In Device Manager, right-click on your wifi card and click uninstall. When it asks you whether you want to delete the driver(s) answer Yes, then reboot. Now install the driver supplied to you by PCS. See how that does. If there is additional software on the disk (control, debug, connection software etc.) install that too. If there are any diagnosis tools provided in there run them, if there is a logging feature in there start that too. One thing I would suggest is that you not use is any third-party connection tool, even one supplied with the card. Just use Windows to manage connections, in my experience Windows is much better at it. :)

Also take a look in the Event Viewer at the Critical and Error entries to see whether anything useful has been logged in there.

Of course, tom_gr7's solution is probably more reliable - just not as much fun. ;)
 
MeveM

MeveM

Bright Spark
Event Viewer:

Session "Homegroup Log" failed to start with the following error: 0xC0000035

+ System

- Provider

[ Name] Microsoft-Windows-Kernel-EventTracing
[ Guid] {B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}

EventID 2

Version 0

Level 2

Task 2

Opcode 12

Keywords 0x8000000000000010

- TimeCreated

[ SystemTime] 2013-07-15T15:37:09.284848300Z

EventRecordID 2647

Correlation

- Execution

[ ProcessID] 476
[ ThreadID] 5216

Channel Microsoft-Windows-Kernel-EventTracing/Admin

Computer Levitation

- Security

[ UserID] S-1-5-18


- EventData

SessionName Homegroup Log
FileName
ErrorCode 3221225525
LoggingMode 285212677


______________________________________________________________________

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2013-07-15T15:37:09.284848300Z" />
<EventRecordID>2647</EventRecordID>
<Correlation />
<Execution ProcessID="476" ThreadID="5216" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>Levitation</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="SessionName">Homegroup Log</Data>
<Data Name="FileName" />
<Data Name="ErrorCode">3221225525</Data>
<Data Name="LoggingMode">285212677</Data>
</EventData>
</Event>


__________________________________________________________________________

Source: Kernel-Power

+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2013-07-15T15:36:11.284413700Z

EventRecordID 334297

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Levitation

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 254
BugcheckParameter1 0x5
BugcheckParameter2 0xfffffa80080971a0
BugcheckParameter3 0x80861c2d
BugcheckParameter4 0xfffffa8008e68908
SleepInProgress false
PowerButtonTimestamp 0

____________________________________________________________________________

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2013-07-15T15:36:11.284413700Z" />
<EventRecordID>334297</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Levitation</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">254</Data>
<Data Name="BugcheckParameter1">0x5</Data>
<Data Name="BugcheckParameter2">0xfffffa80080971a0</Data>
<Data Name="BugcheckParameter3">0x80861c2d</Data>
<Data Name="BugcheckParameter4">0xfffffa8008e68908</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

___________________________________________________________________________
 
MeveM

MeveM

Bright Spark
Event 27, e1cexpress

Intel(R) 82579V Gigabit Network Connection
Network link is disconnected.

Friendly View:

- System

- Provider

[ Name] e1cexpress

- EventID 27

[ Qualifiers] 40964

Level 3

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2013-07-15T06:13:10.938333800Z

EventRecordID 333850

Channel System

Computer Levitation

Security


- EventData


Intel(R) 82579V Gigabit Network Connection
0000040002003000000000001B0004A00000000000000000000000000000000000000000000000001B0004A0


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00040000 00300002 00000000 A004001B
0008: 00000000 00000000 00000000 00000000
0010: 00000000 00000000 A004001B


In Bytes

0000: 00 00 04 00 02 00 30 00 ......0.
0008: 00 00 00 00 1B 00 04 A0 .......
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 1B 00 04 A0 ...

________________________________________________________________

XML View

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="e1cexpress" />
<EventID Qualifiers="40964">27</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-15T06:13:10.938333800Z" />
<EventRecordID>333850</EventRecordID>
<Channel>System</Channel>
<Computer>Levitation</Computer>
<Security />
</System>
- <EventData>
<Data />
<Data>Intel(R) 82579V Gigabit Network Connection</Data>
<Binary>0000040002003000000000001B0004A00000000000000000000000000000000000000000000000001B0004A0</Binary>
</EventData>
</Event>
 
ubuysa

ubuysa

The BSOD Doctor
I'm not an expert at reading these things but I'll have a stab.

The first event you listed is just Homegroup complaining about no being able to start it's log. That's not likely to be a BSOD issue I don't think, in any case there's nothing in there that's terribly helpful.

The third event (in the separate post) is because your network cable was unplugged I think. Nothing serious there either.

But the second event is very interesting:

MeveM said:
Source: Kernel-Power

+ System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2013-07-15T15:36:11.284413700Z

EventRecordID 334297

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Levitation

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 254
BugcheckParameter1 0x5
BugcheckParameter2 0xfffffa80080971a0
BugcheckParameter3 0x80861c2d
BugcheckParameter4 0xfffffa8008e68908
SleepInProgress false
PowerButtonTimestamp 0
Click to expand...

The Bugcheck Code one this one (254 or 0x000000FE) indicates it's for a USB driver, and indicates "a hardware failure because of a bad physical address", see http://msdn.microsoft.com/en-us/library/windows/hardware/ff560407(v=vs.85).aspx). The Vendor Id is for Intel so I'm guessing it's probably for your wifi card but the device Id there is not listed (it's in Parameter 3).

This might be a hardware problem of course, especially since you suspect it's been there from day one. You might try disabling the wifi card (in Device Manager). I realise that will give you no Internet access but at least you should see whether the BSDOs stop. If they do, it's probably hardware related.

One point, when you say "start up your PC" is this a cold boot or a restore from hibernate or sleep? If you're using hibernate or sleep try cold booting for a few days and see whether that stops the BSODs?

I really would try what I suggested in post #4 and uninstall the device, reboot and reinstall the PCS-supplied driver (and any control software that came with it).

What happens if you delete the wifi profile (and thus stop Windows connecting to your router automatically)? Do you get BSODs without it trying to connect? Can you then connect manually afterwards?

I'm at a loss to know how to help more. If none of the above helps then I'd suggest you call PCS, they know this stuff a lot better than I do.

:)
 
ubuysa

ubuysa

The BSOD Doctor
kruppsy said:
If you see tom's rep as 31 you're well on your way...
Click to expand...

Well thank you. :eek:

I really don't know that much about Windows diagnostics but analysing that kind of data, looking up error codes, unscrambling parameter lists etc. was bread-and-butter when I was a large mainframe systems programmer. So I'm really just poking around in the dark with Windows applying the techniques I learned as a mainframe sysprog to the Windows environment. I've always thought that it's not so much what you know that matters, it's knowing what to look for and where to go to find it that counts.

:detective:
 
MeveM

MeveM

Bright Spark
Haven't tried the things ubuysa has said yet but I thiought I'd just throw in another thing, my partner used this network card in her PC before we moved and it worked fine on her PC. She never got any of the bluescreens I did. Both using windows 7.
I only ever encounter this bluescreen when I have the network card in my PC.
 
MeveM

MeveM

Bright Spark
ubuysa said:
One point, when you say "start up your PC" is this a cold boot or a restore from hibernate or sleep? If you're using hibernate or sleep try cold booting for a few days and see whether that stops the BSODs?
Click to expand...

When I say start I mean from scratch. I never leave my PC in sleep or hibernate. Whether it's first thing in the morning or when I'm back from work I tend to get the bluescreen in question. I've also found that after the bluescreen I have at a few points been stuck at a point in boot where it says my overclocking has failed. I haven't got any overclocking, PCS did not do it for me nor have I, so I just reboot yet again which normally gets it working again.
 
ubuysa

ubuysa

The BSOD Doctor
MeveM said:
Haven't tried the things ubuysa has said yet but I thiought I'd just throw in another thing, my partner used this network card in her PC before we moved and it worked fine on her PC. She never got any of the bluescreens I did. Both using windows 7.
I only ever encounter this bluescreen when I have the network card in my PC.
Click to expand...

Well I think that's proof positive that the card causes the BSODs. There must be something about your hardware that the card doesn't like (or vice-versa). It's also possible that the card is faulty but that the fault doesn't materialise or isn't triggered in your partner's PC.

I know I'm whistling in the dark here, but when you're in a hole, stop digging. The card cause your BSODs so I'd look at replacing the card.

I'd strongly suggest you talk to PCS too, they may know of any potential conflicts with your rig and that card?
 
You must log in or register to reply here.
Top