Windows 7: New Win7 64 build, crashing

d211592 · 11 May 2010

I put my new build together two days ago, installed the OS and have run into a variety of crashes: after installing updates, while using IE, while shutting down, at the desktop. My system is:

Win 7 Ultimate 64
Intel E6300
GA-EP41T-UD3L
OCZ 2x2GB (OCZ-3G8004GK)
Seagate 500GB (ST3500418AS)Sapphire HD5670 512M GDDR5
Sony AD7240SGB 22X SATA
Linksys WMP54G

The updates I have done are:
-all important and nearly all recommended Windows Updates
-BIOS flashed
-GPU to 10.4
-Linksys is running on vista x64 drivers on enclosed driver disc (which caused my resolution to revert 800x600. So I uninstalled the ati drivers, reinstalled and my internet connection + graphics still seems okay. Though I'm thinking of installing the ralinktech ones I've seen recommended for this adapter)
-attempted some motherboard-related ones, but i'm not sure how they went.

I haven't tried to do too much else with the system yet (Office 07, Skype, games) because its still unstable.

While doing a system file check, it has gone BSOD again.

Your help would be greatly appreciated.

Jonathan_King · 11 May 2010

I wonder if your network adapter drivers are causing the issue. Update to the latest version you can find.

You should also run a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

Please upload any new dmps as they come.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 08:03:32.826 2010 (GMT-4)
System Uptime: 0 days 0:04:10.543
BugCheck A, {ffffd880009eb100, 2, 0, fffff80002a9805b}
Probably caused by : luafv.sys ( luafv!SynchronousFsControl+1ca )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 08:15:57.620 2010 (GMT-4)
System Uptime: 0 days 0:11:33.337
BugCheck A, {ffffd880009eb100, 2, 0, fffff80002a9905b}
Probably caused by : parport.sys ( parport!P5FdoThread+62 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 10 16:45:09.193 2010 (GMT-4)
System Uptime: 0 days 0:00:44.910
BugCheck D1, {fffff8000bfdc9b0, 2, 1, fffff8800625489d}
*** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 07:41:32.731 2010 (GMT-4)
System Uptime: 0 days 0:16:22.448
BugCheck 3B, {c0000005, fffff80002deb42e, fffff880029e9130, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 11 07:51:54.739 2010 (GMT-4)
System Uptime: 0 days 0:01:31.456
BugCheck 44, {fffffa8005cefb80, eae, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3ecbe )
BUGCHECK_STR:  0x44
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 10 03:59:26.441 2010 (GMT-4)
System Uptime: 0 days 0:31:10.158
BugCheck A, {fffffe8003de0918, 2, 0, fffff80002b33a2f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

d211592 · 11 May 2010

Thanks for your reply Jonathan_King.

I haven't tried updating the network adapters just yet, but I have run a memory test. I imagine the wall of red means the sticks are likely riddled with errors. Should I be making a trip back to the dealer to swap for others?

Jonathan_King · 11 May 2010

Try testing one stick at a time. Bear in mind that whenever Memtest reports errors, it can be either a RAM problem or a motherboard slot problem.

If you find a stick with no errors, test it in another slot.

That way, you can determine whether you need new RAM (and how much), or if you need a new mobo.

d211592 · 11 May 2010

I just tested one stick in the first slot and got no errors. I'll try it in another slot.

And it was error free in the third slot. Now I'll try the other stick by itself.

The other stick produced errors in the first slot. Just to be thorough, I'll third slot it.

d211592 · 11 May 2010

So one stick is good, the other bad. The policy of the store I got it from is:

"Replacement/credit will be issued if it's tested faulty within the first 7 days, otherwise, we will have to send the item away for warranty claim if it's faulty. The usual turnaround time is 14-21 working days (depending on the suppliers). We will notify you via email once the replacement/credit has been issued from our supplier."

Since 7 days haven't passed yet, I'll take it back & get another.

Jonathan_King · 12 May 2010

Sounds good, keep us posted.

d211592 · 12 May 2010

I formatted the drive and decided to reinstall the OS using the good 2gigs of ram. After that I:

Installed motherboard drivers
Installed GPU driver
Installed Microsoft Security Essentials
Installed Linksys WMP54G v4.1 using Ralink driver
Connected to the home network

Then I went to download the important windows updates (20 of them) and halfway through installation I got a crash and a BSOD. However, there's no minidump directory in the Windows one, so I can't attach it to show you. (I've changed the startup & recovery settings to write a small dump now.)

Is it possible to find useful crash data in the Event Viewer? Before the crash, restart and automatic installation of some of the updates is this event:

- <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="2010-05-12T12:07:09.860661400Z" />

<EventRecordID>1465</EventRecordID>

<Correlation />

<Execution ProcessID="516" ThreadID="3824" />

<Channel>System</Channel>

<Computer>jk-PC</Computer>

<Security />

</System>

- <EventData>
<Data Name="param1">Portable Device Enumerator Service</Data>

<Data Name="param2">stopped</Data>

<Binary>57005000440042007500730045006E0075006D002F0031000000</Binary>

</EventData>

</Event>

d211592 · 12 May 2010

After that, I've encountered:

- an error with the windows system assessment tool after trying to refresh the windows experience index
- after restarting and it installing 19 updates it must not have done before the first crash, it told me the antimalware service executable has stopped working
- I ran a system file check, and got to 9% (see attachment)
- then a BSOD when I was about to post the above here (see dump)

Thanks for your ongoing help.

d211592 · 12 May 2010

I'll try a system restore until before the windows updates and the network adapter was installed.

Windows 7: New Win7 64 build, crashing

New Win7 64 build, crashing problems?