Windows 7 BSOD on new computer I built..

K

kskwerl

New Member
Joined
Jul 9, 2010
Messages
46
Ok I'm going to give you guys the most details I can so first here is my system.

CORSAIR CMPSU-850TX 850W ATX12V 2.2 / EPS12V 2.91 SLI Ready CrossFire Ready Active PFC Power Supply

AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz Socket AM3 125W Six-Core Desktop Processor HDT90ZFBGRBOX

GIGABYTE GA-890FXA-UD5 AM3 AMD 890FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard

Scythe SCKTN-3000 92mm Sleeve "KATANA3" 3Heat Pipes CPU Cooler

G.SKILL 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Triple Channel Kit Desktop Memory Model F3-12800CL9T-6GBNQ

OCZ Agility 2 OCZSSD2-2AGTE60G 2.5" 60GB SATA II MLC Internal Solid State Drive (SSD)

XFX HD-487A-ZWFC Radeon HD 4870 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready CrossFireX Support Video Card

I also have another XFX HD 4870 which is in crossfire with the new card which is the one above.

Here a picture: The older XFX HD 4870 is the one on top, the new one is on bottom.

Ok so that's my setup.

I looked through event viewer and this is the error, now I don't know much about his stuff so this is where I'm hoping you guys are gonna come in clutch.

This is some atikmdag error and I inserted a picture of this in event viewer and it's happening a real lot.

Log Name: System
Source: atikmdag
Date: 7/23/2010 3:38:16 PM
Event ID: 43029
Task Category: DAL
Level: Error
Keywords: Classic
User: N/A
Computer: ErichTaylor-PC
Description:
Display is not active
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="atikmdag" />
<EventID Qualifiers="49152">43029</EventID>
<Level>2</Level>
<Task>42</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-07-23T19:38:16.519172700Z" />
<EventRecordID>6982</EventRecordID>
<Channel>System</Channel>
<Computer>ErichTaylor-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00000000010000002A00000015A800C0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here's another:

Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 7/23/2010 2:19:36 AM
Event ID: 10110
Task Category: User-mode Driver problems.
Level: Critical
Keywords:
User: SYSTEM
Computer: ErichTaylor-PC
Description:
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2E35AAEB-857F-4BEB-A418-2E6C0E54D988}" />
<EventID>10110</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2010-07-23T06:19:36.108555300Z" />
<EventRecordID>6760</EventRecordID>
<Correlation />
<Execution ProcessID="1012" ThreadID="1124" />
<Channel>System</Channel>
<Computer>ErichTaylor-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UMDFHostProblem lifetime="{C9035378-BC33-4126-9F20-13312B83AA03}" xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<Problem code="3" detectedBy="2">
</Problem>
<ExitCode>3</ExitCode>
<Operation code="259">
<Message>72448</Message>
<Status>4294967295</Status>
</Operation>
</UMDFHostProblem>
</UserData>
</Event>

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

I did some research on the last error and it seems other people get his error with a BSOD.

Anything else you guys need to know to help me just lemme know. Thanks in advance for any help.
 

Attachments

  • 2010-07-23_15-49-14_571[1].webp
    537 KB · Views: 579
  • atikmdag.webp
    62.7 KB · Views: 478
Solution
T
Alright. Here's what to do to get the machine under control.

1) Uninstall all Gigabyte apps which only cause problems for the masses. This means Easytune 6 and other utilities. Be glad they're removed, after.

2) This driver is too old:

Code: 
pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006
It is commonly installed with CloneDVD or similar software. What you want to do is uninstall this or related softwares to get rid of this driver. Make sure it is gone from C:\Windows\System32\drivers
- after removal.

I recommend PowerISO for drive emulation since it has perfect stability under Windows 7. The drive emulation feature remains free forever although other features require to pay, such as burning.

PowerISO - Create, Edit...
Sort by date Sort by votes
Yes, please post the crash dumps.

What may actually be causing the bsods though are your 2 Crossfire bridges. Only one should be connected between the two cards. Please remove one of them and test for now.
 
Upvote 0 Downvote
TorrentG said:
Yes, please post the crash dumps.

What may actually be causing the bsods though are your 2 Crossfire bridges. Only one should be connected between the two cards. Please remove one of them and test for now.
Click to expand...

Thanks, i'm working on retrieving the crash dumps as this is a first time doing so. Which bridge should I remove the one to he left or right?
 
