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 - What seems to me to be randomly

22 Apr 2010   #11
Jonathan_King

Windows 7 Professional x64
 
 

Reboot, and the new drivers should be installed automatically.


My System SpecsSystem Spec
.
22 Apr 2010   #12
SimonWithTheHat

Windows 7 64-bit
 
 

hmm well anyways i just disabled PhysX and now i have been without bluescreens for quite some time, except for one caused by my USB, which i haven't installed yet so thát i can understand. and to point it out it's my USB 3.0 i haven't installed

I hope people who have nvidia finds turning PhysX off helps. It helped for me!
My System SpecsSystem Spec
22 Apr 2010   #13
Jonathan_King

Windows 7 Professional x64
 
 

What do you mean, you haven't installed USB 3? If it is using the generic drivers, try downloading some, and see if it helps any.
My System SpecsSystem Spec
.

23 Apr 2010   #14
SimonWithTheHat

Windows 7 64-bit
 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
What do you mean, you haven't installed USB 3? If it is using the generic drivers, try downloading some, and see if it helps any.
I forgot I had USB 3.0 on this motherboard and the latest BS was caused my usbport.sys something, so I bet that is the one. But it's the first one caused by my USB. And it's the only one I have gotten since I turned PhysX off in the nvidia control panel.
My System SpecsSystem Spec
23 Apr 2010   #15
SimonWithTheHat

Windows 7 64-bit
 
 

well it seems my luck will never return, i got 2 screens just after each other now and this is the dumps.

it was not the USB and I don't know what to do anymore. I am out of ideas and it's so frustrating to not be able to use the computer i spent so much money on and realize i could do just as good without it.

Nr. 1

Code:
Problemsignatur:
  Problemhändelsens namn: BlueScreen
  OS-version: 6.1.7600.2.0.0.768.3
  Språkvariant-ID: 1053
Ytterligare information om problemet:
  BCCode: 7f
  BCP1: 0000000000000008
  BCP2: 0000000080050033
  BCP3: 00000000000006F8
  BCP4: FFFFF880040026D4
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1
Filer som hjälper till att beskriva problemet:
  C:\Windows\Minidump\042310-12729-01.dmp
  C:\Users\Simon\AppData\Local\Temp\WER-23150-0.sysdata.xml
Läs vår sekretesspolicy online:
  Windows 7 Privacy Statement - Microsoft Windows
Om sekretesspolicyn online inte är tillgänglig kan du läsa vår sekretesspolicy offline:
  C:\Windows\system32\sv-SE\erofflps.txt
Nr. 2

Code:
Problemsignatur:
  Problemhändelsens namn: BlueScreen
  OS-version: 6.1.7600.2.0.0.768.3
  Språkvariant-ID: 1053
Ytterligare information om problemet:
  BCCode: c4
  BCP1: 0000000000000091
  BCP2: 0000000000000000
  BCP3: FFFFF880009F40C0
  BCP4: 0000000000000000
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1
Filer som hjälper till att beskriva problemet:
  C:\Windows\Minidump\042310-15802-01.dmp
  C:\Users\Simon\AppData\Local\Temp\WER-24024-0.sysdata.xml
Läs vår sekretesspolicy online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x041d
My System SpecsSystem Spec
23 Apr 2010   #16
SimonWithTheHat

Windows 7 64-bit
 
 

bumping, still not working and i'm getting sick and tired of my computer

have gotten several bluescreens since last post
My System SpecsSystem Spec
23 Apr 2010   #17
SimonWithTheHat

Windows 7 64-bit
 
 

i ran a driver verifier. it crashed before i could login to windows so i ran a repair. i got this dump from it
My System SpecsSystem Spec
23 Apr 2010   #18
Jonathan_King

Windows 7 Professional x64
 
 

Still looks like graphics card. Download and install these drivers: NVIDIA DRIVERS 197.45 WHQL

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_latest after driver verifier.zip\042310-13275-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Fri Apr 23 12:04:07.783 2010 (GMT-4)
System Uptime: 0 days 0:00:09.954
Loading Kernel Symbols
...............................................................
................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002c90183}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+892a0 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c90183, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea80e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02c90183 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

IRP_ADDRESS:  ffffffffffffff89

