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: Random BSODs. Mostly 0x1A, but also 0x24, 0xE4, 0x19, 0x9F


18 Apr 2012   #1
vko

Windows 7 Enterprise x64
 
 
Random BSODs. Mostly 0x1A, but also 0x24, 0xE4, 0x19, 0x9F

I had 19 crashes in the past 4 month. A computer is 13 month old, the first BSODs happened on 27/12/2011. The exact statistics:

0x1A MEMORY_MANAGEMENT - happened 10 times (the 5 most recent crashes were 0x1A)
0x24 NTFS_FILE_SYSTEM - 4 times (the most recent happened 3 weeks ago)
0xE4 WORKER_INVALID - 3 times (the most recent happened a month ago)
0x19 BAD_POOL_HEADER - 1 time (2 weeks ago)
0x9F DRIVER_POWER_STATE_FAILURE - 1 time (3 month ago)

Besides BSODs, I'm also seeing event 11 in the event log, with messages like "The driver detected a controller error on \Device\Harddisk3\DR3". Harddisk3 is likely to be a WD Passport drive plugged into USB 3.0 port. The drive is used for Acronis backup. Interestingly, the event 11 started to happen on 19/12/2011 (shortly before the first BSOD).

Few notes:

1) I'm ruling out RAM issues. Few weeks ago I bought a brand new 4x4GB kit and replace the old RAM modules. The problem still continued.

2) I upgraded motherboard's BIOS, downloaded and installed all the recent drives from ASUS site, installed the latest AMD Radeon drivers. All with little help.

3) chkdsk on all drives didn't report any errors.

4) I used Kaspersky Anti-Virus 2011 before, and upgraded to Kaspersky Anti-Virus 2012 in March. This upgrade had little effect on BSODs.

5) I'm also using Acronis True Image Home 2011.

6) System configuration:

CPU: Intel i7-2600 (stock clock)
Mainboard: Asus P8P67 LE
RAM: Corsair 4x4GB kit CML16GX3M4A1600C9B at XMP speed (G.Skill F3-12800CL9D-8GBXL before that)
GPU: Fanless Gigabyte Radeon HD 5750
SSD: G.Skill Phoenix PRO 120GB as OS drive
SSD: Intel 520 120GB SSD as data drive (this was added recently - BSOD happened before this SSD was installed)
Discrete NIC: Intel Gigabit CT Desktop
Discrete COM port: MANHATTAN Serial PCI Express Card
PSU: Seasonic X-650
UPS: APC Smart-UPS 750 VA (SMT750I)
OS: Windows 7 64-bit SP1

Interestingly BSODs often happen at night, when the load is minimal. So I don't think it happens due to overheating.

Any help would be appreciated.


My System SpecsSystem Spec
.

18 Apr 2012   #2
vko

Windows 7 Enterprise x64
 
 

Three most recent dump analyses:

