
HELP computer freezing on its own need to force restart urgently pleas
#1
Posted 01 February 2014 - 06:19 AM

#3
Posted 01 February 2014 - 06:57 AM

#4
Posted 01 February 2014 - 07:18 AM

You are welcome btw matvey

#5
Posted 01 February 2014 - 07:24 AM


Attached Files
#6
Posted 01 February 2014 - 07:57 AM

#7
Posted 01 February 2014 - 08:26 AM


Do not zip but upload the file to http://www.mediafire.com/ and then post the download link here.
How to use mediafire http://en.kioskea.ne...es-to-mediafire
Two things that I have noticed in the Speccy results are 1: that you have Norton AV, if this is the free/trial version I suggest that you uninstall it as it is a hog on system resources and it is known to cause a catalogue of problems, you must use the Norton removal tool to get rid of all traces of Norton, details here, once Norton is uninstalled check that Windows Defender has auto enabled, in Windows 8 Defender is the equivalent of Microsoft Security Essentials so you do not need a third party anti virus software. 2: you only have 9% of free storage space available on the D: drive/partition, this can lead to data corruption and cause system instability, can I ask what type of data is stored on the D: drive and if when you are accessing the D: drive the problems that you are having occur.
To see if we can identify any driver conflicts;
1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7/8 - START | type create | select "Create a Restore Point"
2. Run the Driver Verifier -
Go to START | type verifier | make these selections -
1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot*** IMPORTANT - PLEASE READ:
- If the Driver Verifier (DV) finds a violation, it will result in a BSOD
- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1
- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot
- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use
If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
Tip
Please be patient and give me a chance to reply before you post again, none of us can be here 24/7 as we have other responsibilities such as family and employment, unfortunately both take priority over the free help we provide here.
#8
Posted 01 February 2014 - 09:13 AM

https://www.mediafir...o0adky72vhntff7
https://www.mediafir...hdmvz5wwayb4sk8
#9
Posted 01 February 2014 - 09:15 AM

#10
Posted 01 February 2014 - 09:32 AM

#11
Posted 01 February 2014 - 09:58 AM


