Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Problems with new Win7 PC


19 Jul 2010   #1

Windows 7 64bit
 
 
BSOD Problems with new Win7 PC

Hello, I'm having a bit of trouble with a new machine of mine that's only a few months old and running on Windows 7 64 bit.

It started sometime in June when my PC began randomly crashing. The screen would split into lots of little lines and hang then a blue screen would display and my PC would restart. Often it would then get back in only to restart two or three more times, but then would settle down again and rarely happen.

I thought this had something to do with rendering movies in Sony Vegas as it began happening around the time I was doing quite a bit of that and when using the program now it pretty much guarantees a crash before, during or after a render, but I also stopped doing it totally and moved over to rendering on a Windows 7 64bit laptop and it has not had the same problem...while my new PC persists with crashing.

I am not over clocking. The PC is not over heating. I have tested my memory and system in general with Sandra Lite and no errors were found. I have also ran Windows Memory tester when it suggested to do so after failing startup on one occasion about three times and again no errors were found at all. I believe my drivers are all up to date and have used Devise Doctor to check this. I have reinstalled my graphics drivers. I have ran a virus scan. Other than using Sony Vegas, it only tends to happen when just sitting on desktop, perhaps browsing the net and so on but has yet to happen while any kind of game is running.

Attached is a collection of numerous minidumps created by windows (I suspect most of them are for the crashes after a main crash and as a result point wrongly to ntoskrnl.exe, but I could be wrong and require any assistance available to get to the bottom of this. It feels like I've tried everything.

My System SpecsSystem Spec
.

19 Jul 2010   #2
Microsoft MVP

 
 

18 memory dumps from 30 Jun to 19 Jul 2010 (~3 weeks)
5 different STOP errors, blaming 11 different causes
This is most likely a hardware/compatibility problem.

Please start with these free diagnostics:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, if the above tests pass, I'd try these free stress tests:
Quote:
FurMark download site: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Quote:
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
This driver is very outdated, please update it:
Quote:
Afc.sys Wed Jul 12 01:48:20 2006 - Arcsoft(R) ASPI Shell (CD/DVD program)
It belongs to a CD/DVD program on your system

BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 12:59:50.430 2010 (UTC - 4:00)
System Uptime: 0 days 2:07:01.741
BugCheck 3B, {c0000005, fffff80002ec16b4, fffff88009517a00, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+124 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  msnmsgr.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 10:52:20.355 2010 (UTC - 4:00)
System Uptime: 0 days 8:51:32.667
BugCheck 3B, {c0000005, fffff80002e92349, fffff88009d070f0, 0}
Probably caused by : win32k.sys ( win32k!NtUserPostMessage+fe )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 07:20:13.837 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:46.148
BugCheck 1E, {ffffffffc0000005, fffff800031949b8, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!NtQueryDirectoryObject+1e4 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  explorer.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 07:14:58.335 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:47.036
BugCheck 1E, {ffffffffc0000005, fffff880031b3e10, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!WfpRefreshEntryLru+5c )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 06:10:05.040 2010 (UTC - 4:00)
System Uptime: 0 days 1:28:06.741
BugCheck 3B, {c0000005, fffff80002fc190d, fffff8800a1fbe90, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 17 04:41:29.827 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:24.513
BugCheck 27, {baad0073, fffff88007d988d8, fffff88007d98140, fffff88002c37c3e}
Probably caused by : rdbss.sys ( rdbss!RxLowIoWriteShellCompletion+2e )
PROCESS_NAME:  System
BUGCHECK_STR:  0x27
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 03:12:03.210 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:35.911
BugCheck 1E, {ffffffffc0000005, fffff800031badb7, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpReceiveMessage+654 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  csrss.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 17:50:45.176 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:25.051
BugCheck 24, {1904fb, fffff88007fbc8a8, fffff88007fbc110, fffff800020ac11b}
Probably caused by : Ntfs.sys ( Ntfs!NtfsMapStream+5b )
PROCESS_NAME:  Regcleaner.exe
BUGCHECK_STR:  0x24
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 17:37:15.137 2010 (UTC - 4:00)
System Uptime: 0 days 2:28:31.838
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeTranslateCompletedRequest+232 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 15:06:51.749 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.450
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
BugCheck 1000007E, {ffffffffc0000005, fffff88002ac2ae1, fffff880009a8848, fffff880009a80b0}
Probably caused by : avgldx64.sys ( avgldx64+2cae1 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 13:44:07.403 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:10.714
BugCheck 1000007E, {ffffffffc0000005, fffff880041750a4, fffff88002993108, fffff88002992970}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 13:42:30.296 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:48.607
BugCheck 3B, {c0000005, fffff80002e8369f, fffff88008a99aa0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+10f )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  msnmsgr.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 12:42:34.029 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:37.730
BugCheck 1000007E, {ffffffffc0000005, fffff80002e8a882, fffff880031a8298, fffff880031a7b00}
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
Probably caused by : tdx.sys ( tdx!TdxDeactivateTransportAddress+1a6 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 12:40:20.689 2010 (UTC - 4:00)
System Uptime: 0 days 2:30:25.390
BugCheck 3B, {c0000005, fffff960000d4bd2, fffff8800a4adbd0, 0}
Probably caused by : win32k.sys ( win32k!FreeObject+12 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 10:03:11.634 2010 (UTC - 4:00)
System Uptime: 0 days 0:42:47.336
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
BugCheck 1000007E, {ffffffffc0000005, fffff880047e26b2, fffff880078ef488, fffff880078eecf0}
Probably caused by : atikmdag.sys ( atikmdag+1c16b2 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 08:59:16.931 2010 (UTC - 4:00)
System Uptime: 0 days 3:58:35.632
BugCheck 3B, {c0000005, fffff880041360a4, fffff88006cdb810, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  vlc.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul  6 04:54:58.552 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:51.863
BugCheck 1E, {ffffffffc0000005, fffff880091bac70, 0, 0}
Probably caused by : tcpip.sys ( tcpip!IN6_ADDR_EQUAL+4 )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun 30 06:15:25.469 2010 (UTC - 4:00)
System Uptime: 0 days 1:19:36.170
BugCheck 3B, {c0000005, fffff80002f073e9, fffff88006cf10f0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiUnlinkWaitBlocks+61 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WerFault.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
  
  
 
My System SpecsSystem Spec
20 Jul 2010   #3

Windows 7 64bit
 
 

Thank you for the quick reply and to offer up so many things to try. I am currently working through the suggestions, but I have a question about the outdated driver you found; Afc.sys.

My Windows Update doesn't find anything needing to be updated and neither does Device Doctor and if I search my pc for that file it finds nothing. So basically I'd like to know what this file is, where it is on my pc since I can't seem to find it, and how I'd go about updating it? I tried various google searches and didn't have much luck since it seemed to point to XP or Vista related problems.

The fact it's from Arcsoft made me think it was part of Total Media Extreme, which I use to capture footage to be used for rendering, but I have updated that as well and had done prior to these problems starting. I have uninstalled, reinstalled and updated it over again just in case though. I also checked compatibility with Win 7 and it's fine too.


Here's the other test results so far:

HD Tune scan: 0% damaged blocks found.
Malware test run: 0 threats found.
My System SpecsSystem Spec
.


20 Jul 2010   #4

Windows 7 64bit
 
 

While running the passes on Memtest86, during the end of pass1 it found an error, from there it exponentially started counting up errors until it stopped at a total of 274432 and then moved on to pass 2. At time of writing this I have still left it going.

I guess that means bad RAM is to blame then? Very annoying if that is the case given how new this PC is.
My System SpecsSystem Spec
20 Jul 2010   #5

Microsoft Window 7 Professional 32 bit
 
 

It's possible that bad motherboard slots, please test individual Ram stick to choose a good one, then test it on different motherboard slots. It will take quite a lot of times but then you will fully know about the whole situation. Another possibility is the compatibility. It is possible that all of your Ram stick are ok but they are not uniform, you will know for sure after using memtestx86 on individual Ram stick as I mentioned.

Regard,

Tuan
My System SpecsSystem Spec
20 Jul 2010   #6
Microsoft MVP

 
 

HD Tune is a generic test - please use the test from the manufacturer of your hard drive.

Afc.sys is associated with the Arcsoft(R) ASPI Shell
This is a component of a CD/DVD program
If you don't know which one it is, rename the afc.sys file to afc.BAK
Then reboot and see if it affects any of your CD/DVD programs.
My System SpecsSystem Spec
Reply

 BSOD Problems with new Win7 PC




Thread Tools



Similar help and support threads for: BSOD Problems with new Win7 PC
Thread Forum
Win7 install problems no HDD detected & BSOD 1month later. Installation & Setup
Win7 SP1 Problems Windows Updates & Activation
Got some problems with my win7 X64 BSOD Help and Support
Win7 X64 - x86 problems... General Discussion
Win7 USB Problems Hardware & Devices
Win7 sporadic BSOD problems BSOD Help and Support
win7 64 bit ram problems Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 04:43 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33