TRAP_FRAME:  fffff88003361580 -- (.trap 0xfffff88003361580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003361f80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c90183 rsp=fffff88003361710 rbp=fffff88003361860
 r8=fffff88003361818  r9=fffff88003361810 r10=0000000000000002
r11=fffff80002c8f6a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!IopCompleteRequest+0xae3:
fffff800`02c90183 488b09          mov     rcx,qword ptr [rcx] ds:1825:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c6fb69 to fffff80002c70600

STACK_TEXT:  
fffff880`03361438 fffff800`02c6fb69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03361440 fffff800`02c6e7e0 : 00000000`00134610 fffff980`02930ee0 00000000`00000000 fffffa80`05497148 : nt!KiBugCheckDispatch+0x69
fffff880`03361580 fffff800`02c90183 : 0000036c`0000036d fffff800`0000036c fffff880`03cfe910 fffff880`03cfe910 : nt!KiPageFault+0x260
fffff880`03361710 fffff800`02c4cfcf : 00000000`00000001 fffff800`02c10a00 00000000`00057300 fffff880`00000000 : nt!IopCompleteRequest+0xae3
fffff880`033617e0 fffff800`02c4d387 : 00000000`0008a13e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03361860 fffff800`02c48e01 : fffff880`0fea713e fffff880`03361ba0 fffffa80`05c63198 fffff880`03361b80 : nt!KiApcInterrupt+0xd7
fffff880`033619f0 fffff800`02c10aee : 00000000`0005733c 00000000`00000000 fffff880`03361b80 00000000`0008a13e : nt!RtlpLookupFunctionEntryForStackWalks+0xa1
fffff880`03361a60 fffff800`02c1093f : fffffa80`05c63198 fffff880`00000011 fffff980`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x18e
fffff880`03362100 fffff800`02d33b6b : 00000000`00000003 fffffa80`05c63198 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x73
fffff880`03362130 fffff800`0310702c : fffffa80`05c63180 00000000`00000160 00000000`00000080 fffff800`030fadcc : nt!RtlCaptureStackBackTrace+0x4b
fffff880`03362160 fffff800`0310933a : fffff880`0335d000 fffff880`03363000 00000000`00000080 00000000`00000160 : nt!ViPoolLogStackCallout+0x1c
fffff880`03362190 fffff800`0310c026 : 00000000`00000000 00000000`00000028 fffff800`02edde5f fffff880`00f29a11 : nt!ViPoolLogStackTrace+0x8a
fffff880`033621c0 fffff800`0310c160 : fffffa80`07911bf0 fffff800`02edde5f 00000000`2b707249 fffffa80`056da018 : nt!VeAllocatePoolWithTagPriority+0x2b6
fffff880`03362230 fffff800`031153a8 : 00000000`00000001 fffff800`0310702c fffffa80`056da000 fffff800`02edde5f : nt!ViIrpAllocate+0x40
fffff880`03362270 fffff800`031154c3 : fffffa80`07911bf0 fffff800`02edde5f fffffa80`056da018 fffffa80`0713fa20 : nt!ViIrpAllocateLockedPacket+0x28
fffff880`033622b0 fffff800`03115a92 : fffffa80`07911bf0 fffffa80`056da018 00000000`00000000 fffff800`03124640 : nt!VfIoAllocateIrp1+0x23
fffff880`033622e0 fffff800`02c658d6 : fffffa80`07911bf0 fffff880`03cf38b0 00000000`00000058 34d81458`00000000 : nt!IovAllocateIrp+0x52
fffff880`03362330 fffff800`02edde5f : fffffa80`07911bf0 00000000`00807805 00000000`00000058 fffffa80`0795c5d0 : nt!IoBuildAsynchronousFsdRequest+0x36
fffff880`03362380 fffff880`03d652a0 : 00000000`00000000 00000000`00000001 01140009`00000000 00000000`00000000 : nt!IoBuildSynchronousFsdRequest+0x1f
fffff880`033623c0 00000000`00000000 : 00000000`00000001 01140009`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x892a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl+892a0
fffff880`03d652a0 ??              ???

SYMBOL_STACK_INDEX:  13

SYMBOL_NAME:  dxgkrnl+892a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac5509e

FAILURE_BUCKET_ID:  X64_0xA_VRF_dxgkrnl+892a0

BUCKET_ID:  X64_0xA_VRF_dxgkrnl+892a0

Followup: MachineOwner
---------
My System SpecsSystem Spec
23 Apr 2010   #19
SimonWithTheHat

Windows 7 64-bit
 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
Still looks like graphics card. Download and install these drivers: NVIDIA DRIVERS 197.45 WHQL

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_latest after driver verifier.zip\042310-13275-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Fri Apr 23 12:04:07.783 2010 (GMT-4)
System Uptime: 0 days 0:00:09.954
Loading Kernel Symbols
...............................................................
................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck A, {0, 2, 0, fffff80002c90183}
 
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl+892a0 )
 