If you have something to add while waiting for a reply use the edit tab – bottom right of the dialogue input box and this will ensure that no information that you provide is overlooked (this can happen if your topic has more than one page) thank you for understanding.
Both crashes do indeed involve the Norton AV software as I have highlighted below, as you can see the logs are rather large but if you would like me to post the earlier dump file I will be happy to do so.
We may also need to check out the ATI Radeon HD 8670M drivers as the earlier crash dump shows the cause to be FAILURE_BUCKET_ID: X64_AV_atikmdag+36436 hopefully removing Norton completely will resolve the conflict/s.
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff801`09003000 PsLoadedModuleList = 0xfffff801`092c7990
Debug session time: Thu Jan 30 20:17:51.088 2014 (UTC - 5:00)
System Uptime: 0 days 3:32:11.909
*******************************************************************************
* *
* 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: ffffd0002057d000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80001082fb0, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
READ_ADDRESS: fffff801092b5340: Unable to get special pool info
fffff801092b5340: Unable to get special pool info
GetUlongFromAddress: unable to read from fffff80109350208
ffffd0002057d000
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!InetInspectReceiveDatagram+2b0
fffff800`01082fb0 8b00 mov eax,dword ptr [rax]
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: System
TRAP_FRAME: ffffd00020477d50 -- (.trap 0xffffd00020477d50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd0002057d000 rbx=0000000000000000 rcx=ffffe00005e2c550
rdx=000000000000000d rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001082fb0 rsp=ffffd00020477ee0 rbp=000000000000f7ed
r8=0000000000000000 r9=0000000000000000 r10=ffffd0002057d000
r11=ffffd000204777f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
tcpip!InetInspectReceiveDatagram+0x2b0:
fffff800`01082fb0 8b00 mov eax,dword ptr [rax] ds:ffffd000`2057d000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8010915c7e9 to fffff80109150ca0
STACK_TEXT:
ffffd000`20477c08 fffff801`0915c7e9 : 00000000`0000000a ffffd000`2057d000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20477c10 fffff801`0915b03a : 00000000`00000000 00000000`00000003 00000000`00000000 ffffd000`20477d50 : nt!KiBugCheckDispatch+0x69
ffffd000`20477d50 fffff800`01082fb0 : ffffd000`20478430 fffff800`0120c180 ffffe000`1f6b6940 00000000`00000000 : nt!KiPageFault+0x23a
ffffd000`20477ee0 fffff800`0106f88f : ffffe000`060079d0 00000000`00000000 fffff800`0120c180 ffffe000`06e7a140 : tcpip!InetInspectReceiveDatagram+0x2b0
ffffd000`20478010 fffff800`0106f42e : 00000000`00000000 00000000`00000001 ffffe000`05350970 00000000`00000002 : tcpip!UdpBeginMessageIndication+0x7f
ffffd000`204781b0 fffff800`0107e48d : ffffe000`05350900 00000000`00000000 ffffd000`00000018 ffffd000`204783d0 : tcpip!UdpDeliverDatagrams+0xee
ffffd000`20478350 fffff800`0106e9bf : ffffe000`0132b9c0 ffffd000`20478a19 ffffd000`204789c8 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x223
ffffd000`204787f0 fffff800`0106ecc3 : 00000000`00000000 00000012`ffffffff ffffe000`07ecd1a1 00000000`36286078 : tcpip!IppDeliverListToProtocol+0x4f
ffffd000`204788b0 fffff800`0107f13c : 00000000`00000011 fffff800`0120c180 00000000`00000000 ffffd000`204789b8 : tcpip!IppProcessDeliverList+0x63
ffffd000`20478950 fffff800`0107c3da : 00000000`00000000 ffffe000`05e2c550 ffffe000`0134c000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x1fc
ffffd000`20478a80 fffff800`0107bb3c : ffffe000`06006650 00000000`00000000 ffffd000`20478e01 00000000`6e706600 : tcpip!IppFlcReceivePacketsCore+0x68a
ffffd000`20478e00 fffff800`0107b7d5 : ffffe000`06000002 00000000`00000000 fffff800`0107afa0 00000000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x31c
ffffd000`20478ee0 fffff801`090bb3f9 : 00000000`c0000017 00000000`00000000 ffffe000`01304710 ffffd000`20474000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x155
ffffd000`20479010 fffff800`0107af56 : fffff800`0107b680 ffffd000`20479190 ffffe000`06039c10 ffffd000`204791f0 : nt!KeExpandKernelStackAndCalloutInternal+0xe9
ffffd000`20479160 fffff800`00ea2cde : 00000000`00000000 ffffd000`20479241 00000000`00000001 fffff800`00895f65 : tcpip!FlReceiveNetBufferListChain+0xb6
ffffd000`204791e0 fffff800`00eb17f8 : 00000000`00000002 00000000`00000001 00000000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x11e
ffffd000`204792a0 fffff800`00ea3cd5 : ffffe000`051451a0 ffffd000`20469a01 00000000`00000000 fffff800`00821157 : ndis!ndisMTopReceiveNetBufferLists+0x228
ffffd000`20479330 fffff800`02c85a55 : ffffe000`4784017e ffffe000`055d0000 ffffd000`20479800 ffffe000`00000001 : ndis!NdisMIndicateReceiveNetBufferLists+0xba5
ffffd000`20479520 ffffe000`4784017e : ffffe000`055d0000 ffffd000`20479800 ffffe000`00000001 00000000`00000001 : Rt630x64+0x1ba55
ffffd000`20479528 ffffe000`055d0000 : ffffd000`20479800 ffffe000`00000001 00000000`00000001 00000000`40200300 : 0xffffe000`4784017e
ffffd000`20479530 ffffd000`20479800 : ffffe000`00000001 00000000`00000001 00000000`40200300 80000000`01000002 : 0xffffe000`055d0000
ffffd000`20479538 ffffe000`00000001 : 00000000`00000001 00000000`40200300 80000000`01000002 00000001`00000020 : 0xffffd000`20479800
ffffd000`20479540 00000000`00000001 : 00000000`40200300 80000000`01000002 00000001`00000020 00000001`00000000 : 0xffffe000`00000001
ffffd000`20479548 00000000`40200300 : 80000000`01000002 00000001`00000020 00000001`00000000 05e2c600`00000000 : 0x1
ffffd000`20479550 80000000`01000002 : 00000001`00000020 00000001`00000000 05e2c600`00000000 00000020`00000001 : 0x40200300
ffffd000`20479558 00000001`00000020 : 00000001`00000000 05e2c600`00000000 00000020`00000001 00000400`00000010 : 0x80000000`01000002
ffffd000`20479560 00000001`00000000 : 05e2c600`00000000 00000020`00000001 00000400`00000010 ffffd000`00000001 : 0x1`00000020
ffffd000`20479568 05e2c600`00000000 : 00000020`00000001 00000400`00000010 ffffd000`00000001 ffffe000`05e2c550 : 0x1`00000000
ffffd000`20479570 00000020`00000001 : 00000400`00000010 ffffd000`00000001 ffffe000`05e2c550 00000000`00000000 : 0x5e2c600`00000000
ffffd000`20479578 00000400`00000010 : ffffd000`00000001 ffffe000`05e2c550 00000000`00000000 ffffd000`204797c0 : 0x20`00000001
ffffd000`20479580 ffffd000`00000001 : ffffe000`05e2c550 00000000`00000000 ffffd000`204797c0 00000000`00000000 : 0x400`00000010
ffffd000`20479588 ffffe000`05e2c550 : 00000000`00000000 ffffd000`204797c0 00000000`00000000 ffffe000`05e2c550 : 0xffffd000`00000001
ffffd000`20479590 00000000`00000000 : ffffd000`204797c0 00000000`00000000 ffffe000`05e2c550 00000000`00000001 : 0xffffe000`05e2c550
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt630x64+1ba55
fffff800`02c85a55 ?? ???
SYMBOL_STACK_INDEX: 12
SYMBOL_NAME: Rt630x64+1ba55
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt630x64
IMAGE_NAME: Rt630x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50890312
FAILURE_BUCKET_ID: X64_AV_Rt630x64+1ba55
BUCKET_ID: X64_AV_Rt630x64+1ba55
Followup: MachineOwner
#12
Posted 01 February 2014 - 10:05 AM

#13
Posted 01 February 2014 - 10:37 AM

I am far too polite to even consider such a thinghehe im such a bimbo sometimes,

Any further problems that are in any way associated with the computers earlier unstable behavior feel free to come back to this topic and we will take another look.
Can I just confirm the following please;
That you uninstalled Norton using the Norton removal tool.
That you checked that Windows Defender had auto enabled, to check this go to Start > Control Panel > System and Security > Action Centre > check that and/or turn on all security settings and that internet security settings show as being ok.
That you have enabled Driver Verifier and have not had any crashes up to now.
If the three items above are all correct then I suggest that you use the computer as you normally would and see how the computer behaves, if there are no problems within say the next 24 hours let us know, we can then disable Driver Verifier and I will provide information as to how you can improve the performance and efficiency of your computer.
You are welcome btw matvey

Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






