Bsod while playing diablo 3

A

asdd

New member
i have been plagued with bsods while playing diablo 3, i notice my computer starting to run harder then i get a crash sooner or later
it is really starting to anger me

i used the program whocrashed and here is what it says
Code: 
[FONT=Segoe UI, Arial][SIZE=4][B]Crash Dump Analysis[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dump  directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash  dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Fri 8/31/2012 4:24:37 AM GMT your computer  crashed[/B]
crash dump file: C:\Windows\memory.dmp
This was probably  caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_00000000%6000000000.sys"]unknown_module_00000000`00000000.sys[/URL][/COLOR][/SIZE][/FONT]  (Unloaded_Unknown_Module_00000000`00000000+0x6E4F4DB9) 
Bugcheck code: 0x7E  (0xFFFFFFFFC0000005, 0xFFFFF88005BDD3C4, 0xFFFFF880069CA528,  0xFFFFF880069C9D80)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
Bug check  description: This bug check indicates that a system thread generated an  exception that the error handler did not catch.
A third party driver was  identified as the probable root cause of this system error. It is suggested you  look for an update for the following driver:  unknown_module_00000000`00000000.sys . 
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_00000000%6000000000.sys+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"]unknown_module_00000000`00000000.sys  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue 8/28/2012 7:16:15 AM GMT  your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\082812-21949-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_fffff880%6001fa4e50.sys"]unknown_module_fffff880`01fa4e50.sys[/URL][/COLOR][/SIZE][/FONT]  (Unloaded_Unknown_Module_fffff880`01fa4e50+0x2AE39A2) 
Bugcheck code: 0x24  (0x1904FB, 0xFFFFF8800399A1E8, 0xFFFFF88003999A40, 0xFFFFF80002EB64F7)
Error:  [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+NTFS_FILE_SYSTEM"]NTFS_FILE_SYSTEM[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This  indicates a problem occurred in the NTFS file system. 
A third party driver  was identified as the probable root cause of this system error. It is suggested  you look for an update for the following driver:  unknown_module_fffff880`01fa4e50.sys . 
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_fffff880%6001fa4e50.sys+NTFS_FILE_SYSTEM"]unknown_module_fffff880`01fa4e50.sys  NTFS_FILE_SYSTEM[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Mon 8/27/2012 12:31:57 AM GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\082612-25552-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7F1C0) 
Bugcheck code: 0xC5  (0x16800000008, 0x2, 0x0, 0xFFFFF80003010B05)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_CORRUPTED_EXPOOL"]DRIVER_CORRUPTED_EXPOOL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
Bug check description: This indicates that the system attempted to  access invalid memory at a process IRQL that was too high.
This appears to be  a typical software driver bug and is not likely to be caused by a hardware  problem. This might be a case of memory corruption. More often memory corruption  happens because of software errors in buggy drivers, not because of faulty RAM  modules. 
The crash took place in the Windows kernel. Possibly this problem  is caused by another driver which cannot be identified at this time.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sun  8/26/2012 5:59:15 AM GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\082612-26208-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Unknown[/COLOR][/SIZE][/FONT] (0xFFFFF80002E841C0) 
Bugcheck code:  0xD1 (0xFFFFF8800BC69A00, 0x2, 0x8, 0xFFFFF8800BC69A00)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
Bug check description:  This indicates that a kernel-mode driver attempted to access pageable memory at  a process IRQL that was too high.
This appears to be a typical software  driver bug and is not likely to be caused by a hardware problem. 
A third  party driver was identified as the probable root cause of this system error. It  is suggested you look for an update for the following driver: Unknown .  
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Unknown+DRIVER_IRQL_NOT_LESS_OR_EQUAL"]Unknown  DRIVER_IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 8/2/2012 5:21:49 AM GMT  your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\080212-22136-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=asmthub3.sys"]asmthub3.sys[/URL][/COLOR][/SIZE][/FONT] (asmthub3+0x15A2D) 
Bugcheck code:  0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88007DAEA2D, 0xFFFFF8800362E9C8,  0xFFFFF8800362E220)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\asmthub3.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ASMedia%20USB%203.0%20Host%20Drivers"]ASMedia USB 3.0 Host Drivers[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ASMedia%20Technology%20Inc"]ASMedia Technology Inc[/URL][/COLOR][/SIZE][/FONT]
description: ASMedia USB3 Hub  Driver
Bug check description: This indicates that a system thread generated  an exception which the error handler did not catch.
This appears to be a  typical software driver bug and is not likely to be caused by a hardware  problem. 
A third party driver was identified as the probable root cause of  this system error. It is suggested you look for an update for the following  driver: asmthub3.sys (ASMedia USB3 Hub Driver, ASMedia Technology Inc).  
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=asmthub3.sys+ASMedia%20Technology%20Inc+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]asmthub3.sys ASMedia Technology Inc  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed 8/1/2012 6:06:25 AM GMT  your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\080112-21325-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_00000000_00000080.sys"]unknown_module_00000000_00000080.sys[/URL][/COLOR][/SIZE][/FONT]  (Unknown_Module_00000000_00000080+0x2FD79D) 
Bugcheck code: 0x7E  (0xFFFFFFFFC000001D, 0xFFFFF88005B9AB83, 0xFFFFF88006DB2348,  0xFFFFF88006DB1BA0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
Bug check  description: This bug check indicates that a system thread generated an  exception that the error handler did not catch.
A third party driver was  identified as the probable root cause of this system error. It is suggested you  look for an update for the following driver:  unknown_module_00000000_00000080.sys . 
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_00000000_00000080.sys+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"]unknown_module_00000000_00000080.sys  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Mon 7/23/2012 8:16:14 PM GMT  your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\072312-24757-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Unknown[/COLOR][/SIZE][/FONT] (0xFFFFF88004ABD7F2) 
Bugcheck code:  0x3B (0xC0000005, 0xFFFFF88005B2CBF6, 0xFFFFF88009E42D90, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_SERVICE_EXCEPTION"]SYSTEM_SERVICE_EXCEPTION[/URL][/COLOR][/SIZE][/FONT]
Bug check description: This  indicates that an exception happened while executing a routine that transitions  from non-privileged code to privileged code. 
This appears to be a typical  software driver bug and is not likely to be caused by a hardware problem. 
A  third party driver was identified as the probable root cause of this system  error. It is suggested you look for an update for the following driver: Unknown  . 
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Unknown+SYSTEM_SERVICE_EXCEPTION"]Unknown  SYSTEM_SERVICE_EXCEPTION[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue 7/17/2012 7:22:34 AM GMT  your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\071712-22604-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x87CF9) 
Bugcheck code: 0x19  (0x20, 0xFFFFF8A002CD6690, 0xFFFFF8A002CD6E70, 0x947E6921)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+BAD_POOL_HEADER"]BAD_POOL_HEADER[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
Bug check description: This indicates that a pool header is  corrupt.
This appears to be a typical software driver bug and is not likely  to be caused by a hardware problem. This might be a case of memory corruption.  More often memory corruption happens because of software errors in buggy  drivers, not because of faulty RAM modules. 
The crash took place in the  Windows kernel. Possibly this problem is caused by another driver which cannot  be identified at this time. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI, Arial][SIZE=4][B]  Conclusion[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]8 crash dumps  have been found and analyzed. 5 third party drivers have been identified to be  causing system crashes on your computer. It is strongly suggested that you check  for updates for these drivers on their company websites. Click on the links  below to search with Google for updates for these drivers: 

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=asmthub3.sys+ASMedia%20Technology%20Inc+ASMedia%20USB%203.0%20Host%20Drivers"]asmthub3.sys (ASMedia USB3 Hub Driver, ASMedia Technology  Inc)[/URL][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_fffff880%6001fa4e50.sys"]unknown_module_fffff880`01fa4e50.sys [/URL][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_00000000_00000080.sys"]unknown_module_00000000_00000080.sys [/URL][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown"]unknown  [/URL][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=unknown_module_00000000%6000000000.sys"]unknown_module_00000000`00000000.sys [/URL][/COLOR][/SIZE][/FONT]