Upvote 0 Downvote
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Erich Taylor\Desktop\072010-15085-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0341b000 PsLoadedModuleList = 0xfffff800`03658e50
Debug session time: Tue Jul 20 19:57:31.033 2010 (UTC - 4:00)
System Uptime: 3 days 18:24:16.891
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa800e8db000, 0, fffff880083e89f5, 0}


Could not read faulting driver name
Probably caused by : usbaudio.sys ( usbaudio!memmove+c5 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800e8db000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880083e89f5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c30e0
fffffa800e8db000

FAULTING_IP:
usbaudio!memmove+c5
fffff880`083e89f5 488b440af0 mov rax,qword ptr [rdx+rcx-10h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88007bcf560 -- (.trap 0xfffff88007bcf560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800c138fd0
rdx=00000200027a203a rsi=0000000000000000 rdi=0000000000000000
rip=fffff880083e89f5 rsp=fffff88007bcf6f8 rbp=fffffa800e8d5258
r8=0000000000000372 r9=0000000000000004 r10=0000000000000000
r11=fffff8800c138cd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
usbaudio!memmove+0xc5:
fffff880`083e89f5 488b440af0 mov rax,qword ptr [rdx+rcx-10h] ds:0001:fffffa80`0e8daffa=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000350be54 to fffff8000348b600

STACK_TEXT:
fffff880`07bcf3f8 fffff800`0350be54 : 00000000`00000050 fffffa80`0e8db000 00000000`00000000 fffff880`07bcf560 : nt!KeBugCheckEx
fffff880`07bcf400 fffff800`034896ee : 00000000`00000000 00000000`00000372 fffff800`03498200 fffff800`03498318 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`07bcf560 fffff880`083e89f5 : fffff880`083e75bb fffffa80`07ab1000 fffff6fc`400609c0 fffffa80`0e8d5060 : nt!KiPageFault+0x16e
fffff880`07bcf6f8 fffff880`083e75bb : fffffa80`07ab1000 fffff6fc`400609c0 fffffa80`0e8d5060 fffffa80`07ab1018 : usbaudio!memmove+0xc5
fffff880`07bcf700 fffff880`0501b277 : fffffa80`07ab1110 00000000`00000000 fffffa80`00000372 fffffa80`0e8d5060 : usbaudio!USBCaptureProcessPin+0x16f
fffff880`07bcf790 fffff880`0501b764 : fffffa80`07ab1018 00000000`00000000 fffffa80`07512f00 fffffa80`0928ed00 : ks!CKsPin:rocessingObjectWork+0xe3
fffff880`07bcf7e0 fffff880`05019e27 : fffffa80`0928ecc0 fffffa80`07512f00 fffffa80`097fdad0 fffffa80`0928ecc0 : ks!CKsPin:rocess+0x70
fffff880`07bcf810 fffff880`0501abb1 : fffffa80`0928ecc0 fffffa80`07512f88 fffffa80`07512c60 fffffa80`097fdad0 : ks!CKsQueue::AddFrame+0x1e7
fffff880`07bcf850 fffff880`0503304b : 00000000`00000000 00000000`00000000 fffff880`07bcf950 fffffa80`0be35d18 : ks!CKsQueue::TransferKsIrp+0x4a1
fffff880`07bcf8e0 fffff880`0503201b : fffffa80`09d4a010 fffff880`051bd5fb fffffa80`072f4158 fffffa80`07512fb8 : ks!CKsPin:ispatchDeviceIoControl+0x20b
fffff880`07bcf940 fffff880`05019620 : fffff880`07bcfa20 fffff880`051bda0f fffffa80`07512c60 fffffa80`072f4150 : ks!KsDispatchIrp+0xdb
fffff880`07bcf970 fffff880`051bd825 : fffffa80`07512f70 fffffa80`072f4150 fffffa80`072f4150 fffffa80`07512c60 : ks!CKsDevice:assThroughIrp+0xc0
fffff880`07bcf9b0 fffff800`037a76b7 : fffffa80`09dfaf20 fffff880`07bcfca0 fffffa80`00000000 fffffa80`09dfaf20 : ksthunk!CKernelFilterDevice:ispatchIrp+0x11d
fffff880`07bcfa10 fffff800`037a7f16 : fffff880`02fd5180 00000000`00000244 00000000`00000000 00000000`01730970 : nt!IopXxxControlFile+0x607
fffff880`07bcfb40 fffff800`0348a853 : 00000000`00000000 fffff880`07bcfca0 00000000`00000000 fffff800`037ab063 : nt!NtDeviceIoControlFile+0x56
fffff880`07bcfbb0 00000000`7787fdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01def628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7787fdca


STACK_COMMAND: kb

FOLLOWUP_IP:
usbaudio!memmove+c5
fffff880`083e89f5 488b440af0 mov rax,qword ptr [rdx+rcx-10h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbaudio!memmove+c5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME: usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07

FAILURE_BUCKET_ID: X64_0x50_usbaudio!memmove+c5

BUCKET_ID: X64_0x50_usbaudio!memmove+c5

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800e8db000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880083e89f5, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: fffffa800e8db000

FAULTING_IP:
usbaudio!memmove+c5
fffff880`083e89f5 488b440af0 mov rax,qword ptr [rdx+rcx-10h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88007bcf560 -- (.trap 0xfffff88007bcf560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800c138fd0
rdx=00000200027a203a rsi=0000000000000000 rdi=0000000000000000
rip=fffff880083e89f5 rsp=fffff88007bcf6f8 rbp=fffffa800e8d5258
r8=0000000000000372 r9=0000000000000004 r10=0000000000000000
r11=fffff8800c138cd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
usbaudio!memmove+0xc5:
fffff880`083e89f5 488b440af0 mov rax,qword ptr [rdx+rcx-10h] ds:0001:fffffa80`0e8daffa=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000350be54 to fffff8000348b600

STACK_TEXT:
fffff880`07bcf3f8 fffff800`0350be54 : 00000000`00000050 fffffa80`0e8db000 00000000`00000000 fffff880`07bcf560 : nt!KeBugCheckEx
fffff880`07bcf400 fffff800`034896ee : 00000000`00000000 00000000`00000372 fffff800`03498200 fffff800`03498318 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`07bcf560 fffff880`083e89f5 : fffff880`083e75bb fffffa80`07ab1000 fffff6fc`400609c0 fffffa80`0e8d5060 : nt!KiPageFault+0x16e
fffff880`07bcf6f8 fffff880`083e75bb : fffffa80`07ab1000 fffff6fc`400609c0 fffffa80`0e8d5060 fffffa80`07ab1018 : usbaudio!memmove+0xc5
fffff880`07bcf700 fffff880`0501b277 : fffffa80`07ab1110 00000000`00000000 fffffa80`00000372 fffffa80`0e8d5060 : usbaudio!USBCaptureProcessPin+0x16f
fffff880`07bcf790 fffff880`0501b764 : fffffa80`07ab1018 00000000`00000000 fffffa80`07512f00 fffffa80`0928ed00 : ks!CKsPin:rocessingObjectWork+0xe3
fffff880`07bcf7e0 fffff880`05019e27 : fffffa80`0928ecc0 fffffa80`07512f00 fffffa80`097fdad0 fffffa80`0928ecc0 : ks!CKsPin:rocess+0x70
fffff880`07bcf810 fffff880`0501abb1 : fffffa80`0928ecc0 fffffa80`07512f88 fffffa80`07512c60 fffffa80`097fdad0 : ks!CKsQueue::AddFrame+0x1e7
fffff880`07bcf850 fffff880`0503304b : 00000000`00000000 00000000`00000000 fffff880`07bcf950 fffffa80`0be35d18 : ks!CKsQueue::TransferKsIrp+0x4a1
fffff880`07bcf8e0 fffff880`0503201b : fffffa80`09d4a010 fffff880`051bd5fb fffffa80`072f4158 fffffa80`07512fb8 : ks!CKsPin:ispatchDeviceIoControl+0x20b
fffff880`07bcf940 fffff880`05019620 : fffff880`07bcfa20 fffff880`051bda0f fffffa80`07512c60 fffffa80`072f4150 : ks!KsDispatchIrp+0xdb
fffff880`07bcf970 fffff880`051bd825 : fffffa80`07512f70 fffffa80`072f4150 fffffa80`072f4150 fffffa80`07512c60 : ks!CKsDevice:assThroughIrp+0xc0
fffff880`07bcf9b0 fffff800`037a76b7 : fffffa80`09dfaf20 fffff880`07bcfca0 fffffa80`00000000 fffffa80`09dfaf20 : ksthunk!CKernelFilterDevice:ispatchIrp+0x11d
fffff880`07bcfa10 fffff800`037a7f16 : fffff880`02fd5180 00000000`00000244 00000000`00000000 00000000`01730970 : nt!IopXxxControlFile+0x607
fffff880`07bcfb40 fffff800`0348a853 : 00000000`00000000 fffff880`07bcfca0 00000000`00000000 fffff800`037ab063 : nt!NtDeviceIoControlFile+0x56
fffff880`07bcfbb0 00000000`7787fdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01def628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7787fdca


STACK_COMMAND: kb

FOLLOWUP_IP:
usbaudio!memmove+c5
fffff880`083e89f5 488b440af0 mov rax,qword ptr [rdx+rcx-10h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: usbaudio!memmove+c5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME: usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07

FAILURE_BUCKET_ID: X64_0x50_usbaudio!memmove+c5

BUCKET_ID: X64_0x50_usbaudio!memmove+c5

Followup: MachineOwner
 
Upvote 0 Downvote
To post the actual crash dumps, please go to C:\Windows\Minidump

Copy and paste the files in there to any other folder. Then zip them. Attach to a post using the paperclip above where you type, in advanced mode reply.

I don't think it matters which bridge you remove. In the meantime also, install the latest audio driver available for your USB device. If you need a link, I'll provide it after looking at the dump(s).
 
Upvote 0 Downvote


You're the man btw, I really can't say thanks enough. If you could provide the usb audio drivers link that would be fantastic as I don't exactly know what I'm looking for.
 

Attachments

Upvote 0 Downvote
Alright. Here's what to do to get the machine under control.

1) Uninstall all Gigabyte apps which only cause problems for the masses. This means Easytune 6 and other utilities. Be glad they're removed, after.

2) This driver is too old:

Code: 
pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006
It is commonly installed with CloneDVD or similar software. What you want to do is uninstall this or related softwares to get rid of this driver. Make sure it is gone from C:\Windows\System32\drivers
- after removal.

I recommend PowerISO for drive emulation since it has perfect stability under Windows 7. The drive emulation feature remains free forever although other features require to pay, such as burning.

PowerISO - Create, Edit, Compress, Encrypt, Split, Mount, Extract ISO file, ISO/BIN converter, Virtual Drive

3) Install the newest version of GPU-Z to overwrite this driver with the newest one:

Code: 
GPU_Z    GPU-Z.sys    Mon Aug 06 10:47:00 2007
Better to uninstall GPU-Z first. Then get the latest here:

Link Removed - Invalid URL


4) Definitely install the newest video card driver:
Code: 
atikmdag atikmdag.sys Mon Aug 17 23:05:47 2009
Here's the link:

Link Removed

5) I'll need only a little further info so we can update the audio driver. Please type msinfo32 in the start menu then hit enter. File | save on the screen that opens. Then zip the saved file and attach as before.

The machine will be really good after these changes and the audio driver updated too, which I'll link you to in my next post.
 
Last edited:
Upvote 0 Downvote
Solution

Dude this is literally the best support I've ever gotten from someone online, thanks sooo much!!!
 
Upvote 0 Downvote
You're welcome.

It's important to update the USB audio driver. As I said in number 5, if you post the info as shown how to do, I can see which USB audio device you have, in order to get the driver for it updated.

I'd uninstall the bios updater too. It's only software that updates the bios which is a one time use. In the future, if a newer bios is posted on the site to install, you can deal with that then. I wouldn't bother though if there are no issues. Then again, running the latest bios is always good so that will be your call.

So ya...follow number 5 and we'll see what we can do.

Did you do the other things already? If so, any crashes since?
 
Upvote 0 Downvote

I uninstalled all the gigabyte apps and when I looked to find that pcouffin.sys file it's related to VSO software which was a torrented version of CovertXtoDVD so I uninstalled ConvertXtoDVD but the driver is still there, how would I go about getting rid of it?

Also when I go into control panel and try to find GPU-Z to uninstall it, I can't find it

I'm making my way down the list slowly but surely.
 
Upvote 0 Downvote
Go to C:\Windows\System32\drivers

Delete pcouffin.sys in there.
Delete GPU-Z.sys in there too.

Then use CCleaner to clean the registry. Reboot after.

Link Removed
 
Upvote 0 Downvote
I deleted the pcuffin.sys but I can't find the GPU-Z.sys. I actually remember that I never went through any installation prompts for GPU-Z but somehow there is an icon on my desktop. So I deleted the pcuffin.sys and ran the ccleaner and installed the new catalyst suite.
 
Upvote 0 Downvote
Awesome. Good progress!

You can install this update for your onboard audio:

Link Removed

Other than that, the USB audio is coming up as generic. Do you have something like a Logitech headset attached to USB? If so, which?
 
Upvote 0 Downvote
When I click that link for the USB audio driver you posted above it takes about 30 seconds then prompts me for username/pass.
 
Upvote 0 Downvote
Cool. That doesn't require any drivers.

The USB audio may be for your Motorola stuff.

I would complete doing everything suggested if not already. If there are any further crashes, then post the new crash dumps for them. Hopefully it won't even be necessary as we could have already fixed the problem(s).

Good luck and keep us updated in any case.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

T
  • Solved
Windows 10 Multiple BSOD on new computer build
Replies
15
Views
2K
kemical
O
  • Solved
Windows 7 BSOD on new computer.
2
Replies
25
Views
5K
kemical
O
  • Solved
Windows 7 BSOD on new computer
2 3
Replies
41
Views
6K
kemical
  • Solved
Windows 7 Blue screens over the past week on a new computer.
Replies
7
Views
2K
kemical
D
  • Solved
Windows 7 Multiple BSod with new computer
Replies
1
Views
2K
usasma