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: Multiple BSOD Need Help

04 Apr 2011   #1
jco66mt

Windows 7 64bit
 
 
Multiple BSOD Need Help

Currently I have had about 23 BSOD over the past 3 Months or so. The crashes happen at all different times when I just boot and windows screen appears to playing game and even on the internet. I thought I just had a bad graphics card but I took it out and ran video off the motherboard. And I had a crash again. So not really sure what do to from here any help would be great!

PM BUGCODE_USB_DRIVER 0x000000fe 00000000`00000005 fffffa80`056721a0 00000000`10024396 fffffa80`06585250 USBPORT.SYS USBPORT.SYS+2de4e x64 C:\Windows\Minidump\040211-25412-01.dmp 4 15 7600 327,624 is the most frequent of the BSOD.
Not sure if i need to upload more information.


My System

MB-ASUS M4A88TH-V EV0/USB3
CPU-AMD Phenom II x4 965 Black Edition 3.4
GPU-XFX Radeon HD 5830
Memory-G. SKILL Ripjaws Series 4GB 2x2
OS-Windows 7 64bit
PSU-Corsairs 650W


My System SpecsSystem Spec
.
04 Apr 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jco66mt View Post
Currently I have had about 23 BSOD over the past 3 Months or so. The crashes happen at all different times when I just boot and windows screen appears to playing game and even on the internet. I thought I just had a bad graphics card but I took it out and ran video off the motherboard. And I had a crash again. So not really sure what do to from here any help would be great!

PM BUGCODE_USB_DRIVER 0x000000fe 00000000`00000005 fffffa80`056721a0 00000000`10024396 fffffa80`06585250 USBPORT.SYS USBPORT.SYS+2de4e x64 C:\Windows\Minidump\040211-25412-01.dmp 4 15 7600 327,624 is the most frequent of the BSOD.
Not sure if i need to upload more information.


My System




MB-ASUS M4A88TH-V EV0/USB3
CPU-AMD Phenom II x4 965 Black Edition 3.4
GPU-XFX Radeon HD 5830
Memory-G. SKILL Ripjaws Series 4GB 2x2
OS-Windows 7 64bit
PSU-Corsairs 650W





To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
My System SpecsSystem Spec
04 Apr 2011   #3
jco66mt

Windows 7 64bit
 
 

Sorry here is the information. I think.
My System SpecsSystem Spec
.

05 Apr 2011   #4
jco66mt

Windows 7 64bit
 
 

More Info
My System SpecsSystem Spec
07 Apr 2011   #5
Jonathan_King

Windows 7 Professional x64
 
 

Hello,

I'm seeing these events that spark my interest:
Code:
Event[4496]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2011-03-30T23:21:16.184
  Event ID: 5
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Voodoo-PC
  Description: 
{Registry Hive Recovered} Registry hive (file): '\??\Volume{7bfc2222-f542-11df-a715-806e6f6e6963}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{B6544FAC-7B7B-49E0-9A5B-C90909B5A35F}' was corrupted and it has been recovered. Some data might have been lost.


Event[5714]:
  Log Name: System
  Source: Ntfs
  Date: 2011-03-30T02:54:14.595
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Voodoo-PC
  Description: 
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShadowCopy4.

Event[12600]:
  Log Name: System
  Source: Display
  Date: 2011-03-24T06:37:04.000
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Voodoo-PC
  Description: 
Display driver amdkmdap stopped responding and has successfully recovered.
It sounds as if there may be multiple problems occurring here; one is hard drive trouble and the other is a graphics issue. Let's start with a disk check; run SeaTools: SeaTools for Windows | Seagate

Open a command prompt and enter:
Code:
chkdsk /r
I notice that your video card and onboard graphics chip use the same driver, atikmdag.sys. While we can rule out a physical chip problem, a buggy/incompatible driver is still on the table. I suggest you install the latest updates: AMD Graphics Drivers & Software
Code:
atikmdag.sys            Tue Oct 26 22:29:53 2010 (4CC78EA1)
I'm getting symbol errors for your Windows USB drivers; I'll contact someone who may understand this better than I do, but for now, install service pack 1: Learn how to install Windows 7 Service Pack 1 (SP1)

Symantec may be having trouble:
Code:
Unable to load image SYMEFA64.SYS, Win32 error 0n2
Remove old version completely: Norton Product Support | Installation and Uninstall

Replace with new version, or install MSE instead: http://www.microsoft.com/security_essentials

Update your Realtek ethernet adapter drivers as well; they may be to blame for the ndis.sys BSOD, and perhaps the Symantec one as well. Update link: Realtek
Code:
Rt64win7.sys            Mon Mar 22 05:57:14 2010 (4BA73EFA)
Finally ():

Run Memtest86, as I'm seeing some OS corruption: RAM - Test with Memtest86+

