Windows 7 freezes 9 minutes after login on winfast motherboard (probably driver issue) (also in this

S

Skybuck Flying

Hello,

My DreamPC from 2006 has been having this problem ever since the motherboard
was replaced with a winfast motherboard.

Driver installation was something problematic as windows detects a chip
wrongly and it must be removed by telling windows to ignore that driver.

After this step is done windows 7 detects all chips correctly and installs
drivers.

However I noticed something during driver installation and also after
installation.

It seems once of the drivers causes some kind of problem/bug to occur, it
tries to display a message, it only came through a few times via some kind
of kernel message facility.

It seems to by-pass the normal windows desktop gui. It looked gray and
whitesh... very rare.

I think it has something to do with visual studio and the known problems
with it's distribitubles/libs which contained some kind of flaw.

Can't remember which one exactly... msdev or something dont know.

So I suspect one of the drivers is causing a delay/deadlock or message
display of about 9 minutes.

Here is an event log of it to show the time ship:

Information 17/3/2013 9:31:03 Service Control Manager 7036 None
Information 17/3/2013 9:31:02 Service Control Manager 7036 None
Error 17/3/2013 9:22:40 Service Control Manager 7011 None
Information 17/3/2013 9:22:09 UserPnp 20001 (7005)

Here are the details of it:

Log Name: System
Source: Service Control Manager
Date: 17/3/2013 9:31:03
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DREAMPC2006
Description:
The Software Protection service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="16384">7036</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2013-03-17T08:31:03.675781200Z" />
<EventRecordID>114842</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="940" />
<Channel>System</Channel>
<Computer>DREAMPC2006</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Software Protection</Data>
<Data Name="param2">stopped</Data>
<Binary>7300700070007300760063002F0031000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 17/3/2013 9:31:02
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DREAMPC2006
Description:
The Multimedia Class Scheduler service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="16384">7036</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2013-03-17T08:31:02.675781200Z" />
<EventRecordID>114841</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="3864" />
<Channel>System</Channel>
<Computer>DREAMPC2006</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Multimedia Class Scheduler</Data>
<Data Name="param2">stopped</Data>
<Binary>4D004D004300530053002F0031000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 17/3/2013 9:22:40
Event ID: 7011
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DREAMPC2006
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction
response from the WPDBusEnum service.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7011</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2013-03-17T08:22:40.957031200Z" />
<EventRecordID>114840</EventRecordID>
<Correlation />
<Execution ProcessID="464" ThreadID="1644" />
<Channel>System</Channel>
<Computer>DREAMPC2006</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">30000</Data>
<Data Name="param2">WPDBusEnum</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 17/3/2013 9:22:09
Event ID: 20001
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: DREAMPC2006
Description:
Driver Management concluded the process to install driver
FileRepository\volume.inf_amd64_neutral_2509122af013a38e\volume.inf for
Device Instance ID
STORAGE\VOLUME\{A1055875-8EDB-11E2-AE8B-00016CC868F6}#0000000000000000 with
the following status: 0x0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp"
Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-03-17T08:22:09.912109300Z" />
<EventRecordID>114839</EventRecordID>
<Correlation />
<Execution ProcessID="2628" ThreadID="2632" />
<Channel>System</Channel>
<Computer>DREAMPC2006</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<InstallDeviceID
xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events"
xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>FileRepository\volume.inf_amd64_neutral_2509122af013a38e\volume.inf</DriverName>
<DriverVersion>6.1.7600.17122</DriverVersion>
<DriverProvider>Microsoft</DriverProvider>
<DeviceInstanceID>STORAGE\VOLUME\{A1055875-8EDB-11E2-AE8B-00016CC868F6}#0000000000000000</DeviceInstanceID>
<SetupClass>{71A27CDD-812A-11D0-BEC7-08002BE2092F}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>false</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>Generic volume</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>

Furthermore today I also detected a virus called: explore.exe (without the
r) it was in C:\Users\Skybuck\AppData\Local\Temp\explore.exe

I copyied the virus/trojan to a special folder in case I want to examine or
upload it later so perhaps other people can examine it.

It's already detected by virus scan total... it seems to be a generic virus
but also a new spin off about 2 weeks old... I wonder how it got onto my
computer.

HEUR virus or something... anyway I removed it manually... the PC was having
the freezing issues way before this virus came on it... so it's unrelated...
just like to report this virus as well.

It probably came onto my PC via internet explorer which has hopefully be
patched by now ?!

I shall be watching my computer a little bit more closely to see if the
virus/trojan runs... I also wonder if anything was stolen.

I write this report just to show that even windows 7 is not safe and cannot
be trusted.

For now I would just like to solve the freezing issue... it's kinda
stupid... it's not a problem for me because I can do something else while
waiting 9 minutes... but if I am ever in a hurry then it could become a
problem.

So I wonder if anybody has installed windows 7 on a winfast motherboard and
experienced the same problem and found a fix.

I will tell you the exact motherboard model so you can compare if you had
the same one in such a case:

Well guess what you guys shit out of luck, my information virtual disk didnt
mount properly so cannot retrieve that information right now... kinda
weird... tried re-attaching it but no go.

Using vhd-attach to do it... for auto mount... I wonder if perhaps
vhd-attach has something to do with the freezing... probably not...

Also perhaps GT 520 drivers from nvidia have something to do with it... but
probably not... I thought that maybe the driver issues/freezing issues went
away with 7900 gtx card instead... but probably not...

Perhaps later I will post the exact motherboard... it was something with a K
in it though... a socket 939... and SLI version... and older one... it was
the only socket 939 replacement motherboard I could get my hands on...

Perhaps later I will try to find a winfast driver for windows 7... it
probably doesnt exist... I already tried searching for it in the past.

This ofcourse kinda sucks... so definetly no winfast hardware for me in
future ;)

