BSOD every 15 mins USB_BUDCODE_DRIVER and IRL_...

[Tr3MoR]

I previously posted on here and you guys were great and solved my problem. The link to that thread can be found here:
http://www.sevenforums.com/crashes-...budcode_usb_driver-help-asap.html#post1469862

I have since had my harddrive go out, and replaced it with a 7200 RPM Seagate and installed W7 professional x64.

My computer blue screens anywhere from every 15 mins-2 hours, and all the solutions from my previous thread have failed to fix it this time around. The second Bluescreen is new but I believed started with IRL_ something. If it happens again with that error I will edit to update right away.

My system specs are:
-Asus U30JC
-Freshly installed W7 64 bit professional
-4gb ram, i3
-New 500 gb 7200 rpm seagate
-13 months old.

I thought all the drivers have been installed correctly, but it seems that isn't the case. Any help is greatly appreciated as my laptop is virtually useless for extended periods of time.

Thanks in advance to anyone that can help, the latest .dmp has the new error, the other ones are likely all BUGCODE_USB_DRIVER

 

[ePeen]

Very sorry to hear you're still undergoing BSOD related issues my friend, I know how stressful they can be. I'm sure we'll all do our best here to get you BSOD free!

I took a look at multiple dumps, it's a trade off between the FE and D1 bugchecks, some 0XA bugchecks there too. (Bugcode USB Driver) or (DRIVER IRQL NOT LESS OR EQUAL). Tons of usbhub.sys errors.

BUGCODE_USB_DRIVER (fe) is generally caused by a bad USB connection / port or hub. I would recommend running your system BARE using only the keyboard and mouse. I would recommend swapping out both the keyboard and mouse (or one at a time). I would also mess around with various USB ports when running bare to ensure that it isn't a bad USB hub / port.

Onto the other things I have noticed. Whether it's a coincidence or not, the IRQL bugchecks all listed the process fault as uTorrent.exe, so for now... I'd disable uTorrent or uninstall it for testing purposes.

Another thing I have noticed is in a few dumps in mentions the inability to load the symbols and timestamps for NETw5s64.sys. NETw5s64.sys is the driver for the Intel 5100 Wifi, which can be updated here.

To uninstall your current network drivers (remember to download new version of network drivers first!!!!!!) follow these great instructions provided by writhziden:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Install the latest driver for the device.

BugCheck A, {0, 2, 0, fffff800031f5477}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+b76b )

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

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eba0e8
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+103
fffff800`031f5477 448b08          mov     r9d,dword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  uTorrent.exe

TRAP_FRAME:  fffff8800de4c540 -- (.trap 0xfffff8800de4c540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000018c
rdx=000000000000018c rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031f5477 rsp=fffff8800de4c6d8 rbp=0000000000000000
 r8=000000000000001c  r9=0000000000000000 r10=00000000000fffff
r11=fffffa8005e43970 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`031f5477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c88be9 to fffff80002c89640

STACK_TEXT:  
fffff880`0de4c3f8 fffff800`02c88be9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0de4c400 fffff800`02c87860 : fffffa80`0a93ddc0 fffff880`05654c2e fffffa80`045cbb20 fffffa80`04dadc10 : nt!KiBugCheckDispatch+0x69
fffff880`0de4c540 fffff800`031f5477 : fffffa80`04126b40 fffffa80`04026e74 fffff800`031f5524 fffffa80`04dadc10 : nt!KiPageFault+0x260
fffff880`0de4c6d8 fffff800`031f5524 : fffffa80`04dadc10 fffffa80`05e43970 fffffa80`05e43670 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`0de4c6f0 fffff800`031f84fb : fffffa80`04dadc10 fffffa80`05e43970 fffffa80`04126b40 fffffa80`04ad1fd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`0de4c740 fffff800`031f8472 : fffffa80`04dadc10 fffffa80`04dadc08 00000000`0000001c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`0de4c7d0 fffff800`031f794f : 00000000`00000000 fffff800`031f4fb9 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`0de4c810 fffff800`031f7afd : fffffa80`057f4050 fffffa80`05e43970 00000000`00000001 fffffa80`000003f7 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`0de4c8b0 fffff800`031f8156 : fffffa80`05e43970 00000000`00000000 fffffa80`05e43900 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`0de4c8e0 fffff800`031f771f : fffffa80`0418db70 00000000`00000050 fffffa80`05e43970 fffffa80`03f812e0 : hal!HalAllocateAdapterChannel+0x11a
fffff880`0de4c920 fffff880`014f7750 : fffffa80`04720290 fffffa80`05e435e0 fffffa80`000000a0 fffff880`058a1d50 : hal!HalBuildScatterGatherList+0x2f3
fffff880`0de4c990 fffff880`0565d76b : fffffa80`057f41a0 00000000`00000000 fffffa80`043c9dc0 fffff880`05802c30 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`0de4ca30 fffffa80`057f41a0 : 00000000`00000000 fffffa80`043c9dc0 fffff880`05802c30 00000000`00000000 : NETw5s64+0xb76b
fffff880`0de4ca38 00000000`00000000 : fffffa80`043c9dc0 fffff880`05802c30 00000000`00000000 00000050`00000100 : 0xfffffa80`057f41a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+b76b
fffff880`0565d76b ??              ???

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  NETw5s64+b76b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b13ae9c

