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's out of the blue...


23 Jun 2010   #1

Windows 7 X64
 
 
BSOD's out of the blue...

Never had any BSOD since installing my system, but just had two on one day.
Could anyone give me an insight as to the culprit of this? Nothing significant was changed. To me it appeared to start out of nowhere

My System SpecsSystem Spec
.

23 Jun 2010   #2

Windows 7 Ultimate 32 bit
 
 

Sorry you are having problems, we will take a look.

Quote:
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
BSOD Index

STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION

Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
BSOD Index
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Seven Forums.zip\Seven Forums\062310-39671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Wed Jun 23 08:48:00.387 2010 (GMT-4)
System Uptime: 0 days 6:26:26.495

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c2b52000, 0, fffff96000075d83, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!DrvTextOut+4cc )

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

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: fffff900c2b52000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000075d83, 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 fffff800030c40e0
 fffff900c2b52000 

FAULTING_IP: 
win32k!draw_clrt_nf_ntb_o_to_temp_start+7b
fffff960`00075d83 41803b00        cmp     byte ptr [r11],0

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002af8050 -- (.trap 0xfffff88002af8050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff9600031ba60
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000075d83 rsp=fffff88002af81e8 rbp=000000007fffe95e
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000039
r11=fffff900c2b52000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k!draw_clrt_nf_ntb_o_to_temp_start+0x7b:
fffff960`00075d83 41803b00        cmp     byte ptr [r11],0 ds:3120:fffff900`c2b52000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f0ce54 to fffff80002e8c600

STACK_TEXT:  
fffff880`02af7ee8 fffff800`02f0ce54 : 00000000`00000050 fffff900`c2b52000 00000000`00000000 fffff880`02af8050 : nt!KeBugCheckEx
fffff880`02af7ef0 fffff800`02e8a6ee : 00000000`00000000 fffff900`c2c610a4 fffff900`c21cbc00 fffff800`02ed79dc : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`02af8050 fffff960`00075d83 : fffff900`c00cf650 00000000`000000ac 00000000`0000002c 00000000`00000025 : nt!KiPageFault+0x16e
fffff880`02af81e8 fffff960`000aa988 : fffff900`c00bf010 fffff880`02af9400 fffff900`c2b50740 00000000`0000002c : win32k!draw_clrt_nf_ntb_o_to_temp_start+0x7b
fffff880`02af8220 fffff960`00084da8 : 00000000`00000000 fffff900`c2b50740 fffff900`c2c61030 fffff900`0000002c : win32k!vExpandAndCopyText+0x268
fffff880`02af85b0 fffff960`0064b4e0 : fffff900`00000025 00000000`000000aa fffff900`c21f7ca0 fffff880`02af9340 : win32k!EngTextOut+0xe28
fffff880`02af8940 fffff960`00099e67 : fffff900`c43c7ce8 fffff880`02af9400 fffff900`c21f7ca0 fffff880`02af9340 : cdd!DrvTextOut+0x4cc
fffff880`02af8d50 fffff960`00083f0b : 00000000`00000000 00000000`00000001 fffff960`0064b014 00000000`00000001 : win32k!OffTextOut+0xdf
fffff880`02af8dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SpTextOut+0x2bb


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cdd!DrvTextOut+4cc
fffff960`0064b4e0 488b8c24e0000000 mov     rcx,qword ptr [rsp+0E0h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  cdd!DrvTextOut+4cc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94

FAILURE_BUCKET_ID:  X64_0x50_cdd!DrvTextOut+4cc

BUCKET_ID:  X64_0x50_cdd!DrvTextOut+4cc

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

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Seven Forums.zip\Seven Forums\062310-49967-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03041e50
Debug session time: Wed Jun 23 16:25:19.045 2010 (GMT-4)
System Uptime: 0 days 7:36:04.154
Loading Kernel Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89f8789b9, b3b7465ef2045baf, fffff80002e4cea4, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See Patching Policy for x64-Based Systems: Information for Driver Developers
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89f8789b9, Reserved
Arg2: b3b7465ef2045baf, Reserved
Arg3: fffff80002e4cea4, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e74600

STACK_TEXT:  
fffff880`035625d8 00000000`00000000 : 00000000`00000109 a3a039d8`9f8789b9 b3b7465e`f2045baf fffff800`02e4cea4 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner
This appears to be a hardware/driver issue. I would like to address the easy things first.

You have a very old driver on your system. Old drivers do not play well with Windows 7. Upgrade the driver and software or uninstall it.

pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2) This driver is Patin-Couffin low level access layer for CD devices or low level access layer for CD/DVD/BD devices or VSO Software pcouffin belongs to the software Low level access layer for CD devices or Patin couffin engine or VSO Software pcouffin by VSO Software (www.vso-software.fr).

I also see that you have AVG installed. AVG is known to cause BSOD's on some systems. I suggest that uninstall AVG for the purpose of troubleshooting. I suggest you install MSE in its place. Use the AVG uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Indentity Protection installed uninstall it also >Info > Tool

After you have done these, run your system and let's see what happens.
My System SpecsSystem Spec
24 Jun 2010   #3

Windows 7 X64
 
 

I uninstalled both AVG and DVDFab (the source of the old pcouffin driver). I installed MSE and will see how it goes the next couple of days. Thanks so far
My System SpecsSystem Spec
.


24 Jun 2010   #4

Windows 7 Ultimate 32 bit
 
 

Very good. If we are lucky, your problem is solved. Be sure to post back and let us know how your system is running. Post back if you get another BSOD. Fingers crossed!
My System SpecsSystem Spec
07 Aug 2010   #5

Windows 7 X64
 
 

The system is mostly stable, but I had two more blue screens. One on july 29th and one on august 6th. Something seems to be unstable, but I cannot lay my finger on it. Memory? CPU? Mainboard?

Here's another zipfile with information

My system is Windows 7 X64
Original installation (about 6 months old)
I didn't change any of the default timings in the BIOS.
My System SpecsSystem Spec
07 Aug 2010   #6

Windows 7 Ultimate 32 bit
 
 

I will take a look and be right back. I am sorry you are still having problems.

Quote:
STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory


STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION

Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
The latest dump doesn't tell us very much. The analysis is incomplete
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Murdock_BSOD.zip\Windows7_BSOD_jcgriff2\072910-53367-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50
Debug session time: Thu Jul 29 13:34:50.147 2010 (GMT-4)
System Uptime: 0 days 2:31:22.255
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 280870, 2, 28086c}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000280870, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000028086c, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f0e2bc to fffff80002e7e600

STACK_TEXT:  
fffff880`0354d7e8 fffff800`02f0e2bc : 00000000`0000004e 00000000`00000099 00000000`00280870 00000000`00000002 : nt!KeBugCheckEx
fffff880`0354d7f0 fffff800`02edcf12 : 00000000`00000002 00000000`00000000 fffffa80`00e01a20 00000000`00000080 : nt!MiBadShareCount+0x4c
fffff880`0354d830 fffff800`02f3f1dd : fffffa80`00e01a20 fffff880`0354d980 00000000`00000080 00000000`002946f9 : nt! ?? ::FNODOBFM::`string'+0x11aa2
fffff880`0354d890 fffff800`02e239d5 : fa800a06`b63004c0 fffff880`0354d980 00000000`000001e0 00000000`00000000 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`0354d910 fffff800`0311f89a : fffffa80`0e3f0160 fffffa80`00000001 fffffa80`0e3f0160 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x2d928
fffff880`0354da80 fffff800`02e30a57 : fffffa80`0e3f0160 00000001`66fa8000 00000001`66fa8000 fffff800`030235a0 : nt!MmPrefetchForCacheManager+0x96
fffff880`0354dad0 fffff800`02e72472 : fffffa80`0b97ef20 fffffa80`09d7d000 00000000`00000000 fffff800`03085138 : nt!CcPerformReadAhead+0x2f3
fffff880`0354dc00 fffff800`02e8b861 : fffffa80`09d8a930 fffff800`02e72254 fffff800`03085150 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`0354dcb0 fffff800`03123a86 : e985e985`f481f481 fffffa80`09d7d040 00000000`00000080 fffffa80`09d5f040 : nt!ExpWorkerThread+0x111
fffff880`0354dd40 fffff800`02e5cb06 : fffff880`0336a180 fffffa80`09d7d040 fffff880`033750c0 143d143d`609d609d : nt!PspSystemThreadStartup+0x5a
fffff880`0354dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f0e2bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Murdock_BSOD.zip\Windows7_BSOD_jcgriff2\080610-41402-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e0b000 PsLoadedModuleList = 0xfffff800`03048e50
Debug session time: Fri Aug  6 16:22:53.602 2010 (GMT-4)
System Uptime: 0 days 13:20:05.710
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89fc897dd, 0, 565cd38053d8aeb2, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See Patching Policy for x64-Based Systems: Information for Driver Developers
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89fc897dd, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 565cd38053d8aeb2, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e7b600