If no  updates for these drivers are available, try searching with Google on the names  of these drivers in combination the errors that have been reported for these  drivers and include the brand and model name of your computer as well in the  query. This often yields interesting results from discussions from users who  have been experiencing similar problems.
[/COLOR][/SIZE][/FONT]
 

My Computer

OS
windows 7 professional 64 bit

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
i have uploaded the attachment, sorry for the wait
 

My Computer

OS
windows 7 professional 64 bit
► One of your dumps indicate to ASMedia USB 3.0 Hub driver. Well, it is almost one your old, of Sept 2011. Check for possible updated in ASMedia Technology Inc. ????.

► Another one shows pool corruption as the cause. In this situation, I think it is better to enable driver verifier to monitor the drivers:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

► All your other dumps indicate to almost nothing, with different bugchecks. Most possibly that generated due to hardware error. I would suggest you to take a few hardware tests:
1> For RAM:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

2> For CPU:
http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

3> For HDD:

  1. Reseat the sata and power.
  2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
  3. Seatool for dos: SeaTools | Seagate download
    Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Let us know the results!
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
Hello, i recently adjusting the fan on my video card and i seem to be getting a lot less bsod's

i will run these tests right now and respond back to you guys
 

My Computer

OS
windows 7 professional 64 bit
I turned on driver verifier and i get a bsod instantly, here is what whocrashed said:

[FONT=Segoe UI, Arial]On Mon 9/17/2012 8:04:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-20623-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xC4 (0x0, 0x0, 0x1, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver requested a zero-byte pool allocation. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]
 

My Computer

OS
windows 7 professional 64 bit
Upload the crash dump? We need a closer look :)
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
i have uploaded my last 2 minidumps
one from 2 days ago and one from just now
 

My Computer

OS
windows 7 professional 64 bit
Kaspersky.
Code: 
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {0, 0, 1, 0}

Unable to load image \SystemRoot\system32\DRIVERS\klif.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
[COLOR=Red][B]Probably caused by : klif.sys[/B][/COLOR] ( klif+4b584 )

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

As a test, uninstall Kaspersky and use Microsoft Security Essentials - Free Antivirus for Windows, and see if it is causing crashes or not.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
ok i will try this tonight, sorry for the long wait between replies
i was just hesitant to remove the kaspersky but at this point, ill try anything :(
 

My Computer

OS
windows 7 professional 64 bit
ok, ran driver verifier for a few days no errors, thought my bsod problem was finally gone
i turn it off and boom bsods start again lol :mad:

mindumps are attached
no kaspersky installed
Microsoft security installed instead

please help me :cry:

also, i have a question
i have an SSD, when i reinstalled windows i put the paged file on my HDD instead of the SSD because it writes to it too much, do you think this might be the culprit?
 

My Computer

OS
windows 7 professional 64 bit
Mate there is a problem, see it:
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002fce7e0}

Unable to load image Unknown_Module_00000000`000039e9, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`000039e9
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`000039e9
Unknown module 'Unknown_Module_00000000_000039e9' found on stack, using vad to reload module.
!vad_reload -1 0x39e9
Failed to get old VAD root
Unknown module 'Unknown_Module_00000000_000039e9' found on stack, using vad to reload module.
!vad_reload -1 0x39e9
Failed to get old VAD root
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

[COLOR=Red]Probably caused by : Unknown_Image [/COLOR]( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
A stop 0x7F may be caused out of a lot of reasons.
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack (source: Carrona.org)

May I see your MSINFO32 file once again? The latest state?

  1. Click on the start button
  2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
  3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
  4. Give the time for processing, it will save a .nfo file on your desktop.
  5. Zip it, and upload it following the instruction.
Also run Driver Verifier.
Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
ok i uploaded the txt file it created

how about the other minidumps?
one of them was something about usb while the other said something about amd
 

My Computer

OS
windows 7 professional 64 bit
I checked the latest one only. As the latest one gives the information about the latest situation. Dont worry. Just enable driver verifier. Upload a few dumps with verifier on.

Probably those will give it causes, including USB and AMD :)
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
ok ran verifier for the whole day while i did stuff on comp and played d3
crashed just now after 24 hours with verifier on
it said dxgkrnl.sys

dump attached
 

My Computer

OS
windows 7 professional 64 bit
Still it is unknown image.
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {114f30, b, 0, fffff880052445ff}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

[COLOR=Red]Probably caused by : Unknown_Image[/COLOR] ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
Now what we are to do at first is to burn test the CPU

And a stress test of the RAM modules.

Do the tests and let us know the results.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Assembled
OS
Microsoft Windows 10 Pro Insider Preview 64-bit
CPU
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Motherboard
Gigabyte Technology Co., Ltd. B85M-D3H
Memory
Corsair Vengence 4GB x2 (8.00GB Dual-Channel DDR3 @ 798MHz)
Graphics Card(s)
2047MB GeForce GTS 450 (ZOTAC International)
Sound Card
Onboard (Realtek High Definition Audio)
Monitor(s) Displays
LG Flatron E2040T
Screen Resolution
1600x900
Hard Drives
Western Digital 1 TB
Seagate 500 GB
PSU
Corsair VS550
Case
Cooler Master K380
Cooling
Cooler Master Seidon 120V Plus
Keyboard
Logitech MK260r
Mouse
Logitech MK260r
Internet Speed
PMPL Broadband
Antivirus
Windows Defender + MBAM
Browser
Firefox
Other Info
Dell Studio 15" Laptop
You must log in or register to reply here.
Back
Top