Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

Random BSoD, BSoD while playing, BSoD on boot

This is a discussion on Random BSoD, BSoD while playing, BSoD on boot within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. PSU: Corsair 750W CMPSU-750TXEU Case: THERMALTAKE ElementS CPU: AMD Phenom II X4 965 BE HDD: SAMSUNG HD502HJ SpinPoint F3 3,5"


Closed Thread
 
Thread Tools Search this Thread
Old 09-29-2011, 11:24 AM   #1
Registered Member
 
Join Date: Sep 2011
Posts: 2
OS: Windows 7 64 bit



PSU: Corsair 750W CMPSU-750TXEU
Case: THERMALTAKE ElementS
CPU: AMD Phenom II X4 965 BE
HDD: SAMSUNG HD502HJ SpinPoint F3 3,5" 500GB
GPU: ZOTAC Geforce GTX480 1536MB DDR5
Lettore: LG Super Multi CH10LS20
RAM: CORSAIR Dominator 2x2 GB DDR3 (CMP4GX3M2A1600C8)
Mobo: Asus M4A88T-M/USB3
OS: Windows 7 Ultimate 64bit

I've got this system running since november 2010 and i have had not a single problem. About a month ago, i had issues trying to boot windows: i had to turn power on/off loads of time until i was able to get to desktop. Since that day, Blue Screens happened every time i got to desktop, after few seconds or after few minutes... Freezes and BSoD kept coming, so i ran some tests: memtest86, scandisk, a samsung hdd test... They showed no errors but memtest.
Memtest86 found out loads of errors coming from both RAMs and so i bought new ones: Kingstone HyperX KHX1600C8D3K2. I had same problems: freeze and errors just after boot, not later (played some heavy game for more than 5 hours or so).

I tested old rams on another computer, and they worked just fine.

Oh, and i format/install Windows7 about three times.

I tried to remove GPU and tried to use MOBO GPU, but it still freezed.

Right now i have no freeze/BSoD on boot, but only while playing (after few secs).

P.S. : I had 2 BSoD using the BsoD collecting application.

P.P.S. : Some things are written in italian because i'm running an italian OS.
Attached Files
File Type: rar Windows7_Vista_jcgriff2.rar (1.01 MB, 40 views)
Gravhur is offline  
Sponsored Links
Advertisement
 
Old 09-29-2011, 01:43 PM   #2
Registered Member
 
Join Date: Sep 2011
Posts: 2
OS: Windows 7 64 bit



Here some Blue Screen coming from Driver Verifier ...
If my Blue Screen View says the truth, they come from MagicIso... Which i have installed, like, today...
Attached Files
File Type: rar Minidump.rar (66.0 KB, 41 views)
Gravhur is offline  
Old 09-30-2011, 06:40 AM   #3
TSF Team Emeritus
Microsoft MVP
 
usasma's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2009
Location: Southeastern CT, USA
Posts: 7,483
OS: Win7



NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

You tested old RAM in the system and it failed MemTest
You bought new RAM and put in the system. Did you test it with MemTest? If not, please do so (stop the test as soon as errors start appearing)
You tested the old RAM in another system with MemTest and got no errors