STACK_TEXT:  
fffff880`035855d8 00000000`00000000 : 00000000`00000109 a3a039d8`9fc897dd 00000000`00000000 565cd380`53d8aeb2 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner
---------
Since both dumps point to memory, lets start with testing your RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 7 passes. Errors will show in red. Post back with the results.

See if you can update this driver. It is a later version of the driver that is notorious for BSOD's; I do not know if there is a later version yet.

ASACPI.sys Wed May 13 21:25:17 2009 -
ASACPI.sys should be updated. Please install the latest ATK0110 Utility for Vista/7 from this link: ASUSTeK Computer Inc.-Support-


Here are some more outdated drivers on your system. Win 7 does not like outdated drivers and they can definitely cause memory corruption.

AsUpIO.sys Sun Jul 05 22:21:38 2009 - Asus Support --> http://support.asus.com/download/dow...Language=en-us. Update this driver.

PxHlpa64.sys Wed Mar 12 21:58:17 2008 - This is an obsolete driver. Sonic CD/DVD driver (used by many different CD/DVD programs). I suggest you go to C:\Windows\System32\drivers and rename PxHlpa64.sys to PxHlpa64.BAK. This will break your CD/DVD program, but can easily be renamed after you have finished troubleshooting. Reboot after you rename the driver. You could uninstall the software since it is obsolete and replace it with something compatible with Win 7. Here is a list of the programs associated with this driver: pxHelp20.sys programs

RTKVHD64.sys Fri May 22 14:04:20 2009 - Realtek High Definition Audio Function Driver Realtek. Update this driver.

After you update/disable these drivers. Reboot, run your system and report back.



My System SpecsSystem Spec
07 Aug 2010   #7

Windows 7 X64
 
 

I started a test earlier today with MEMTEST86 and after running for 3+ hours I stopped the tests. It showed 1 error in red on test #7. While searching for some information on this error I was pointed to Super PI Mod. If my system was unstable this program could be of aid. I actually ran the 32M test and after a while it said 'not convergent in sqr5'.

My system is stable 9 out of 10 times I use it, but this one time it isn't bugs me.

Is any of the above info helpful?
My System SpecsSystem Spec
07 Aug 2010   #8

Windows 7 Professional x64
 
 

In addition to Carl's advice, please enable driver verifier: Driver Verifier - Enable and Disable

EDIT: Sorry, I missed your reply. Try testing your sticks individually, to see if you can isolate whether it is a bad stick, bad motherboard slot, or compatibility issue between the sticks.
My System SpecsSystem Spec
07 Aug 2010   #9

Windows 7 X64
 
 

How long should MEMTEST86+ run to have a good test of a stick?
Single stick testing means always booting with MEMTEST86+ and every time only one module in slot 1?
My System SpecsSystem Spec
07 Aug 2010   #10

Windows 7 Ultimate 32 bit
 
 

It should run for 5-7 passes. I would let it run at least 6. I edited my post above and added more info. Please refresh your page and take a look. You need to take care of those obsolete drivers and enable driver verifier as Jonathan suggestive. Be sure to read the thread Jonathan gave you the link for. I would recommend you print his first post in that thread.

Quote:
Single stick testing means always booting with MEMTEST86+ and every time only one module in slot 1?
Yes, you are correct.
My System SpecsSystem Spec
Reply

 BSOD's out of the blue...




Thread Tools



Similar help and support threads for2: BSOD's out of the blue...
Thread Forum
two BSOD's out of the blue, one of which 0000003B BSOD Help and Support
BSOD Out of the blue BSOD Help and Support
BSOD without the Blue Screen BSOD Help and Support
Out of the blue BSOD 0xF4 BSOD Help and Support
Blue Screen BSOD BSOD Help and Support
BSOD / Blue screen while using ICS BSOD Help and Support
BSOD Out of the Blue 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 10:03 PM.
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