FAILURE_BUCKET_ID:  X64_0xA_NETw5s64+b76b

BUCKET_ID:  X64_0xA_NETw5s64+b76b

Followup: MachineOwner

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8006793b20, TimeoutContext - PortData

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800426ba60 to fffff80002cd1640

STACK_TEXT:  
fffff880`031cbc18 fffff880`0426ba60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`031cbc20 fffff800`02fc7f33 : fffffa80`054ed050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02e6e658 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`031cbc80 fffff800`02cdba21 : fffff800`02e6e600 fffff800`02fc7f01 fffffa80`03e75600 fffffa80`063ab980 : nt!IopProcessWorkItem+0x23
fffff880`031cbcb0 fffff800`02f6ecce : fffffa80`03ec9060 fffffa80`03e75680 00000000`00000080 fffffa80`03e5f990 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02cc2fe6 : fffff880`02fd5180 fffffa80`03e75680 fffff880`02fdffc0 fffff800`02de4ad4 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`0426ba60 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a68e

FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800583d524, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f060e8
 0000000000000030 

CURRENT_IRQL:  2

FAULTING_IP: 
NETw5s64+1b4524
fffff880`0583d524 488b4930        mov     rcx,qword ptr [rcx+30h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  uTorrent.exe

TRAP_FRAME:  fffff8800b8ea760 -- (.trap 0xfffff8800b8ea760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80049f9c88 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800583d524 rsp=fffff8800b8ea8f0 rbp=0000000000000048
 r8=fffffa80047e4e70  r9=fffff8800b8ea920 r10=078bb256f3ab3276
r11=fffff8800b8ea8e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
NETw5s64+0x1b4524:
fffff880`0583d524 488b4930        mov     rcx,qword ptr [rcx+30h] ds:b300:00000000`00000030=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd4be9 to fffff80002cd5640

STACK_TEXT:  
fffff880`0b8ea618 fffff800`02cd4be9 : 00000000`0000000a 00000000`00000030 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b8ea620 fffff800`02cd3860 : fffffa80`044db000 00000000`00000001 00000000`00000002 fffffa80`049f9c30 : nt!KiBugCheckDispatch+0x69
fffff880`0b8ea760 fffff880`0583d524 : fffffa80`044db000 00000000`00000001 fffffa80`0657b300 fffff800`02c11472 : nt!KiPageFault+0x260
fffff880`0b8ea8f0 fffffa80`044db000 : 00000000`00000001 fffffa80`0657b300 fffff800`02c11472 fffffa80`047e4eb8 : NETw5s64+0x1b4524
fffff880`0b8ea8f8 00000000`00000001 : fffffa80`0657b300 fffff800`02c11472 fffffa80`047e4eb8 fffffa80`047e4eb0 : 0xfffffa80`044db000
fffff880`0b8ea900 fffffa80`0657b300 : fffff800`02c11472 fffffa80`047e4eb8 fffffa80`047e4eb0 00000000`00000000 : 0x1
fffff880`0b8ea908 fffff800`02c11472 : fffffa80`047e4eb8 fffffa80`047e4eb0 00000000`00000000 00000000`00000000 : 0xfffffa80`0657b300
fffff880`0b8ea910 fffff800`02c109ce : fffffa80`047e4eb8 fffff800`02c0dfb9 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`0b8ea950 fffff800`02c10afd : fffffa80`0568e050 fffffa80`05dfc130 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0x146
fffff880`0b8ea9f0 fffff800`02c11156 : fffffa80`05dfc130 00000000`00000500 fffffa80`05dfc100 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`0b8eaa20 fffff800`02c1071f : fffffa80`044a92f0 00000000`000005da fffffa80`05dfc130 fffffa80`04cd4f10 : hal!HalAllocateAdapterChannel+0x11a
fffff880`0b8eaa60 fffff880`01500750 : fffffa80`041b9210 fffffa80`05e8fd70 fffffa80`000000a0 fffff880`058d8d50 : hal!HalBuildScatterGatherList+0x2f3
fffff880`0b8eaad0 fffff880`0569476b : fffffa80`0568e1a0 00000000`00000000 fffffa80`046eb020 fffff880`05839c30 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`0b8eab70 fffffa80`0568e1a0 : 00000000`00000000 fffffa80`046eb020 fffff880`05839c30 00000000`00000000 : NETw5s64+0xb76b
fffff880`0b8eab78 00000000`00000000 : fffffa80`046eb020 fffff880`05839c30 00000000`00000000 000005da`00000100 : 0xfffffa80`0568e1a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+1b4524
fffff880`0583d524 488b4930        mov     rcx,qword ptr [rcx+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETw5s64+1b4524

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b13ae9c

FAILURE_BUCKET_ID:  X64_0xD1_NETw5s64+1b4524

BUCKET_ID:  X64_0xD1_NETw5s64+1b4524

Followup: MachineOwner

 

[Tr3MoR]

Thanks ePeen!

I will bump this thread after I have done all that you have listed, and then go from there. I actually do not use a keyboard or mouse, only an external harddrive and my windows phone and I believe it is the external that causes issues. Thanks again.

 

[ePeen]

No problem, keep updated!

 

[Tr3MoR]

Update: I did everything listed to no avail. It is doing it even more often now .

Attached is the new report...any help to solve this is appreciated

 

[ePeen]

Sorry to hear my friend.

All of the attached dumps are an FE bugcheck with the probable cause listed as usbhub.sys. This may be an issue with a specific driver, or a specific peripheral attached, or even possibly a malfunctioning usb hub that is shorting the system out.

I would recommend enabling Driver Verifier to see if it shows us any third party driver culprits causing this:

Driver Verifier:

Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Dump for reference:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032812-28048-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e52e90
Debug session time: Wed Mar 28 15:51:51.127 2012 (UTC - 4:00)
System Uptime: 0 days 0:43:53.188
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa8006a08b20}

Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa8006a08b20, TimeoutContext - PortData

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800f012a60 to fffff80002c8d640

STACK_TEXT:  
fffff880`031c4c18 fffff880`0f012a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`031c4c20 fffff800`02f83f33 : fffffa80`069f8050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02e2a658 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`031c4c80 fffff800`02c97a21 : fffff800`02e2a600 fffff800`02f83f01 fffffa80`03e81600 fffffa80`065e9d50 : nt!IopProcessWorkItem+0x23
fffff880`031c4cb0 fffff800`02f2acce : 00000000`00000040 fffffa80`03e81680 00000000`00000080 fffffa80`03e6ab30 : nt!ExpWorkerThread+0x111
fffff880`031c4d40 fffff800`02c7efe6 : fffff880`02fd5180 fffffa80`03e81680 fffff880`02fdffc0 ffff7b5b`df5e76fd : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`0f012a60 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a68e

FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

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

 

[Tr3MoR]

Attached is the latest dumps. The driver verifier just caused the same error that the previous ones did. No help, other than my computer now blue screens even more often.

Very frustrated atm. I can't figure out how to solve this so any further input is great

 

[writhziden]

First, disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:

verifier /reset​

-> Restart your computer.


For the USB related crashes:

• Start with http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
  
  1. Shut down and turn off the computer.
  2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
  3. "Remove the computer from any port replicator or docking station, disconnect
     cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
  4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
     power from components is drained to clear the software connections between the BIOS
     and hardware and clear any corruption in the temporary memory.
  5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
     and mouse should suffice and be the only peripherals reconnected.
  6. Turn it on to reinitialize the software connections between the BIOS and hardware

Some questions:

• What USB devices do you use?
• Are your Chipset drivers up to date?

 

[Tr3MoR]

I believe my chipset drivers are up to date, and I don't use any USB devices before it begins bluescreening. It says there is an unrecognized device attached when there is nothing attached.

I now have to run in safe mode...I created a restore point and installed windows update and now my computer will not run. Everything freezes as soon as I log in. And it deleted my restore points? I now have no way to restore my computer and am at a loss...help!

 

[writhziden]

Go through the steps in http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html and let us know if they resolve the issue. Also, post back if you need help with any steps.