Code:
 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [M:\Users\Vadim\Crash Dumps\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03060650
Debug session time: Mon Apr  9 03:00:06.764 2012 (UTC + 10:00)
System Uptime: 1 days 14:19:11.196
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd7018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45a35 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocol
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88008805510 -- (.trap 0xfffff88008805510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f762f5 rsp=fffff880088056a0 rbp=fffff88008805700
 r8=fffff80002e1c000  r9=0000000000000001 r10=0000058000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiResolvePageFileFault+0x1115:
fffff800`02f762f5 8b4830          mov     ecx,dword ptr [rax+30h] ds:00000000`00000030=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002e2d0be to fffff80002e98d40
STACK_TEXT:  
fffff880`088053a8 fffff800`02e2d0be : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`088053b0 fffff800`02e96e6e : 00000000`00000000 00000000`00000030 00000000`00000000 00000000`fffff8a0 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`08805510 fffff800`02f762f5 : fffff8a0`000000a8 00000000`ffffffff fffff700`01080488 fffff700`01080000 : nt!KiPageFault+0x16e
fffff880`088056a0 fffff800`02f0a6b8 : 00000000`77536a50 fffff8a0`000000b0 fffffa80`11677478 00000000`77624500 : nt!MiResolvePageFileFault+0x1115
fffff880`088057e0 fffff800`02eb56e3 : 00000000`00003926 00000000`77536a50 fffff680`003ba9b0 fffffa80`11677478 : nt! ?? ::FNODOBFM::`string'+0x38a97
fffff880`08805870 fffff800`02ea5389 : 00000000`00000000 00000000`77536a50 fffff880`03ea5180 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`08805980 fffff800`02e96e6e : 00000000`00000008 00000000`77536a50 00000000`00000001 00000000`00000002 : nt!MmAccessFault+0x359
fffff880`08805ae0 00000000`77536a50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0099f9d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77536a50
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45a35
fffff800`02e2d0be cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45a35
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35
BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35
Followup: MachineOwner
---------

Code:
 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [M:\Users\Vadim\Crash Dumps\041712-10030-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a9650
Debug session time: Tue Apr 17 01:45:12.956 2012 (UTC + 10:00)
System Uptime: 2 days 14:52:26.643
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 0, 0}
Unable to load image klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+559e0 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41287
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff8800af8ee40 -- (.trap 0xfffff8800af8ee40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a01c816000
rdx=00000f5ed1422000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004f0b9e0 rsp=fffff8800af8efd8 rbp=fffff8800af8f120
 r8=0000000000001000  r9=0000000000000080 r10=0000000000000001
r11=fffff8a01c815000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
klif+0x559e0:
fffff880`04f0b9e0 ??              ???
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002e760be to fffff80002ee1c80
STACK_TEXT:  
fffff880`0af8e708 fffff800`02e760be : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`0af8e710 fffff800`02edfdae : 00000000`00000000 00000000`00000030 fffff8a0`1728a000 00000000`fffff8a0 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`0af8e870 fffff800`02fbf1e5 : fffff8a0`00000030 00000000`ffffffff fffff8a0`1728a038 fffff8a0`1728a048 : nt!KiPageFault+0x16e
fffff880`0af8ea00 fffff800`02f535b8 : 000007fe`edc37ff8 fffff8a0`00000038 fffffa80`107e8ec8 00000000`00000000 : nt!MiResolvePageFileFault+0x1115
fffff880`0af8eb40 fffff800`02efe5c3 : 00000000`00003865 000007fe`edc37ff8 fffff683`ff76e1b8 fffffa80`107e8ec8 : nt! ?? ::FNODOBFM::`string'+0x38a97
fffff880`0af8ebd0 fffff800`02eee269 : 00000000`00000000 000007fe`edc37ff8 00000000`00000000 fffff880`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0af8ece0 fffff800`02edfdae : 00000000`00000000 000007fe`edc37ff8 00000000`72624c00 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`0af8ee40 fffff880`04f0b9e0 : fffff880`04ef2d3e fffff880`0af8f120 fffff880`0af8f120 fffff880`00000098 : nt!KiPageFault+0x16e
fffff880`0af8efd8 fffff880`04ef2d3e : fffff880`0af8f120 fffff880`0af8f120 fffff880`00000098 00000000`00000000 : klif+0x559e0
fffff880`0af8efe0 fffff880`0af8f120 : fffff880`0af8f120 fffff880`00000098 00000000`00000000 00000000`00001000 : klif+0x3cd3e
fffff880`0af8efe8 fffff880`0af8f120 : fffff880`00000098 00000000`00000000 00000000`00001000 000007fe`edc37000 : 0xfffff880`0af8f120
fffff880`0af8eff0 fffff880`00000098 : 00000000`00000000 00000000`00001000 000007fe`edc37000 00000000`00000000 : 0xfffff880`0af8f120
fffff880`0af8eff8 00000000`00000000 : 00000000`00001000 000007fe`edc37000 00000000`00000000 fffff880`0af8f100 : 0xfffff880`00000098
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
klif+559e0
fffff880`04f0b9e0 ??              ???
SYMBOL_STACK_INDEX:  8
SYMBOL_NAME:  klif+559e0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: klif
IMAGE_NAME:  klif.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb6b7
FAILURE_BUCKET_ID:  X64_0x1a_41287_klif+559e0
BUCKET_ID:  X64_0x1a_41287_klif+559e0
Followup: MachineOwner
---------

Code:
 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [M:\Users\Vadim\Crash Dumps\041812-9469-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`0321f000 PsLoadedModuleList = 0xfffff800`03463650
Debug session time: Wed Apr 18 17:45:25.149 2012 (UTC + 10:00)
System Uptime: 0 days 23:20:37.946
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 30, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45a35 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41287
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff88009668510 -- (.trap 0xfffff88009668510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033791e5 rsp=fffff880096686a0 rbp=fffff88009668700
 r8=fffff8000321f000  r9=0000000000000001 r10=0000058000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiResolvePageFileFault+0x1115:
fffff800`033791e5 8b4830          mov     ecx,dword ptr [rax+30h] ds:00000000`00000030=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800032300be to fffff8000329bc80
STACK_TEXT:  
fffff880`096683a8 fffff800`032300be : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`096683b0 fffff800`03299dae : 00000000`00000000 00000000`00000030 00000000`c0000000 00000000`fffff8a0 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`09668510 fffff800`033791e5 : fffff8a0`00000090 00000000`ffffffff 00000000`00000008 fffffa80`142158d0 : nt!KiPageFault+0x16e
fffff880`096686a0 fffff800`0330d5b8 : 00000000`08b4200e fffff8a0`00000090 fffffa80`13fb7ec8 fffff800`035bed00 : nt!MiResolvePageFileFault+0x1115
fffff880`096687e0 fffff800`032b85c3 : 00000000`00003c65 00000000`08b4200e fffff680`00045a10 fffffa80`13fb7ec8 : nt! ?? ::FNODOBFM::`string'+0x38a97
fffff880`09668870 fffff800`032a8269 : 00000000`00000000 00000000`08b4200e 00000000`0046ca90 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`09668980 fffff800`03299dae : 00000000`00000000 00000000`08b4200e 00000000`00000001 00000000`00bdcd60 : nt!MmAccessFault+0x359
fffff880`09668ae0 00000000`65a557e2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0463cac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x65a557e2
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45a35
fffff800`032300be cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45a35
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35
BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a35
Followup: MachineOwner
---------
My System SpecsSystem Spec
18 Apr 2012   #3

Win 8 Release candidate 8400
 
 

Feels like software. You have a couple of really old drivers that need updating, and sorry to say but Kaspersky has known issues on some systems.


I would update the drivers, remover Kaspersky (JUST TO TEST) and run driver verifier to find the mis-behaving driver. If you have another other DMP plese upload them so we can look for trends



Old drivers

Code:
BrUsbSIb.sys    1/22/2008 1:01:51 AM       
BrSerIb.sys    1/22/2008 1:01:55 AM        
wdcsam64.sys    4/16/2008 4:39:08 AM                
000.fcl    9/26/2008 9:11:22 AM       
adfs.SYS    11/3/2008 12:48:14 PM        
PciSPorts.sys    12/19/2008 12:55:33 AM       
GEARAspiWDM.sys    5/18/2009 8:17:04 AM
Kaspersky is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloa...vremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.






Driver Verifer

Quote:
Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JGriff2 & Usasma.
Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
.


Reply

 Random BSODs. Mostly 0x1A, but also 0x24, 0xE4, 0x19, 0x9F




Thread Tools



Similar help and support threads for2: Random BSODs. Mostly 0x1A, but also 0x24, 0xE4, 0x19, 0x9F
Thread Forum
BSOD's still rampant 0x1a 0x107e 0x24 BSOD Help and Support
Getting random BSODs @ 0x1A, 0x50 BSOD Help and Support
0x0a & 0x1a BSODs. Frequent and Frustrating to Fix BSOD Help and Support
BSOD Playing Dota2,Borderlands and other "source" games (0x1a,0x24...) BSOD Help and Support
Multiple BSODs per month (0x3B, 0X50, 0X24) BSOD Help and Support
BSOD on newly built PC (0x24, 0x7E, 0x1A) 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 11:05 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