Windows 7 Getting Constant BSOD's.

[savithepk]

Hey there guys,

I have recently started getting constant BSOD's, now to the point that I can't even use my computer. It started about a week or two ago, and has constantly gotten worse. I have gotten a variety of different codes. I really need my computer to go back to normal, as I am taking online college classes. If you have time, please help me .

Some of the common Codes:

Memory_Management
Page_fault_in_nonpaged_area
IRQL_not_or_less_equal
Bad_pool_header
service_management
etc..

Here are some dump files that I have


I reinstalled windows. . . .Ran good for 35 minutes, and boom another Blue screen. Last 2 was c2. Bad Pool Caller.

Another EDIT: While running chkdsk, I got another blue screen. It was on stage 4 of the 5 stages. The last two digits were 3B, interrupt exception not handled.

Someone please help ;(

 

[savithepk]

[BSOD] Constant BSOD's

REPEATED - Ignore This

 

[savithepk]

Constant BSOD's

Repeated - IGNORE THIS Link Removed

 

[savithepk]

Constantly getting BSOD's

REPEATED - IGNORE THIS!

 

[kemical]

Re: Constantly getting BSOD's

Threads merged to save confusion.

Please do not double post.

Unfortunately I'm late for a Dr's appointment otherwise I'd check through your dmp files. If it isn't answered by the time I'm back I'll certainly have a look see for you.

 

[usasma]

Re: Constantly getting BSOD's

You cite at least 5 different BSOD error codes (I counted 6 different codes out of 8 memory dumps). Here's my canned speech about differing error codes:

Out of 8 memory dumps there were 6 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).

You can get a head start on the hardware diagnostics if you'd like - they are located here: Link Removed

These other comments of yours are also suggestive of hardware problems:

I reinstalled windows. . . .Ran good for 35 minutes, and boom another Blue screen. Last 2 was c2. Bad Pool Caller.

Another EDIT: While running chkdsk, I got another blue screen. It was on stage 4 of the 5 stages. The last two digits were 3B, interrupt exception not handled.

Please provide this information so we can provide a complete analysis: Link Removed

There are a number of driver issues that could be causing this also - so I'd suggest the following:

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.

Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from Link Removed (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: Link Removed

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Remove HotSpotShield (it is the hssdrv6.sys driver) as it has been known to cause BSOD's on some Windows systems

Your USB 3.0 drivers date from 2009. The 2009 and 2010 versions are known to cause BSOD's - please update to the latest, Win7 compatible version

Kaspersky dates from 2012, please update to the latest available version from the Kaspersky website

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

tsvp.sys Fri Jan 19 05:17:17 2007 (45B09AAD)
CommView Pid Driver
Link Removed

teamviewervpn.sys Thu Dec 13 04:22:09 2007 (4760F9C1)
TeamViewerVPN Network Adapter
Link Removed

tscomm.sys Tue Nov 11 15:56:20 2008 (4919F174)
TamoSoft CommStudio Driver
tscomm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

nusb3hub.sys Fri Nov 20 05:15:57 2009 (4B066C5D)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Link Removed

nusb3xhc.sys Fri Nov 20 05:16:01 2009 (4B066C61)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
Link Removed

If all of this doesn't stop the BSOD's, please run these free hardware diagnostics: Link Removed. Let us know the results and we can move on from there.




Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sun Jul 14 16:50:23.612 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071413-22245-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:04.502[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiUnlinkWaitBlocks+1a )[/B]
BugCheck [B]3B, {c0000005, fffff800034aac5e, fffff88008ee7f10, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800034aac5e, Address of the instruction which caused the bugcheck
Arg3: fffff88008ee7f10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  FlashPlayerPlu
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!KiUnlinkWaitBlocks+1a[/B]
  BIOS Version                  F3
  BIOS Release Date             05/14/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 14 16:28:13.010 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071413-22682-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:50.212[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!RtlpNewSecurityObject+e5f )[/B]
BugCheck [B]19, {20, fffff8a0047d6cf0, fffff8a0047d7080, 5393180}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a0047d6cf0, The pool entry we were looking for within the page.
Arg3: fffff8a0047d7080, The next pool entry.
Arg4: 0000000005393180, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]X64_0x19_20_nt!RtlpNewSecurityObject+e5f[/B]
  BIOS Version                  F3
  BIOS Release Date             05/14/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 14 14:33:44.802 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071413-26192-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:17:55.378[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiUnlinkWaitBlocks+1a )[/B]
BugCheck [B]3B, {c0000005, fffff800040b3c5e, fffff88009f49f10, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800040b3c5e, Address of the instruction which caused the bugcheck
Arg3: fffff88009f49f10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!KiUnlinkWaitBlocks+1a[/B]
  BIOS Version                  F3
  BIOS Release Date             05/14/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 14 01:11:36.316 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071413-17472-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:08:57.892[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PoIdle+1f5 )[/B]
BugCheck [B]50, {fffffa80e120a7c8, 1, fffff800040d63c5, 5}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa80e120a7c8, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800040d63c5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x50_nt!PoIdle+1f5[/B]
  BIOS Version                  F3
  BIOS Release Date             05/14/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 20:17:35.557 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-21481-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:52.447[/B]
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
Probably caused by :[B]ntkrnlmp.exe ( nt!KiPageFault+260 )[/B]
BugCheck [B]A, {1000, 2, 1, fffff80003495b36}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000001000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003495b36, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xA_nt!KiPageFault+260[/B]
  BIOS Version                  F3
  BIOS Release Date             05/14/2010
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 20:15:39.246 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-22230-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:36.822[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6071 )[/B]
BugCheck [B]1A, {411, fffff6fc00021d98, 19c00000043b3860, fffff6fc00021d89}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc00021d98
Arg3: 19c00000043b3860
Arg4: fffff6fc00021d89
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  daemonu.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_411_VRF_nt!_??_::FNODOBFM::_string_+6071[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 12 15:11:06.610 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071213-26644-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:06:41.812[/B]
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by :[B]tcpip.sys ( tcpip+5323d )[/B]
BugCheck [B]D1, {b8, 2, 0, fffff88001e5323d}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001e5323d, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID: [B][COLOR=RED]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_VRF_tcpip+5323d[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 12 13:29:42.332 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071213-26223-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`07cba5b0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`07cba5b0
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:10:57.534[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`07cba5b0
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`07cba5b0
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]50, {fffffa8066fdf2a0, 1, fffff8000389d3c5, 5}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa8066fdf2a0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8000389d3c5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Sun Jul 14 16:50:23.612 2013 (UTC - 4:00)**************************
[COLOR=RED][B]teamviewervpn.sys           Thu Dec 13 04:22:09 2007 (4760F9C1)[/B][/COLOR]
[COLOR=RED][B]tscomm.sys                  Tue Nov 11 15:56:20 2008 (4919F174)[/B][/COLOR]
[COLOR=RED][B]nusb3hub.sys                Fri Nov 20 05:15:57 2009 (4B066C5D)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Fri Nov 20 05:16:01 2009 (4B066C61)[/B][/COLOR]
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
RzSynapse.sys               Wed Apr  6 05:29:13 2011 (4D9C3269)
Rt64win7.sys                Fri Mar 16 09:01:36 2012 (4F6339B0)
usbfilter.sys               Fri Mar 30 23:48:56 2012 (4F767EA8)
AtiPcie64.sys               Tue Jun 12 22:33:31 2012 (4FD7FBFB)
[COLOR=RED][B]hssdrv6.sys                 Wed Apr 24 15:18:16 2013 (51782FF8)[/B][/COLOR]
taphss6.sys                 Wed Apr 24 15:27:25 2013 (5178321D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 14 16:28:13.010 2013 (UTC - 4:00)**************************
[COLOR=RED][B]tsvp.sys                    Fri Jan 19 05:17:17 2007 (45B09AAD)[/B][/COLOR]
RTKVHD64.sys                Tue Dec  8 05:20:05 2009 (4B1E2855)
nvBridge.kmd                Fri Jul  9 17:07:54 2010 (4C378FAA)
Sftvollh.sys                Fri Sep 30 12:42:46 2011 (4E85F186)
Sftplaylh.sys               Fri Sep 30 12:43:05 2011 (4E85F199)
Sftfslh.sys                 Fri Sep 30 12:43:06 2011 (4E85F19A)
[COLOR=RED][B]AODDriver2.sys              Tue Mar  6 04:55:00 2012 (4F55DEF4)[/B][/COLOR]
MpFilter.sys                Wed Oct 31 18:43:06 2012 (5091A97A)
mbam.sys                    Thu Feb 28 15:33:07 2013 (512FBF03)
nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 14 14:33:44.802 2013 (UTC - 4:00)**************************
Sftredirlh.sys              Fri Sep 30 12:43:14 2011 (4E85F1A2)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 20:17:35.557 2013 (UTC - 4:00)**************************
kl1.sys                     Tue Jun 19 09:27:15 2012 (4FE07E33)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 20:15:39.246 2013 (UTC - 4:00)**************************
klim6.sys                   Thu Aug  2 07:09:23 2012 (501A5FE3)
klkbdflt.sys                Mon Sep  3 09:55:35 2012 (5044B6D7)
klmouflt.sys                Mon Sep  3 10:21:58 2012 (5044BD06)
kneps.sys                   Tue Mar  5 04:09:23 2013 (5135B643)
klflt.sys                   Tue Mar 26 10:44:59 2013 (5151B46B)
klif.sys                    Tue Mar 26 11:07:33 2013 (5151B9B5)
kltdi.sys                   Mon Apr 29 08:07:50 2013 (517E6296)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 12 15:11:06.610 2013 (UTC - 4:00)**************************
nvlddmkm.sys                Sun May 12 15:09:45 2013 (518FE8F9)
[/font]

Link Removed
tscomm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[savithepk]

Re: Constantly getting BSOD's

Thank you John so much for your reply! So, my friend says that since it crashed in Chkdsk, the HDD or the Hard drive have to be the problem. Is there a possibility that just updating these drivers will fix the problem? I'm trying not to buy a new HDD or hard drive, as this computer is starting to get old anyways, and would most likely be buying a new computer if I can't get this one fixed.

 

[GeneralHiningII]

Re: Constantly getting BSOD's

A chkdsk fail doesn't always mean it's a HDD problem (usually is, but in rare cases) - it could be possible that chkdsk came upon a bad driver and couldn't move on.
Try using Driver Verifier (verifier.exe, search "Verifier" in Start Menu) and run it until you have a BSOD. Then get the minidump and post it back here.

 

[savithepk]

Re: Constantly getting BSOD's

Thanks for your response GeneralHiningII! I enabled driver verifier, computer ran for about 30 minutes, and just shut off, didn't blue screen, just shut off. Turned back on, got a blue screen, turned back on, blue screen. I'm not sure what logs you want for driver verifier, I youtube'd it, and it doesn't seem to show where the logs go to. The only logs I have on my computer are these. When I activated the verifier, and restarted, I was expecting machine to turn off very quickly, but after 5 minutes of it not turning off, I decided to let it start to install Windows Updates, it was at like 59% when the computer just froze. I manually turned off. Then restarted, and got the blue screens. Ended in 7E.

RECAP OF PROBLEM:
Blue screens constantly, even in Safe Mode.
Reinstalled Windows 7, still blue screens.
Blue screened while running Chkdsk.

 

[usasma]

Re: Constantly getting BSOD's

Please provide this information so we can provide a complete analysis: Link Removed

Also, please do this:

Upload Dump Files:
NOTE: If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service. Then post the link to it in your topic so that we can download it.

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp. Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Link RemovedMore info on dump file options here: Overview of memory dump file options for Windows 2000, Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2

Finally, please run these free diagnostics: Link Removed

 

[savithepk]

Re: Constantly getting BSOD's

Please provide this information so we can provide a complete analysis: Link Removed

Also, please do this:


Finally, please run these free diagnostics: Link Removed

I did provide a minidump.zip. It has most all my minidumps except the ones that have happened since this post. Considering I just reinstalled windows 2 days ago, and don't even start my computer much because I can't play anyways, I've only had about 4 blue screens since. I completed a chkdsk last night, however the information went away too quickly for me to write down. All's I saw was that there were 0 bad sectors. I looked for the logs under event viewer, but wasn't able to find them.

Thanks for responding John

 

[savithepk]

Re: Constantly getting BSOD's

Ignore This

 

[usasma]

Re: Constantly getting BSOD's

There are other reports included in the information that I requested.
Minidumps alone cannot solve all of the problems.

For example, this scenario shows that the culprits might not be in the minidump:

Suppose that a bad driver access' the memory space of a Windows driver and writes info to this space
Then the bad driver exits
Later on the Windows driver looks into that memory space and finds unexpected info
It (the Windows driver) panics and crashes - generating the BSOD and the memory dump
Since the bad driver exited BEFORE the crash, there's no evidence of it in the minidump.

Also, in most cases there's a record of the chkdsk results in the reports that I requested.

 

[savithepk]

Re: Constantly getting BSOD's

A lot of your post is about stuff that happened when I first started this thread. Since then I have reinstalled Windows, so almost all of those outdated drivers don't have any effect because they are no longer on my computer. I just got on my computer, installed the catalyst uninstaller, and uninstalled the stuff the thread you linked told me too, however I got a blue screen and can't even turn my computer on now. When I click the power, everything starts up but there is nothing on the screen. Not sure if this is any more of a help to what the problem is. I'm asking some friends if they have any spare hard drives that I could maybe try, as I don't think its driver related after all the work I've put into it.

As always, Thanks for your response !

There are other reports included in the information that I requested.
Minidumps alone cannot solve all of the problems.

For example, this scenario shows that the culprits might not be in the minidump:


Also, in most cases there's a record of the chkdsk results in the reports that I requested.

 

[usasma]

Re: Constantly getting BSOD's

As you have repeatedly skipped providing the reports that I've asked for, I am unsubscribing from this topic.
Should you decide to provide the reports, feel free to PM me AFTER the reports are posted if you wish to have my continued assistance.