...Summary of the dumps:
Code:

Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr  4 12:27:34.736 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:44.359
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  TurboVHelp.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Mon Apr  4 12:22:10.913 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:07.162
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff880`0113dbd8
Probably caused by : Unknown_Module_fffff880_0113dbd8 ( Unknown_Module_fffff880_0113dbd8+32afc1a )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_Unknown_Module_fffff880_0113dbd8+32afc1a
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 15:52:25.416 2011 (UTC - 4:00)
System Uptime: 0 days 0:27:33.039
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 14:27:43.236 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:11.712
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Apr  3 00:00:08.615 2011 (UTC - 4:00)
System Uptime: 0 days 2:58:12.864
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_PollActiveControlEndpoint+57
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr  2 21:01:10.333 2011 (UTC - 4:00)
System Uptime: 0 days 5:37:03.957
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr  2 15:23:25.190 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:17.875
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr  2 15:19:46.618 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:16.867
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by : usbohci.sys ( usbohci+2ec8 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_usbohci+2ec8
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr  2 15:16:53.154 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:21.793
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by : usbohci.sys ( usbohci+2ec8 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_usbohci+2ec8
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Apr  2 14:57:23.921 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:50.169
Probably caused by : tdx.sys ( tdx!TdxEventReceiveConnection+25d )
BUGCHECK_STR:  0x19_22
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_22_tdx!TdxEventReceiveConnection+25d
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar 30 16:25:26.513 2011 (UTC - 4:00)
System Uptime: 0 days 19:07:41.136
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 20:04:21.392 2011 (UTC - 4:00)
System Uptime: 0 days 5:55:29.031
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 13:28:53.553 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:37.177
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+86d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ccsvchst.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiWaitForInPageComplete+86d
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar 29 13:25:28.279 2011 (UTC - 4:00)
System Uptime: 0 days 1:15:18.527
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xFE
PROCESS_NAME:  CarboniteServi
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+67
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 27 19:49:45.400 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:30.070
Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPagingFileIo+155
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sun Feb 27 19:42:07.296 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:37.545
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 23:23:48.946 2011 (UTC - 4:00)
System Uptime: 0 days 5:52:01.196
Probably caused by : afd.sys ( afd!AfdMapMdlChain+14 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_afd!AfdMapMdlChain+14
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 03:50:30.856 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:13.105
Probably caused by : ndis.sys ( ndis!ndisPreProcessOid+19d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_ndis!ndisPreProcessOid+19d
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Feb  5 11:44:03.043 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:15.291
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+45 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFullDeleteLcb+45
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Feb  5 02:35:50.377 2011 (UTC - 4:00)
System Uptime: 0 days 6:43:57.016
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+10c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFcb+10c
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 31 18:33:09.391 2011 (UTC - 4:00)
System Uptime: 0 days 5:02:29.029
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by : usbohci.sys ( usbohci+2ec8 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_usbohci+2ec8
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Jan 30 00:28:47.974 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:14.613
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906
SystemProductName = System Product Name
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
Full dump report (for other BSOD analysts): http://sysnative.com/jk/_99-dbug.txt
My System SpecsSystem Spec
Reply

 Multiple BSOD Need Help




Thread Tools




Similar help and support threads
Thread Forum
BSOD Multiple types multiple times a day, can't pin down the problem
Hello everyone, I came here once before for assistance, but the issue was unable to be resolved. Here is the link to the previous thread. https://www.sevenforums.com/bsod-help-support/342840-several-bsod-no-singular-triggers.html There is no singular trigger to set this off. Sometimes I can...
BSOD Help and Support
Multiple BSOD Multiple Drivers - Fresh Install (atikmdag.sys = main)
Hi, i had been having issues with bluescreens once every week or so. I took action by updating my drivers etc but this did not fix the issue. I re-installed windows and got all my drivers on and such yet the problem persists with more bluescreens, more often and with more driver causes. Before the...
BSOD Help and Support
BSOD Multiple times multiple errors 0x0000001A
Last week I started receiving BSODs, and after the first one it got to the point where my computer was not booting up and my hard drive was beeping very angrily at me. I was not sure what all the problems were, however I also knew that there was something seriously wrong with my hard drive, so I...
BSOD Help and Support
Multiple BSOD's with multiple errors occuring randomly
Just realized I uploaded the wrong zip folder, It doesn't have everything in it. Fixed that now though! Sorry about the hassle! So I built my own PC a a good few months back, and within a month I experienced a BSOD, and now they are very frequent. They can happen three or four times a day, or...
BSOD Help and Support
BSOD errors. multiple times during multiple programs
windows 7 x64 - original install on system but i don't have my disks. they are somewhere... - full retail version installed - age of the system is approximately 3 years - age of the install is approximately 2 years it seems to happen at random but i get BSODs. approximately 2-3 times a day...
BSOD Help and Support
Multiple BSOD at Random Times with Multiple Drivers Identified
I am trying to get my wife's new computer up and running without any BSOD or program failures. Note that the system was not initially set up to capture the dmp files so all the earliest ones are missing. I presented the initial problems to the original seller who recommended sticking with MSE and...
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 01:40.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App