This seems to be a motherboard problem. But you can better isolate it by running these free stress tests:
Quote:
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"
- Please run all 3 tests (Blend, Small FFT's, and Large FFT's) - and keep track of the time it takes to get an error in each test.
- "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).
Monitor the CPU temperature and DON'T let it exceed 85║C. If it does, then you probably have a CPU cooling problem.
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.
More details on the use of this test: Torture test your CPU with Prime95
Perfmon relates that the "dirty bit" is set on your E: and F: drives. To fix this, run CHKDSK /R /F on both volumes (yes, I know this is supposedly redundant - but I have good results with it) then rerun perfmon to ensure that it's fixed. If it isn't fixed, the volumes will have to be formatted to reset the "dirty bit" - which will erase all info on those drives. I'd also suggest running a bootable hard drive test on the disk(s) to be sure that the drive isn't failiing. Here's a link to the free tools:
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Wireless USB devices can cause BSOD issues on Win7 systems - especially if using Vista drivers. I haven't seen anything that indicates that this is your problem, but wanted to warn you about the issues with these devices. Here's my rant on the subject:
Quote:
I do not recommend using wireless USB devices.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
MSINFO32 shows 7 BSOD's over a period of 10 days
It shows 5 different BSOD error codes
and blames at least 4 different causes
This is usually symptomatic of a hardware/compatibility problem (and tends to support the supposition that your motherboard is damaged.

The memory dumps show 15 memory dumps over a period of 11 days
It shows 6 different BSOD error codes
and blames at least 7 dufferent causes
This is also symptomatic of a hardware issue.

Finally, there are 3 Verifier enabled memory dumps. They are all the same, and they all blame MagicISO drivers. It's possible that MagicISO is contributing to the problem - and it should be uninstalled until the rest of the problems are fixed.

Top 3 reports are Verifier enabled, the rest are normal memory dumps:
[B]BSOD BUGCHECK SUMMARY
Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-21122-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 16:29:55.500 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:13.061
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`076d9a00 00000000`0000008a 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-20311-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 16:13:41.163 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:19.724
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`0a90b2c0 00000000`0000008a 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-20654-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 15:41:02.969 2011 (UTC - 4:00)
System Uptime: 0 days 1:09:59.529
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`0abae210 00000000`0000008a 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-19546-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 13:30:31.391 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:31.562
Probably caused by : memory_corruption ( nt!MiResolveProtoPteFault+13f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveProtoPteFault+13f
Bugcheck code 0000000A
Arguments fffffa00`09bfdf90 00000000`00000002 00000000`00000000 fffff800`030b64af
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-20155-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 11:45:16.554 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:55.725
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_nt!PoIdle+52a
Bugcheck code 0000007E
Arguments ffffffff`c0000005 fffff880`0456305b fffff880`03c35698 fffff880`03c34ef0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-18969-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 28 11:59:58.534 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:07.126
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AVGIDSAgent.ex
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ebfb65 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-22448-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 28 06:14:27.050 2011 (UTC - 4:00)
System Uptime: 0 days 0:39:29.252
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`03964820 fffffa80`03964820 ff7ffa80`03964820
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-21793-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 28 05:34:23.718 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:18.310
*** WARNING: Unable to verify timestamp for AVGIDSDriver.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.Sys
Probably caused by : AVGIDSDriver.Sys ( AVGIDSDriver+862f )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_AVGIDSDriver+862f
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ed0d58 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092711-29905-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Sep 27 11:46:33.039 2011 (UTC - 4:00)
System Uptime: 0 days 6:49:29.631
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`045bdcee fffff880`03c366a8 fffff880`03c35f00
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092611-23618-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 26 09:17:58.830 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:36.391
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092611-21808-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 26 09:07:43.078 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:57.654
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092511-24757-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Sep 25 13:36:06.400 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:10.587
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092411-23696-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Sep 24 11:08:51.313 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:30.890
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3B_nt!PoIdle+52a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`002c430f fffff880`0a1e40c0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092311-24788-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep 23 17:35:46.307 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:39.493
Probably caused by : memory_corruption ( nt!MmCreateSection+482 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmCreateSection+482
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031dcba2 fffff880`0959cf50 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092311-24601-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep 23 03:39:13.577 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:40.154
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck FE, {5, fffffa80054b71a0, 10024396, fffffa8005edf258}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_nt!PoIdle+52a
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`054b71a0 00000000`10024396 fffffa80`05edf258
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092111-32105-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 21 14:07:33.938 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:54.109
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f
Bugcheck code 0000000A
Arguments fffffa00`06ebb5b0 00000000`00000002 00000000`00000000 fffff800`02f72f9f
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092111-32058-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 21 14:03:03.648 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:51.819
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\091911-33540-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 19 13:26:24.220 2011 (UTC - 4:00)
System Uptime: 0 days 0:29:57.766
Probably caused by : tcpip.sys ( tcpip!TcpTcbReceive+2cc )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_tcpip!TcpTcbReceive+2cc
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`00b9a0b0 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
__________________
John Carrona, Microsoft MVP - Windows Expert - Consumer
Driver Reference Table ` ` BSOD Index
usasma is offline  
Sponsored Links
Advertisement
 
Old 09-30-2011, 06:40 AM   #4
TSF Team Emeritus
Microsoft MVP
 
usasma's Avatar

Microsoft Most Valuable Professional
 
Join Date: Apr 2009
Location: Southeastern CT, USA
Posts: 7,483
OS: Win7



NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

You tested old RAM in the system and it failed MemTest
You bought new RAM and put in the system. Did you test it with MemTest? If not, please do so (stop the test as soon as errors start appearing)
You tested the old RAM in another system with MemTest and got no errors

This seems to be a motherboard problem. But you can better isolate it by running these free stress tests:
Quote:
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"
- Please run all 3 tests (Blend, Small FFT's, and Large FFT's) - and keep track of the time it takes to get an error in each test.
- "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).
Monitor the CPU temperature and DON'T let it exceed 85║C. If it does, then you probably have a CPU cooling problem.
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.
More details on the use of this test: Torture test your CPU with Prime95
Perfmon relates that the "dirty bit" is set on your E: and F: drives. To fix this, run CHKDSK /R /F on both volumes (yes, I know this is supposedly redundant - but I have good results with it) then rerun perfmon to ensure that it's fixed. If it isn't fixed, the volumes will have to be formatted to reset the "dirty bit" - which will erase all info on those drives. I'd also suggest running a bootable hard drive test on the disk(s) to be sure that the drive isn't failiing. Here's a link to the free tools:
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Wireless USB devices can cause BSOD issues on Win7 systems - especially if using Vista drivers. I haven't seen anything that indicates that this is your problem, but wanted to warn you about the issues with these devices. Here's my rant on the subject:
Quote:
I do not recommend using wireless USB devices.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
MSINFO32 shows 7 BSOD's over a period of 10 days
It shows 5 different BSOD error codes
and blames at least 4 different causes
This is usually symptomatic of a hardware/compatibility problem (and tends to support the supposition that your motherboard is damaged.

The memory dumps show 15 memory dumps over a period of 11 days
It shows 6 different BSOD error codes
and blames at least 7 dufferent causes
This is also symptomatic of a hardware issue.

Finally, there are 3 Verifier enabled memory dumps. They are all the same, and they all blame MagicISO drivers. It's possible that MagicISO is contributing to the problem - and it should be uninstalled until the rest of the problems are fixed.

Top 3 reports are Verifier enabled, the rest are normal memory dumps:BSOD BUGCHECK SUMMARY
Code:

Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-21122-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 16:29:55.500 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:13.061
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`076d9a00 00000000`0000008a 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-20311-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 16:13:41.163 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:19.724
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`0a90b2c0 00000000`0000008a 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-20654-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 15:41:02.969 2011 (UTC - 4:00)
System Uptime: 0 days 1:09:59.529
*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : mcdbus.sys ( mcdbus+36823 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_81
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823
Bugcheck code 000000C4
Arguments 00000000`00000081 fffffa80`0abae210 00000000`0000008a 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-19546-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 13:30:31.391 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:31.562
Probably caused by : memory_corruption ( nt!MiResolveProtoPteFault+13f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  WmiPrvSE.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveProtoPteFault+13f
Bugcheck code 0000000A
Arguments fffffa00`09bfdf90 00000000`00000002 00000000`00000000 fffff800`030b64af
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092911-20155-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Sep 29 11:45:16.554 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:55.725
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_nt!PoIdle+52a
Bugcheck code 0000007E
Arguments ffffffff`c0000005 fffff880`0456305b fffff880`03c35698 fffff880`03c34ef0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-18969-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 28 11:59:58.534 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:07.126
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AVGIDSAgent.ex
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ebfb65 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-22448-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 28 06:14:27.050 2011 (UTC - 4:00)
System Uptime: 0 days 0:39:29.252
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`03964820 fffffa80`03964820 ff7ffa80`03964820
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092811-21793-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 28 05:34:23.718 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:18.310
*** WARNING: Unable to verify timestamp for AVGIDSDriver.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.Sys
Probably caused by : AVGIDSDriver.Sys ( AVGIDSDriver+862f )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_AVGIDSDriver+862f
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02ed0d58 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092711-29905-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Sep 27 11:46:33.039 2011 (UTC - 4:00)
System Uptime: 0 days 6:49:29.631
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`045bdcee fffff880`03c366a8 fffff880`03c35f00
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092611-23618-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 26 09:17:58.830 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:36.391
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092611-21808-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 26 09:07:43.078 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:57.654
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092511-24757-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Sep 25 13:36:06.400 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:10.587
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+a15
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092411-23696-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Sep 24 11:08:51.313 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:30.890
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x3B_nt!PoIdle+52a
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`002c430f fffff880`0a1e40c0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092311-24788-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep 23 17:35:46.307 2011 (UTC - 4:00)
System Uptime: 0 days 0:08:39.493
Probably caused by : memory_corruption ( nt!MmCreateSection+482 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!MmCreateSection+482
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031dcba2 fffff880`0959cf50 00000000`00000000
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092311-24601-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep 23 03:39:13.577 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:40.154
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck FE, {5, fffffa80054b71a0, 10024396, fffffa8005edf258}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_nt!PoIdle+52a
Bugcheck code 000000FE
Arguments 00000000`00000005 fffffa80`054b71a0 00000000`10024396 fffffa80`05edf258
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092111-32105-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 21 14:07:33.938 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:54.109
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f
Bugcheck code 0000000A
Arguments fffffa00`06ebb5b0 00000000`00000002 00000000`00000000 fffff800`02f72f9f
BiosVersion = 0703   
BiosReleaseDate = 12/23/2010
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\092111-32058-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Sep 21 14:03:03.648 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:51.819
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\091911-33540-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Sep 19 13:26:24.220 2011 (UTC - 4:00)
System Uptime: 0 days 0:29:57.766
Probably caused by : tcpip.sys ( tcpip!TcpTcbReceive+2cc )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_tcpip!TcpTcbReceive+2cc
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`00b9a0b0 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
__________________
John Carrona, Microsoft MVP - Windows Expert - Consumer
Driver Reference Table ` ` BSOD Index
usasma is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
Crashes and BSOD at random intervals of time
Hi guys, I've been having random crashesd and BSOD (I got a crash while making this thread and had to reboot!). First let me post my specs: https://img199.imageshack.us/img199/3812/specste.png I recently had XP (still have it in my 80gig HDD) and decided to update to win7 on my other HDD (320...
Nathan Graves BSOD, App Crashes And Hangs 2 08-10-2011 03:04 AM
BSOD after sleep and (rarely) fresh boot
Hi all, I have a Dell XPS15 laptop. Specs are: *Win7 x64 *OEM original install from vendor *system purchased only 6 mo. ago *bought refurbished from Dell. I'm assuming Dell just wipes refurbs and installs OS anew. So, basically 6 mo. I have not re-installed the OS. *cpu = Intel i5 M 460 @...
Speedicut BSOD, App Crashes And Hangs 2 08-06-2011 10:56 AM
BSOD Windows 7 64bit Random.
Hey guys, I'm experiencing random BSOD at the minute and I can't seem to find the cause. The computer has been running fine for about 6 months, prior to that I was getting regular BSOD and after changing my motherboard frorm a Crosshair III to a Crosshair IV it seem to eliminate the problem...
Caatalyst BSOD, App Crashes And Hangs 23 06-20-2011 07:37 AM
Random BSOD while playing game
hi, i got random BSOD while i playing a game, somewhat it's always happens in online game (starcraft 2, WoW, Rift) and never happens when im playing offline game. i already update the driver for my wireless LAN, but the problem still occurs. could you help me, Thanks this is my spec OS - Win...
CR353 BSOD, App Crashes And Hangs 19 04-19-2011 06:14 AM
BSOD random, driver_power_state_failure (9F)
Hello everyone, So here is the scenario: My laptop has been working perfectly for months and months, but then one day i tried something new, I installed Connectify which promised to give me the functionality that i needed at the moment, so I installed it and restarted my computer, right after...
erral BSOD, App Crashes And Hangs 2 04-17-2011 05:40 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 01:41 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts