Random BSODs playing videos, idling, start up, etc..

[yeffiely]

Hi,

I'm having a few problems with my pc since a few months.
Its getting heavier since a month or two.

I'm getting lots of crashes, mostly randoms.

It can crash while viewing a video (vlc or online browsing), While playing music (foobar), at start up (crashes 30 seconds or more after the whole log on has been done).

Yesterday it has crashed while idling and the internal speakers made continious short small beeps (Happened only once)

Sometimes the video card (GeForce GTS 240) makes lots of noise.

I updated everything i could (video driver), but i havent done the bios.

Thanks a lot!

Is Windows 7 Home Basic
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 2 years and a half
- What is the age of OS installation (have you re-installed the OS?) 2 years and a half

 

[yeffiely]

Here's an update of my minidump.

I ran driver verifier on all non-microsoft driver and had crashes at every start up (after all applications loaded).

I had to disable it in safe mode.

Im not too good with all this but HIDCLASS.SYS was comming out of this in the BSODs screen.

Thanks!

 

[writhziden]

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\BSODDmpFiles\yeffiely\Windows_NT6_BSOD_jcgriff2\013012-28891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329c670
Debug session time: Mon Jan 30 10:37:35.308 2012 (GMT-7)
System Uptime: 0 days 0:02:07.369
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff88006f11710, fffff9801f0f4dc0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff88006f11710, The address in the driver's code where the error was detected.
Arg3: fffff9801f0f4dc0, IRP address.
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_23b

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23b

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`06f11710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`06f11710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff9801f0f4dc0

DEVICE_OBJECT: fffffa800ae9f500

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff800032d2b80 -- (!locks fffff800032d2b80)

Resource @ nt!PiEngineLock (0xfffff800032d2b80)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff800032d2b80
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000355d3dc to fffff800030d3c40

STACK_TEXT:  
fffff880`0337e0e8 fffff800`0355d3dc : 00000000`000000c9 00000000`0000023b fffff880`06f11710 fffff980`1f0f4dc0 : nt!KeBugCheckEx
fffff880`0337e0f0 fffff800`0356747a : fffff800`0355b9f0 fffff880`06f11710 fffff980`1f0f4dc0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0337e130 fffff800`03568483 : 00000000`0000023b 00000000`c0000010 fffff980`1f0f4dc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`0337e180 fffff800`03568b42 : fffff980`1f0f4f20 fffff880`06f11710 00000000`00000000 00000000`00000000 : nt!VfErrorReport1+0x63
fffff880`0337e220 fffff800`0355d071 : fffffa80`0aa971c8 00000000`00000001 00000000`00000000 fffff980`1f0f4f20 : nt!ViGenericVerifyIrpStackUpward+0x62
fffff880`0337e250 fffff800`03569b2d : fffffa80`0a6c5610 fffffa80`0aa97010 fffff980`1f0f4dc0 fffff980`1f0f4dc0 : nt!VfMajorVerifyIrpStackUpward+0x91
fffff880`0337e290 fffff800`0357b50d : fffff980`1f0f4f20 fffff880`0337e480 00000000`c0000010 fffff980`1f0f4f20 : nt!IovpCompleteRequest2+0xad
fffff880`0337e300 fffff800`030d7021 : fffff980`1f0f4f23 00000000`00000000 00000000`000000ff fffff800`0355eeea : nt!IovpLocalCompletionRoutine+0x9d
fffff880`0337e360 fffff800`0357319f : fffff980`1f0f4dc0 fffff880`06f1b400 fffffa80`0ae9f600 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`0337e450 fffff800`030b9876 : fffff880`00000013 fffff880`0337e578 fffff980`1f0f4f20 fffffa80`0ae9f650 : nt!IovCompleteRequest+0x19f
fffff880`0337e520 fffff880`06f11a0f : 00000000`00000000 fffffa80`0ae9f650 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`0337e550 fffff880`06f117fb : 00000000`00000000 fffffa80`0ae9f650 fffff980`1f0f4dc0 fffff880`0337e600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`0337e590 fffff800`03579c16 : fffff980`00000002 fffff980`1f0f4dc0 00000000`00000002 fffff800`0357537e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`0337e600 fffff800`03578c42 : fffff980`1f0f4f68 00000000`00000002 fffffa80`0ae9f3f0 fffffa80`0a9cba00 : nt!IovCallDriver+0x566
fffff880`0337e660 fffff800`03579c16 : fffff980`1f0f4dc0 00000000`00000002 fffffa80`0ae9f2a0 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
fffff880`0337e690 fffff800`03578d58 : fffff980`1f0f4dc0 fffffa80`0ae9f2a0 00000000`00000000 fffffa80`0a7514d0 : nt!IovCallDriver+0x566
fffff880`0337e6f0 fffff800`03578e42 : fffffa80`0a571cc0 fffffa80`06d948e0 fffffa80`0a571cc0 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`0337e760 fffff800`03565faf : fffffa80`0aa97d90 00000000`000007ff fffff800`0320d5b8 fffff800`03469899 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`0337e800 fffff800`031809d2 : fffffa80`0aa97d90 00000000`00000000 00000000`00000010 00000000`00010282 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`0337e830 fffff800`034bde5c : fffffa80`0aa97d90 fffffa80`06d948e0 00000000`00000001 00000000`00000000 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`0337e860 fffff800`034bfa54 : fffffa80`0aa97d90 fffffa80`0aa97d90 fffffa80`06d948e0 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`0337e950 fffff800`034c0018 : fffff800`032d0500 00000000`00000000 00000000`00000010 fffff800`034bff80 : nt!PipProcessDevNodeTree+0x264
fffff880`0337ebc0 fffff800`031d08e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`0337ec10 fffff800`030de001 : fffff800`031d05c0 fffff800`033ca901 fffffa80`06d7fb00 fffff800`032836a0 : nt!PnpDeviceActionWorker+0x327
fffff880`0337ecb0 fffff800`0336efee : 00000000`00000000 fffffa80`06d7fb60 00000000`00000080 fffffa80`06d59040 : nt!ExpWorkerThread+0x111
fffff880`0337ed40 fffff800`030c55e6 : fffff880`03186180 fffffa80`06d7fb60 fffff880`031910c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0337ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

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

[*]
Loading Dump File [K:\BSODDmpFiles\yeffiely\Windows_NT6_BSOD_jcgriff2\122311-18876-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`0305f670
Debug session time: Fri Dec 23 09:44:28.528 2011 (GMT-7)
System Uptime: 0 days 0:00:50.463
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa8008caa1a0, 80863b3c, fffffa800946dc48}

Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
	using a physical memory address that was not allocated by
	the USBport driver.
Arg2: fffffa8008caa1a0, Device extension pointer of the host controller
Arg3: 0000000080863b3c, PCI Vendor,Product id for the controller
Arg4: fffffa800946dc48, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88004484f7e to fffff80002e96c40

STACK_TEXT:  
fffff880`031aea58 fffff880`04484f7e : 00000000`000000fe 00000000`00000005 fffffa80`08caa1a0 00000000`80863b3c : nt!KeBugCheckEx
fffff880`031aea60 fffff880`0444bfac : 00000000`bd779180 fffffa80`08cab6a0 00000000`00000000 fffffa80`0946ddc0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`031aeaa0 fffff880`0444bb73 : fffffa80`0946dc48 fffffa80`08e18a00 fffffa80`0946ddc0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
fffff880`031aeb30 fffff880`04450d91 : fffffa80`0946dc48 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff880`031aeb70 fffff880`04458e8b : 00000000`00000002 fffffa80`08caa1a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0x41
fffff880`031aebb0 fffff880`0445d9d1 : 00000000`00000040 00000000`00000004 fffffa80`0946da00 fffffa80`08caa050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`031aebe0 fffff880`04469077 : fffffa80`08caa1a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`031aec40 fffff880`04459f89 : fffffa80`08caa050 00000000`00000000 fffffa80`08caaa02 fffffa80`08caaa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`031aeca0 fffff800`02ea20ac : fffff880`03186180 fffffa80`08caaa18 fffffa80`08caaa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`031aecd0 fffff800`02e8e96a : fffff880`03186180 fffff880`031910c0 00000000`00000000 fffff880`04459db0 : nt!KiRetireDpcList+0x1bc
fffff880`031aed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_sMode_PollEndpointSlot+6c
fffff880`0444bfac 4533c9          xor     r9d,r9d

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00

FAILURE_BUCKET_ID:  X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+6c

BUCKET_ID:  X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+6c

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


[/list]

1. HIDCLASS.SYS is usually blamed when an external device (external hard drive, gaming device, mouse, keyboard, etc) is plugged into the computer.
2. Appears to be a usb device that you have plugged in causing the crashes, or possibly a usb device that is lingering on the system.

Disable Driver Verifier. Then start with the steps outlined for http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html and post back when finished.

 

[yeffiely]

Alright, i did uninstall all the faded drivers except for one that just wouldnt disapear, RAS asynch card, under network card (Sorry for the bad term translation since my OS isnt installed in english). I also deleted INFCACHE.1.

Whats next?
Should i try reinstalling my usb drivers or run the driver verifier again?

Thanks a lot for your help.

 

[writhziden]

Install the USB drivers for only the essential items (mouse, keyboard, etc.) and then let it run for a while to test stability. Then install one USB driver at a time, test stability after each, and determine if one of your other devices is causing the crashes.

 

[yeffiely]

Too bad i dont think uninstalling all unused drivers did the thing. I still had a few crashes today. Also, i had a crash each time i tried to run the Windows Performance Index... Also the internal speakers made continious short small beeps again when i tried rebooting.
Thanks!

 

[writhziden]

Alright, I was hoping it was just the USB issue. Short beeps typically mean bad hardware of some kind; you would have to call the vendor to find out what exactly your beeps mean. The number of beeps would be significant. We can do hardware testing with software in Windows if you'd like, but it would be better if you can find out what the beeps signify.



Did you determine which hardware was causing problems?

 

[yeffiely]

Actually i havent had a crash in a week,
I updated my video card and removed OpenOffice quick start up.
Im kinda convinced the problem's the video card.
Thanks

 

[writhziden]

You're welcome. Glad you tracked it down.

 

[yeffiely]

Bad news... I had a run of about two weeks without a single crash. Then i had 3 crashes de same night, then another week without a crash, then i had about like 4 or 5 crashes in 2 days. I really dont know what to do. i uploaded my new BSOD dump if you guys can see anything new in there. Thanks!

 

[writhziden]

Security Software:

sdwinsec.exe	c:\program files (x86)\spybot - search & destroy\sdwinsec.exe	2452	8	200	1380	2012-03-10 16:00	1.0.0.12	1,10 Mo (1*153*368 octets)	2011-01-24 15:02
afwserv.exe	c:\program files\avast software\avast\afwserv.exe	1380	8	200	1380	2012-03-10 16:00	6.0.1367.0	124,21 Ko (127*192 octets)	2012-01-22 21:59
avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1336	8	200	1380	2012-03-10 16:00	6.0.1367.0	43,72 Ko (44*768 octets)	2012-01-22 22:03
avastui.exe	c:\program files\avast software\avast\avastui.exe	1880	8	200	1380	2012-03-10 16:01	6.0.1367.0	3,57 Mo (3*744*552 octets)	2012-01-22 22:03

Possible out of date drivers:

ElbyCDIO	fffff880`042e0000	fffff880`042ea000	Tue Feb 17 10:11:23 2009 (499aefbb)	00016f74		ElbyCDIO.sys
VClone	fffff880`04259000	fffff880`04268000	Fri May 22 17:08:37 2009 (4a173075)	000185ff		VClone.sys
k57nd60a	fffff880`0f000000	fffff880`0f051000	Sat Jun 20 05:34:49 2009 (4a3cc959)	0005682d		k57nd60a.sys
nvBridge	fffff880`0fd9a000	fffff880`0fd9b180	Fri Jun 26 15:22:03 2009 (4a453bfb)	00010f0d		nvBridge.kmd

ElbyCDIO.sys
VClone.sys
k57nd60a.sys
nvBridge.kmd

Loading Dump File [D:\Kingston\BSODDmpFiles\yeffiely\Windows_NT6_BSOD_jcgriff2\030812-20560-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03058000 PsLoadedModuleList = 0xfffff800`0329d670
Debug session time: Thu Mar  8 18:01:43.624 2012 (UTC - 7:00)
System Uptime: 0 days 3:52:46.670
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff70001080000, 5233, 2005232fffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a7fa )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000005233
Arg4: 02005232fffffffe

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


BUGCHECK_STR:  0x1a_5002

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031400e7 to fffff800030d4c40

STACK_TEXT:  
fffff880`055579c8 fffff800`031400e7 : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`00005233 : nt!KeBugCheckEx
fffff880`055579d0 fffff800`030e219e : 00000000`00000001 00000000`0e91f000 fffff880`05557c20 fffff680`000748f8 : nt! ?? ::FNODOBFM::`string'+0x2a7fa
fffff880`05557ac0 fffff800`030d2d6e : 00000000`00000001 00000000`0e91f000 00000000`fffdb001 00000000`000015c8 : nt!MmAccessFault+0x5de
fffff880`05557c20 00000000`6a86df6b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0032ecf4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a86df6b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2a7fa
fffff800`031400e7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2a7fa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2a7fa

BUCKET_ID:  X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+2a7fa

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

Points to memory problems or driver issues. I would remove the Virtual clone software that has outdated drivers to test.

Update the Broadcom drivers and nVidia nForce chipset drivers if you are able to do so.

Also, remove avast! and Spybot. avast! Uninstall Utility | Download aswClear for avast! Removal can be used for uninstalling avast!; Spybot can be removed through Start Menu -> Control Panel -> Uninstall a program. Replace your current security setup with the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 This free combination should provide similar security to your previous setup.

See how the system responds to the above.

 

[yeffiely]

Thats too bad... I did everything i could and just cant find the answer.

Im getting more crashes, but not much BSOD... Mostly freezes and automatic restarts.

Here's a new dump file. Thanks to whoever may help me out with my problem!

 

[writhziden]

Freezing and automatic restarts indicate hardware issues. So does the latest crash from April 5th. Do some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.