Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cem_devecioglu]

looking at the other fan buying thread temp problem comes to my mind.. open bios and monitor cpu temp..

[dbug]

Is there not an event in the System Log something like Bugtrap?

Just as easy to read stop code off bsod

[omega3000]

Is there not an event in the System Log something like Bugtrap?

Bug Check Event ID:1001

System rebooted after bugcheck

[dbug]

Is there not an event in the System Log something like Bugtrap?

Bug Check Event ID:1001

System rebooted after bugcheck

Need the stop code

[TheBoy]

Is there not an event in the System Log something like Bugtrap?

Bug Check Event ID:1001

System rebooted after bugcheck

There should be other details in that

[TheBoy]

Is there not an event in the System Log something like Bugtrap?

Just as easy to read stop code off bsod

Means waiting for reoccurance.

[omega3000]

0xC0000188 

[TheBoy]

0xC0000188 

Post up the entire text for that log message

[TheBoy]

Actually, I think you've got that from the wrong event, I suspect that is from the kernel trap one.

Its the entire text from the Bugtrap one I need

[omega3000]

How come it wont let me copy 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000fe (0x0000000000000008, 0x0000000000000006, 0x000000000000000b, 0xfffffa8006fd9b20). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060513-29889-01.

[dbug]

How come it wont let me copy 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000fe (0x0000000000000008, 0x0000000000000006, 0x000000000000000b, 0xfffffa8006fd9b20). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060513-29889-01.

Stop Code 0x000000fe or Stop Error 000000FE (0xFE) usually relates to faults with USB drivers particularly your USBPORT.SYS driver.  Re-install the driver and then run a system file check to verify and repair your OS files

To do this type cmd in search, then right click to run as administrator, then type SFC /SCANNOW

If this doesn't cure your issue, your INFCACHE.1 file, which stores information about USB drivers, may have become corrupted and may cause windows to load the wrong driver or cause a driver not found message to be generated. You may have to delete this file which will force windows to generate a new INFCACHE.1 file.

HTH

If you like email me the relevant memory dump file & I'll have a nose

[omega3000]

 

Am running the scan now , will take a while 

Scan did not find any violations 

[TheBoy]

USBPORT.SYS is an MS provided driver, so unlikely to be that thats at fault per-se.

Did you have *any* USB devices plugged in when it BSOD'd, as faulty drivers for them could have caused the main USB driver to go into a tizz. The dump can show the state of the stack, so worth getting it off to someone who can read it (the Windows debugger isn't for the faint hearted - I used to use it almost daily in the Win2K days, and even then, I'd call myself just an amateur in it)

Lastly, was it on battery, or mains.

[omega3000]

No usb devices were plugged in and at the time it was on mains charge