One odd thing though... the memory seems to be twice as fast as old
motherboard but maybe the test wasn't done right or whatever... only 3GB
being used... the 4GB not available because of bios issue...

Ofcourse not going to flash it... flashing from unreliable floppy disks is
insane... and also windows flash doesnt work... and flash from cd cannot
work because of write-protection... when trying to dump old bios... so bad
advice given by even winfast itself... very bad.

Fortunately people on the internet warned for it... so I pass it along to
you ;)

Bye,
Skybuck.
 
S

Skybuck Flying

Perhaps it's skype related, probably not but not sure, from application
logs:

Information 17/3/2013 9:31:03 Security-SPP 903 None
*Information 17/3/2013 9:23:39 SkypeUpdate 103 Service Events
Information 17/3/2013 9:21:46 Desktop Window Manager 9003 None
Information 17/3/2013 9:21:45 Winlogon 6000 None
Information 17/3/2013 9:21:45 Winlogon 4101 None
Information 17/3/2013 9:21:41 Security-SPP 902 None
Information 17/3/2013 9:21:41 Security-SPP 1003 None
*Error 17/3/2013 9:21:41 IBG_gds_db 212 None
Information 17/3/2013 9:21:41 Security-SPP 1066 None



*SkypeUpdate service is shutting down due to idle timeout.

**

The description for Event ID 212 from source IBG_gds_db cannot be found.
Either the component that raises this event is not installed on your local
computer or the installation is corrupted. You can install or repair the
component on the local computer.

If the event originated on another computer, the display information had to
be saved with the event.

The following information was included with the event:

The registry information is missing.
Please run the InterBase Configuration Utilit

All of this probably has nothing to do with it... I still think it's same
weird driver bug... relying on flawed microsoft libraries.

Bye,
Skybuck.
 
S

Skybuck Flying

In case you were wondering which motherboard it is for which the drivers
freeze for 9 minutes, I think it's this one or something very samiliar:

http://www.foxconnchannel.com/ProductDetail.aspx?T=motherboard&U=en-us0000008

Winfast/Foxxconn:

NF4SK8AA-8EKRS


The driver installation issue is already a known issue... and a solution for
that is somewhere on the internet, as mentioned it requires telling windows
to ignore installing or detecting a certain device/chip on the
motherboard...
by telling windows to exclude that driver/device from the detection list or
something.

Unfortunately after installing the default windows drivers it still causes
the bootup/login freeze up of 9 minutes.

Also having an internet connection helps windows 7 to download the correct
drivers for this motherboard after the flawed/wrong detection is fixed.

Somehow the driver is affected by microsoft libraries which had to be
replaced because of vunerabilities...

So it's a cause of microsoft library hell... affecting the driver somehow...
the kernel tries to communicate this to the user in some odd way.

Bye,
Skybuck.
 
S

Skybuck Flying

Microsoft libraries causing the driver bug is probably something like msvrt
or mscrt or something like that... can't remember exactly but it's a very
well known library...

Bye,
Skybuck.
 
S

Skybuck Flying

mscvrt or something...

some advice mentioned to run, this checks important system files and might
repair them.

sfc /scannow

from admin console... so my PC is doing that now... hopefully nothing bad
will happen.

I dont expect anything to get fixed but with ms software one never knows.

I will report back if my PC survives this scan ;)

Bye,
Skybuck.
 
S

Skybuck Flying

It got paused somehow because I accidently selected some text or
something...

But then I noticed it, selected something or pressed something and it
continued.

It completed, no problems found:

"
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>
"

Bye,
Skybuck.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top