Followup: MachineOwner
---------
 
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c90183, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ea80e0
 0000000000000000 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
nt!IopCompleteRequest+ae3
fffff800`02c90183 488b09          mov     rcx,qword ptr [rcx]
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
IRP_ADDRESS:  ffffffffffffff89
 
TRAP_FRAME:  fffff88003361580 -- (.trap 0xfffff88003361580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003361f80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c90183 rsp=fffff88003361710 rbp=fffff88003361860
 r8=fffff88003361818  r9=fffff88003361810 r10=0000000000000002
r11=fffff80002c8f6a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!IopCompleteRequest+0xae3:
fffff800`02c90183 488b09          mov     rcx,qword ptr [rcx] ds:1825:00000000`00000000=????????????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80002c6fb69 to fffff80002c70600
 
STACK_TEXT:  
fffff880`03361438 fffff800`02c6fb69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03361440 fffff800`02c6e7e0 : 00000000`00134610 fffff980`02930ee0 00000000`00000000 fffffa80`05497148 : nt!KiBugCheckDispatch+0x69
fffff880`03361580 fffff800`02c90183 : 0000036c`0000036d fffff800`0000036c fffff880`03cfe910 fffff880`03cfe910 : nt!KiPageFault+0x260
fffff880`03361710 fffff800`02c4cfcf : 00000000`00000001 fffff800`02c10a00 00000000`00057300 fffff880`00000000 : nt!IopCompleteRequest+0xae3
fffff880`033617e0 fffff800`02c4d387 : 00000000`0008a13e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03361860 fffff800`02c48e01 : fffff880`0fea713e fffff880`03361ba0 fffffa80`05c63198 fffff880`03361b80 : nt!KiApcInterrupt+0xd7
fffff880`033619f0 fffff800`02c10aee : 00000000`0005733c 00000000`00000000 fffff880`03361b80 00000000`0008a13e : nt!RtlpLookupFunctionEntryForStackWalks+0xa1
fffff880`03361a60 fffff800`02c1093f : fffffa80`05c63198 fffff880`00000011 fffff980`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x18e
fffff880`03362100 fffff800`02d33b6b : 00000000`00000003 fffffa80`05c63198 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x73
fffff880`03362130 fffff800`0310702c : fffffa80`05c63180 00000000`00000160 00000000`00000080 fffff800`030fadcc : nt!RtlCaptureStackBackTrace+0x4b
fffff880`03362160 fffff800`0310933a : fffff880`0335d000 fffff880`03363000 00000000`00000080 00000000`00000160 : nt!ViPoolLogStackCallout+0x1c
fffff880`03362190 fffff800`0310c026 : 00000000`00000000 00000000`00000028 fffff800`02edde5f fffff880`00f29a11 : nt!ViPoolLogStackTrace+0x8a
fffff880`033621c0 fffff800`0310c160 : fffffa80`07911bf0 fffff800`02edde5f 00000000`2b707249 fffffa80`056da018 : nt!VeAllocatePoolWithTagPriority+0x2b6
fffff880`03362230 fffff800`031153a8 : 00000000`00000001 fffff800`0310702c fffffa80`056da000 fffff800`02edde5f : nt!ViIrpAllocate+0x40
fffff880`03362270 fffff800`031154c3 : fffffa80`07911bf0 fffff800`02edde5f fffffa80`056da018 fffffa80`0713fa20 : nt!ViIrpAllocateLockedPacket+0x28
fffff880`033622b0 fffff800`03115a92 : fffffa80`07911bf0 fffffa80`056da018 00000000`00000000 fffff800`03124640 : nt!VfIoAllocateIrp1+0x23
fffff880`033622e0 fffff800`02c658d6 : fffffa80`07911bf0 fffff880`03cf38b0 00000000`00000058 34d81458`00000000 : nt!IovAllocateIrp+0x52
fffff880`03362330 fffff800`02edde5f : fffffa80`07911bf0 00000000`00807805 00000000`00000058 fffffa80`0795c5d0 : nt!IoBuildAsynchronousFsdRequest+0x36
fffff880`03362380 fffff880`03d652a0 : 00000000`00000000 00000000`00000001 01140009`00000000 00000000`00000000 : nt!IoBuildSynchronousFsdRequest+0x1f
fffff880`033623c0 00000000`00000000 : 00000000`00000001 01140009`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x892a0
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
dxgkrnl+892a0
fffff880`03d652a0 ??              ???
 
