Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: omega3000 on 05 June 2013, 22:02:20
-
Ive heard of the blue screen virus , just had an automatic shutdown >:( No harm done i think :-\
-
something has caused it to shutdown, there is a program you can download that captures the problem from nirsoft :y
-
did you add any new ram, card or driver ?
and your cpu fans are clean ?
-
something has caused it to shutdown, there is a program you can download that captures the problem from nirsoft :y
Yes , then it rebooted itself :-\ Ran Spybot ... no unusual problems :-\
did you add any new ram, card or driver ?
and your cpu fans are clean ?
Its laptop cem , nothing added .. dont know about the fans or how to clean them . I know my old tower use to get blocked up with dust :(
-
something has caused it to shutdown, there is a program you can download that captures the problem from nirsoft :y
Yes , then it rebooted itself :-\ Ran Spybot ... no unusual problems :-\
did you add any new ram, card or driver ?
and your cpu fans are clean ?
Its laptop cem , nothing added .. dont know about the fans or how to clean them . I know my old tower use to get blocked up with dust :(
blue screens are hardware and diver related mostly .. if its not heat related you have a problem :P
-
something has caused it to shutdown, there is a program you can download that captures the problem from nirsoft :y
Yes , then it rebooted itself :-\ Ran Spybot ... no unusual problems :-\
did you add any new ram, card or driver ?
and your cpu fans are clean ?
Its laptop cem , nothing added .. dont know about the fans or how to clean them . I know my old tower use to get blocked up with dust :(
blue screens are hardware and diver related mostly .. if its not heat related you have a problem :P
There's probably a flipper stuck in the cooling fan! ;D ;)
-
What was the STOP code? Will be in the event log if you didn't grab it.
BSOD are where the kernel cannot (100% safely) recover from an unexpected situation, so it just stops everything. The kernel is tried and tested, and rock solid. If the STOP code was 0A or 1E, its 99.99% certain its a driver/hardware (actually, its always the driver, but usually because the controlled hardware has not acted as expected). Drivers are better than the used to be, so its going to be hardware, especially if you haven't installed new drivers recently.
The alarm bells are ringing, as you said laptop. These suffer from cooling issues, esp those with the (utterly pointless) discrete GPUs.
What make/model?
-
Yep it would help if you could advise stop code - control panel-->administrative tools-->event viewer ;)
-
Microsoft-Windows-Kernel-EventTracing ErrorCode 3221225525 ???
Sony Vaio
The programe explorer EXE version 6.1.7601.17567 stopped interacting with Windows and closed
-
Microsoft-Windows-Kernel-EventTracing ErrorCode 3221225525 ???
Nope
Sony Vaio
Oh dear ::)
-
Microsoft-Windows-Kernel-EventTracing ErrorCode 3221225525 ???
Nope
Sony Vaio
Oh dear ::)
(http://i600.photobucket.com/albums/tt84/SVT-GT500/smileys/bangheadsmiley-1.gif)
-
Microsoft-Windows-Kernel-EventTracing ErrorCode 3221225525 - this is one of those common "safe to ignore" errors what won't get fixed - shouldn't cause it to blue screen. What you want is the stop code.
Assuming you are running Win7 you can stop Windows rebooting to allow you to get stop code off BSOD.
Go to Control Panel--> System-->Advanced System Settings (on left hand side), then click on settings on "Startup & Recovery" section (bottom one) and under System Failure untick Auto Restart box. Click OK, Apply and then reboot Windoze.
Next time you have an issue (BSOD), it won't reboot and read errorcode off screeen. Thats the code required :y
Vaio - thats what I'm using at the mo ;)
-
Microsoft-Windows-Kernel-EventTracing ErrorCode 3221225525 - this is one of those common "safe to ignore" errors what won't get fixed - shouldn't cause it to blue screen. What you want is the stop code.
Assuming you are running Win7 you can stop Windows rebooting to allow you to get stop code off BSOD.
Go to Control Panel--> System-->Advanced System Settings (on left hand side), then click on settings on "Startup & Recovery" section (bottom one) and under System Failure untick Auto Restart box. Click OK, Apply and then reboot Windoze.
Next time you have an issue (BSOD), it won't reboot and read errorcode off screeen. Thats the code required :y
Vaio - thats what I'm using at the mo ;)
Done , thanks mate :y
-
When it next crashes with a bsod read the stop code before you turn off/restart it and post up here - it will be obvious which code you require - should look something like this (example only) . . .
STOP Error 0x00000065: MEMORY1_INITIALIZATION_FAILED
STOP code 0x00000065 may also display "MEMORY1_INITIALIZATION_FAILED" on the same STOP message
HTH Steve :y
-
Is there not an event in the System Log something like Bugtrap?
-
looking at the other fan buying thread temp problem comes to my mind.. open bios and monitor cpu temp..
-
Is there not an event in the System Log something like Bugtrap?
Just as easy to read stop code off bsod :)
-
Is there not an event in the System Log something like Bugtrap?
Bug Check Event ID:1001
System rebooted after bugcheck
-
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 ;)
-
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 :y
-
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.
-
0xC0000188 :-\
-
0xC0000188 :-\
Post up the entire text for that log message
-
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
-
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.
-
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 :y
If you like email me the relevant memory dump file & I'll have a nose
-
:y
Am running the scan now , will take a while ;)
Scan did not find any violations :)
-
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.
-
No usb devices were plugged in and at the time it was on mains charge :-[