Random restarts.
- Thread starter Jimbo
- Start date
Goto control panel, system, Advanced tab, system and recovery settings, remove the tick from automatically restart.
This will give you a BSOD next time it dies. See what that says.
Also in the event viewer (control panel, admin tools) click the system tab and see if you have any red entries at the time it crashes.
This will give you a BSOD next time it dies. See what that says.
Also in the event viewer (control panel, admin tools) click the system tab and see if you have any red entries at the time it crashes.
I have auto restart unticked. I have worked out how to use event viewer, and I have one red error, but it wasnt when it restarted.
I do have this though...
A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I think this might be when it restarted?
Or it could be caused by perfect disk scheduler as I notice ot said started just before it crashed.
I do have this though...
A provider, OffProv11, has been registered in the WMI namespace, Root\MSAPPS11, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I think this might be when it restarted?
Or it could be caused by perfect disk scheduler as I notice ot said started just before it crashed.
Don't think that error would be the prob, not 100% sure what that is to be honest.
From the ms page:
http://support.microsoft.com/kb/891642
Did you get anything from the BSOD?
From the ms page:
http://support.microsoft.com/kb/891642
Did you get anything from the BSOD?
Thanks for the reply, sorry i been at work.
The problem is I dont get a blue screen, but lately I have had 2 resets. Once I was listnen to something on media player, and I heard a couple of pops from my speakers and it reseted. The other time the pc was just sitting idle.
I'll keep an eye on it to see if it re occours.
The problem is I dont get a blue screen, but lately I have had 2 resets. Once I was listnen to something on media player, and I heard a couple of pops from my speakers and it reseted. The other time the pc was just sitting idle.
I'll keep an eye on it to see if it re occours.
I don't have any from today and it restarted about 30mins ago. I do have one from yesterday evening, but i think that one actually bsod'd. How do you open these up, as i opened in notepad and its just garble....can post if you like though...
You need the Windows debugging tools - http://www.microsoft.com/whdc/devtools/debugging/default.mspx but it's a pain to setup. 
Post the file up here / email me and i can take a look. It should only be a few hundred kb or so.
Post the file up here / email me and i can take a look. It should only be a few hundred kb or so.
Cool thanks Pho. It bsod'd whilst i was trying to do a virus scan (completed virus scan after restart btw). I took a pic of the bsod, see link below
BSOD
And here is the minidump from that restart:
Minidump here
Many thanks for helping me here, hope you find something rectifiable.
BSOD
And here is the minidump from that restart:
Minidump here
Many thanks for helping me here, hope you find something rectifiable.
Code:
1: 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: 00000054, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80501ff4, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000054
CURRENT_IRQL: 1c
FAULTING_IP:
nt!KiUnlinkThread+0
80501ff4 095154 or dword ptr [ecx+54h],edx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: MpfTray.exe
LAST_CONTROL_TRANSFER: from 80502062 to 80501ff4
STACK_TEXT:
94d8cc10 80502062 87574990 87574998 00000100 nt!KiUnlinkThread
94d8cc24 80502259 00000000 94d8cc40 87574990 nt!KiUnwaitThread+0x12
94d8cc50 804f8529 87552da8 87574ac8 94d8ccf0 nt!KiWaitTest+0xab
94d8cc60 805d0e6d 87574990 00000000 00000000 nt!KeSetProcess+0x31
94d8ccf0 805d0fb9 c0000005 94d8cd4c 804fecb1 nt!PspExitThread+0x5b9
94d8ccfc 804fecb1 86fa12b8 94d8cd48 94d8cd3c nt!PsExitSpecialApc+0x23
94d8cd4c 80540677 00000001 00000000 94d8cd64 nt!KiDeliverApc+0x1af
94d8cd4c 7c90eb94 00000001 00000000 94d8cd64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0180fe28 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiUnlinkThread+0
80501ff4 095154 or dword ptr [ecx+54h],edx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiUnlinkThread+0DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: MpfTray.exe
Is the output from your dump. I'm not an expert with the debugging tools, but it lists the process as MpfTray.exe - which according to Google belongs to McAffe Firewall - it may be a good start to uninstall that.
Cool, thanks i will look into that, if i post another one from say yesterday could you have a look and see if its the same msg? Does the bsod mean anything to you?
dump from last night : have another dump
Thanks again
dump from last night : have another dump
Thanks again
Well the BSOD gives a good idea of the problem but the debugging tools should give the actual source .
IRQL_NOT_LESS_OR_EQUAL (your first dump) - "This behavior can occur if there is incompatible hardware or an incompatible device driver on your computer."
http://support.microsoft.com/kb/311564
The other dump is DRIVER_IRQL_NOT_LESS_OR_EQUAL. I'm not sure what the cause is though, I can't work it out from the debug. Maybe someone else can?
.IRQL_NOT_LESS_OR_EQUAL (your first dump) - "This behavior can occur if there is incompatible hardware or an incompatible device driver on your computer."
http://support.microsoft.com/kb/311564
The other dump is DRIVER_IRQL_NOT_LESS_OR_EQUAL. I'm not sure what the cause is though, I can't work it out from the debug. Maybe someone else can?
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {85, 2, 1, b7a8069a}
Probably caused by : hardware ( serial!SerialRundownIrpRefs+58 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 00000085, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b7a8069a, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000085
CURRENT_IRQL: 2
FAULTING_IP:
serial!SerialRundownIrpRefs+58
b7a8069a 832000 and dword ptr [eax],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
MISALIGNED_IP:
serial!SerialRundownIrpRefs+58
b7a8069a 832000 and dword ptr [eax],0
LAST_CONTROL_TRANSFER: from b7a805ed to b7a8069a
STACK_TEXT:
80550280 b7a805ed 8a026a3c 8a026d50 8a026d28 serial!SerialRundownIrpRefs+0x58
805502a4 b7a79720 8a026978 b7a8052c 00000002 serial!SerialTryToCompleteCurrent+0x41
805502e0 80501543 8a026ba4 8a026978 9f85b208 serial!SerialReadTimeout+0x59
805503fc 8050165f 8055b0a0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b
80550428 80544e5f 8055b4a0 00000000 00078cff nt!KiTimerExpiration+0xb1
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544d44 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
serial!SerialRundownIrpRefs+58
b7a8069a 832000 and dword ptr [eax],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: serial!SerialRundownIrpRefs+58
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_serial.sys
BUCKET_ID: IP_MISALIGNED_serial.sysHmmm the plot thickens......I was just wondering if the first one listed the MpfTray.exe, due to it being the last thing that the comp had seen ( if you know what i mean) I have had McAfee for years now and not had an issie before, not overly keen on moving to Nortons either!
Would be good if someone else could shed some light on this second dump as i have looked at all the normal restart issues, run blend for an hour etc, board has memtest built in i believe so i could run that for a while. PSU is 600w Seasonic, so i should be safe with power. The problem is that it does not do it at any particualr time, just very random with sometimes 24 hours between them. Have not tried playing any FPS's yet to see if that causes it, but have been playing Dark Crusade a lot and has only done it once whilst playing.
Not sure if the above helps at all, would just like to determine if its a software issue or hardware atleast as do not fancy re-installing then finding that it still does it. Also on the flip side do not have the cash to start splashing out on new ram when not needed etc.
Any help is very appreciated.
Would be good if someone else could shed some light on this second dump as i have looked at all the normal restart issues, run blend for an hour etc, board has memtest built in i believe so i could run that for a while. PSU is 600w Seasonic, so i should be safe with power. The problem is that it does not do it at any particualr time, just very random with sometimes 24 hours between them. Have not tried playing any FPS's yet to see if that causes it, but have been playing Dark Crusade a lot and has only done it once whilst playing.
Not sure if the above helps at all, would just like to determine if its a software issue or hardware atleast as do not fancy re-installing then finding that it still does it. Also on the flip side do not have the cash to start splashing out on new ram when not needed etc.
Any help is very appreciated.
Nice one Jimbo, seems you have passed it onto me ! lol 
Mine are not regular, just annoying and never whilst doing the same thing.
The only thing that i am thinking is possibly hard drive. Like i said before, i have tested the memory and do not have any clocking going on. So was thinking of getting a new HD and re-installing, hmmm a raptor maybe?
Either way, i do not have a hard and fast solution, so atleast this way i will be ruling out drivers and HD as the HD does make more noise than it used to ( have done a check disk and defrag though).
Anyone have any other views?
Cheers
Mine are not regular, just annoying and never whilst doing the same thing.The only thing that i am thinking is possibly hard drive. Like i said before, i have tested the memory and do not have any clocking going on. So was thinking of getting a new HD and re-installing, hmmm a raptor maybe?
Either way, i do not have a hard and fast solution, so atleast this way i will be ruling out drivers and HD as the HD does make more noise than it used to ( have done a check disk and defrag though).
Anyone have any other views?
Cheers
One question, what does it generally mean if your machine restarts, but with no minidump and no log in event viewer? I just came back in the room and found it at login....
Like i said above my general plan atm, is to replace the boot drive and re-install, that way i can rule out driver conflicts and hd failiure.
cheers
Like i said above my general plan atm, is to replace the boot drive and re-install, that way i can rule out driver conflicts and hd failiure.
cheers