SYMBOL_STACK_INDEX:  13
 
SYMBOL_NAME:  dxgkrnl+892a0
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: dxgkrnl
 
IMAGE_NAME:  dxgkrnl.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4ac5509e
 
FAILURE_BUCKET_ID:  X64_0xA_VRF_dxgkrnl+892a0
 
BUCKET_ID:  X64_0xA_VRF_dxgkrnl+892a0
 
Followup: MachineOwner
---------

Well if that is the latest ones, that were the ones I had. And it did not work. So I erased it and installed Windows 7 32 bit now. I am prepared to put my life on that this is going to work without any problems.

And I noticed that my USB 3.0 drivers did not want to cooperate with Windows 7 64-bit, it still ended up unrecognized while browsing the hardware.

As this is not my real Windows license I will only be able to use it for 3 days so I still need help. I have tried the GPU drivers several times. Still does not work. I have uninstalled them manually, it prompts me to reboot. I do, windows installs a new one (which is not the latest) so that I have to install on top of that.
My System SpecsSystem Spec
23 Apr 2010   #20
usasma
Microsoft MVP

 
 

What directions did you follow when using Driver Verifier? If you used Cap'n Jack's instructions - then I'd have to suspect that you have a hardware problem (because of the number of different BSOD errors - and the presence of Windows drivers in a Verifier enabled memory dump that should have been checking for 3rd party drivers).

Additionally, the STOP 0xC4 error from post 15 was also a Verifier Enabled memory dump - and it blames ntkrnlmp.exe (the kernel (core) of the Windows OS). Again, if you specified having Driver Verifier check for 3rd party (non-Microsoft) drivers - then this is also indicative of a hardware issue (can also be an incompatibility).

Please do more research and give us more information on the specifications of your system.
My System SpecsSystem Spec
Reply

 BSOD - What seems to me to be randomly




Thread Tools




Similar help and support threads
Thread Forum
BSOD-PC Freezes randomly-Driver Verifier BSOD's at User Log-On
Hello, As the thread shows im having lots and lots of little(and big) crashes. Im attaching the SF log and any help will be appreciated Many thanks, Dimitris
BSOD Help and Support
BSOD whilst playing Games, also sometimes just randomly BSOD
Not sure what is going wrong with my comp, i recently over clocked it and set it to 4.0GHz if that helps?
BSOD Help and Support
BSOD randomly (no specific trigger) Commonly an IRQL issue on BSOD
Hi, My computer has been unstable for quite some time and after memory tests, changing graphics cards, many driver variations and a couple of fresh OS installs a while ago it is still not stable. The difficulty is that it doesn't seem to be triggered by anything specific so it makes debugging...
BSOD Help and Support
BSOD randomly and PC freezes randomly
Hi guys, my pc has been acting weird lately, it has began randomly crashing frequently. I turn it on and after 3 or so minutes of random activity it just freezes or gives me a blue screen error. Sometimes while playing BF3, it freezes. Problem signature: Problem Event Name: BlueScreen ...
BSOD Help and Support
BSOD semi-randomly. Self built computer. (BSOD dump.zip included)
64 bit, full retail. Hardware is 1 month old (built myself) OS was installed when I built it from a USB drive (did not include an optical drive in the build) SPECS: i5 2500k ATI 7850 GPU corsair tx650 PSU ASRock Extreme3 Gen3 motherboard Corsair vengance 1600 ddr3 ram (2x4gb)...
BSOD Help and Support
BSOD randomly (?) When waking laptop after sleeping, BSOD pic attached
Is Windows 7 . . . - x64 - the original installed OS on the system? Windows 7 Ultimate x64 - an OEM or full retail version? Retail - What is the age of system (hardware)? ~1 year - What is the age of OS installation (have you re-installed the OS?) ~1 year, I installed it when I got the...
BSOD Help and Support


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 03:26.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App