Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random Frequent BSOD. Help? Free cookies!


  • Please log in to reply
23 replies to this topic

#1 PCLoadLetter

PCLoadLetter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 04 May 2014 - 09:41 AM

Hey folks. First, I appreciate everyone's efforts here as I've resolved a number of PC issues over the years thanks to other users issues and solutions given here. I've done my best to solve my issue without posting, but this appears to be above my abilities. This issue is crippling my productivity and I'd be eternally grateful for help. 

 

Let's get into it.

 

So, for the past month or so I've been getting random BSODs many times a day. It appears to be either a driver issue or RAM modules are kicking the bucket. I cannot pinpoint the cause and have tried *almost* all I can think of. I just spent nearly 15 minutes writing this post only for my PC to crash and lose all progress, so I'm now resorting to copying to a notepad and saving every few sentences in an attempt to preserve my sanity; or at least what's left of it.

 

Details and what I've done so far:

The problem PC is an AsusG75VW-BBK (aka, BestBuy model) running Window 7 Home Premium, but you'll see that all in the Speccy below. I'm BSODing many times per day and it's seemingly random. WhoCrashed shows I've accumulated 40 or so Dump files. I can be surfing the web, designing in Illustrator, watching a tube video, or simply editing an excel document with nothing else running, and it will just blue screen.

 

-The problem also occurs in Safemode with networking, and regular Safemode. Initial safemode attempt it BSOD'd the second the desktop came up.

-All drivers are up to date.

-I've run MalwareBytes and Spybot, everything was clean.

-Antivirus is Webroot and it's up to date and scans are clean.

-WhoCrashed was pointing to a webroot driver as the culprit and I uninstalled Webroot, installed MSE, yet the problem still occurred, so I put Webroot back on.

-Nvidia drivers were updated a couple of weeks into the problem first occurring and it's still occurring after update so I don't think it's a Nvidia driver issue, but who knows.

-I ran Furmark to stress test the graphics; no problems there.

-Fans are working and internal temp is also not the issue.

 

What I haven't done yet:

I have had MemTest86 sitting on my desktop begging to be run but I have not gotten to it yet. I also attempted to physically test the RAM by removing each at a time, but the factory RAM is not easily accessible and requires dismantling the chassis. I was hoping someone here might notice something I missed before I pull it apart, but I will if there is nothing else suggested.

 

WhoCrashed also pointed at the network adapter, but I've not pursued that.

 

I've tried stressing the machine in various ways to produce a BSOD, to no avail. I can't reproduce it when trying and then shortly after I've given up trying, I'll be typing up a post on a help forum hoping someone out there smarter than me can help out and BAM!, BSOD. Do not pass go, do not collect $200. 

 

I'm out of ideas here and would appreciate any input. I'll wait a bit to see if anyone is on here on this Sunday morning and then I'll run Memtest86 throughout the day and report back tonight. Below is some relevant information.

 

Dump file is 665MB. Can provide upon request if necessary. Not sure if the below info gives you enough to work with.

 

Speccy:

http://speccy.piriform.com/results/86pAvZFG75OlkyVNQbSTGzp

 

WhoCrashed:

System Information (local)

computer name: CHRIS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: G75VW, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel® Core™ i7-3610QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8547905536 total
VM: 2147352576, free: 1916596224


 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 5/4/2014 1:39:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050414-23696-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x96604)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000096604, 0xFFFFF8800B632C00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 5/4/2014 1:39:37 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!XLATEOBJ_iXlate+0xB454)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000096604, 0xFFFFF8800B632C00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 5/3/2014 9:00:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-18595-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A991338, 0xFFFFF8800A990B90, 0xFFFFF88001964589)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 5/3/2014 7:49:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-17737-01.dmp
This was probably caused by the following module: athrx.sys (0xFFFFF880050E22AC)
Bugcheck code: 0xD1 (0x80, 0x2, 0x0, 0xFFFFF880050E22AC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
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: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 5/3/2014 7:34:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-18922-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x61940, 0x2952000, 0x3232B4800000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
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 that cannot be identified at this time.



On Sat 5/3/2014 6:16:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-17893-01.dmp
This was probably caused by the following module: acpi.sys (0xFFFFF88000FA1977)
Bugcheck code: 0x50 (0xFFFFFA807909E058, 0x0, 0xFFFFF88000FA1977, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\acpi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ACPI Driver for NT
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 5/3/2014 5:34:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-21996-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960000E7811)
Bugcheck code: 0x50 (0xFFFFF90000B9585C, 0x0, 0xFFFFF960000E7811, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 5/3/2014 3:29:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050314-19250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x130006, 0x2, 0x127385)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.



On Thu 5/1/2014 2:56:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050114-22354-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0xAF0000E, 0x2, 0x0, 0xFFFFF800039AAB05)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 that cannot be identified at this time.



On Thu 5/1/2014 2:25:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050114-21606-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800BF1EB30, 0xFFFFFA800BF1EE10, 0xFFFFF80003B7A7B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


 

Conclusion

43 crash dumps have been found and analyzed. Only 10 are included in this report. 2 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:

wrkrn.sys (Webroot SecureAnywhere, Webroot)
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
 

 

BlueScreen View
 

050414-23696-01.dmp 5/4/2014 9:39:37 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`00096604 fffff880`0b632c00 00000000`00000000 win32k.sys win32k.sys+96604 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050414-23696-01.dmp 8 15 7601 291,528 5/4/2014 9:40:39 AM
 
050314-18595-01.dmp 5/3/2014 5:00:00 PM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`0a991338 fffff880`0a990b90 fffff880`01964589 Ntfs.sys Ntfs.sys+115589 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050314-18595-01.dmp 8 15 7601 291,528 5/3/2014 5:00:56 PM
 
050314-17737-01.dmp 5/3/2014 3:49:34 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`00000080 00000000`00000002 00000000`00000000 fffff880`050e22ac athrx.sys athrx.sys+272ac x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050314-17737-01.dmp 8 15 7601 291,560 5/3/2014 3:50:25 PM
 
050314-18922-01.dmp 5/3/2014 3:34:06 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00061940 00000000`02952000 03232b48`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050314-18922-01.dmp 8 15 7601 291,536 5/3/2014 3:35:01 PM
 
050314-17893-01.dmp 5/3/2014 2:16:31 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa80`7909e058 00000000`00000000 fffff880`00fa1977 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050314-17893-01.dmp 8 15 7601 291,544 5/3/2014 2:17:22 PM
 
050314-21996-01.dmp 5/3/2014 1:34:53 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff900`00b9585c 00000000`00000000 fffff960`000e7811 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050314-21996-01.dmp 8 15 7601 295,944 5/3/2014 1:37:17 PM
 
050314-19250-01.dmp 5/3/2014 11:29:42 AM PFN_LIST_CORRUPT 0x0000004e 00000000`00000099 00000000`00130006 00000000`00000002 00000000`00127385 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050314-19250-01.dmp 8 15 7601 291,536 5/3/2014 11:30:43 AM
 
050114-22354-01.dmp 5/1/2014 10:56:49 AM DRIVER_CORRUPTED_EXPOOL 0x000000c5 00000000`0af0000e 00000000`00000002 00000000`00000000 fffff800`039aab05 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050114-22354-01.dmp 8 15 7601 291,160 5/1/2014 10:58:15 AM
 
050114-21606-01.dmp 5/1/2014 10:25:21 AM CRITICAL_OBJECT_TERMINATION 0x000000f4 00000000`00000003 fffffa80`0bf1eb30 fffffa80`0bf1ee10 fffff800`03b7a7b0 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\050114-21606-01.dmp 8 15 7601 291,592 5/1/2014 10:26:17 AM
 
042714-20966-01.dmp 4/27/2014 2:04:54 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`0010a7bd 00000000`00000002 00000000`00000000 fffff800`0388025b ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042714-20966-01.dmp 8 15 7601 291,592 4/27/2014 2:05:52 AM
 
042614-19375-01.dmp 4/26/2014 10:55:24 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`06000000 00000000`00000002 00000000`00000001 fffff800`038f4622 NETIO.SYS NETIO.SYS+4510 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042614-19375-01.dmp 8 15 7601 291,624 4/26/2014 10:56:17 AM
 
042614-43883-01.dmp 4/26/2014 9:25:16 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041284 00000000`158cb001 00000000`0000b18f fffff700`01080000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042614-43883-01.dmp 8 15 7601 291,592 4/26/2014 9:26:47 AM
 
042514-19032-01.dmp 4/25/2014 7:28:57 AM CACHE_MANAGER 0x00000034 00000000`00050853 fffff880`0b4d8278 fffff880`0b4d7ad0 fffff880`010b0468 fltmgr.sys fltmgr.sys+3468 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042514-19032-01.dmp 8 15 7601 291,608 4/25/2014 7:30:19 AM
 
042514-18938-01.dmp 4/24/2014 1:57:29 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffff880`03df9580 00000000`00000002 00000000`00000000 fffff800`038dccfb ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042514-18938-01.dmp 8 15 7601 291,336 4/25/2014 12:37:09 AM
 
042414-100043-01.dmp 4/24/2014 11:34:01 AM ATTEMPTED_WRITE_TO_READONLY_MEMORY 0x000000be fffff880`03008970 00000002`0fa54121 fffff880`03258730 00000000`0000000b vwififlt.sys vwififlt.sys+8970 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-100043-01.dmp 8 15 7601 291,248 4/24/2014 11:36:45 AM
 
042414-102149-01.dmp 4/24/2014 11:31:22 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 fffff680`0002fb40 c2600001`b9a37867 fffff680`000399f0 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-102149-01.dmp 8 15 7601 270,880 4/24/2014 11:33:39 AM
 
042414-37097-01.dmp 4/24/2014 11:26:45 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a fffffa80`02c34760 00000000`00000002 00000000`00000001 fffff800`03103150 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-37097-01.dmp 8 15 7601 291,272 4/24/2014 11:29:56 AM
 
042414-35661-01.dmp 4/24/2014 11:18:50 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00001236 fffffa80`0a98ec50 fffffa80`0a98ecf8 00000000`001c4890 rdyboost.sys rdyboost.sys+7243 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-35661-01.dmp 8 15 7601 270,936 4/24/2014 11:20:09 AM
 
042414-39171-01.dmp 4/24/2014 11:10:36 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000048 00000000`00000002 00000000`00000001 fffff800`03137c9f athrx.sys athrx.sys+149962 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-39171-01.dmp 8 15 7601 291,232 4/24/2014 11:12:01 AM
042414-38407-01.dmp 4/24/2014 11:08:24 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`03754798 fffff880`03753ff0 fffff880`018b1e27 Ntfs.sys Ntfs.sys+9be27 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-38407-01.dmp 8 15 7601 291,648 4/24/2014 11:10:08 AM
042414-16738-01.dmp 4/24/2014 10:57:22 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff680`000e1200 f6100000`5e00b867 fffffa80`0c13e160 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-16738-01.dmp 8 15 7601 291,400 4/24/2014 10:58:41 AM
 
042414-29499-01.dmp 4/24/2014 10:51:01 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00000031 fffffa80`06e350f0 fffff880`0caed000 fffff8a0`0e02facb ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042414-29499-01.dmp 8 15 7601 291,648 4/24/2014 10:52:43 AM
 
042214-18938-01.dmp 4/22/2014 3:02:24 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041287 fffff700`01080060 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042214-18938-01.dmp 8 15 7601 291,400 4/22/2014 3:03:41 PM
 
042214-22479-01.dmp 4/22/2014 2:59:50 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff8a0`0286faa0 00000000`00000000 fffff880`01171cf0 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042214-22479-01.dmp 8 15 7601 291,648 4/22/2014 3:01:14 PM
 
042214-50934-01.dmp 4/22/2014 1:14:26 PM BAD_POOL_CALLER 0x000000c2 00000000`00000007 00000000`0000109b 00000000`00000000 fffffa80`07bd0700 rdyboost.sys rdyboost.sys+917b x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042214-50934-01.dmp 8 15 7601 291,616 4/22/2014 1:15:59 PM
 
042114-18766-01.dmp 4/21/2014 11:19:46 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`500001ec 00000000`00000002 00000000`00000001 fffff800`0310230e ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042114-18766-01.dmp 8 15 7601 291,608 4/21/2014 11:20:42 PM
 
042114-21668-01.dmp 4/21/2014 10:46:33 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`033d6080 fffff880`0bc6dcc0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042114-21668-01.dmp 8 15 7601 291,320 4/21/2014 10:49:05 AM
 
042114-41121-01.dmp 4/21/2014 9:16:05 AM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 fffff800`03110437 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042114-41121-01.dmp 8 15 7601 295,920 4/21/2014 9:17:54 AM
 
042014-27690-01.dmp 4/20/2014 12:40:55 AM BAD_POOL_HEADER 0x00000019 00000000`00000003 fffffa80`0d8c2290 fffffa80`0d8c2290 fffffa80`0d2d2290 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\042014-27690-01.dmp 8 15 7601 291,616 4/20/2014 12:42:04 AM
 
041114-24585-01.dmp 4/11/2014 1:59:46 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000007 00000000`00000002 00000000`00000001 fffff800`036b1f05 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\041114-24585-01.dmp 8 15 7601 291,648 4/11/2014 2:00:44 PM
 
033014-28579-01.dmp 3/30/2014 12:01:40 PM CACHE_MANAGER 0x00000034 00000000`00050853 fffff880`0373f3c8 fffff880`0373ec20 fffff800`030a5a6d ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\033014-28579-01.dmp 8 15 7601 291,616 3/30/2014 12:03:48 PM
 
032814-43259-01.dmp 3/28/2014 4:31:25 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff700`ff080020 00000000`00000000 fffff800`030dd7be 00000000`00000005 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\032814-43259-01.dmp 8 15 7601 291,608 3/28/2014 4:33:16 AM
 
032814-47751-01.dmp 3/28/2014 3:35:10 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`0309ca6d fffff880`0d240780 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\032814-47751-01.dmp 8 15 7601 291,152 3/28/2014 3:36:35 AM
 
032814-37471-01.dmp 3/28/2014 3:29:00 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`00ee308d fffff880`0c8cfd90 00000000`00000000 Wdf01000.sys Wdf01000.sys+1208d x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\032814-37471-01.dmp 8 15 7601 291,608 3/28/2014 3:30:20 AM
 
032814-59046-01.dmp 3/28/2014 3:12:38 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`06004490 00000000`00000002 00000000`00000001 fffff800`030de43f ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\032814-59046-01.dmp 8 15 7601 291,600 3/28/2014 3:14:24 AM
 
032814-51027-01.dmp 3/28/2014 12:27:37 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 NDIS.SYS NDIS.SYS+64100 x64 ntoskrnl.exe+75b90 C:\Windows\Minidump\032814-51027-01.dmp 8 15 7601 291,632 3/28/2014 12:29:11 AM
 
032714-61433-01.dmp 3/27/2014 11:37:52 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000088 00000000`00000002 00000000`00000001 fffff800`03047bfb ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\032714-61433-01.dmp 8 15 7601 291,632 3/27/2014 11:39:37 PM
 
032714-29530-01.dmp 3/27/2014 10:56:54 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`2375f010 00000000`00000002 00000000`00000000 fffff800`036ba30f ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\032714-29530-01.dmp 8 15 7601 291,624 3/27/2014 10:58:02 PM
 
031814-46956-01.dmp 3/18/2014 2:28:00 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`014a7cf0 fffff880`0a8126e0 00000000`00000000 WRkrn.sys WRkrn.sys+bcf0 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\031814-46956-01.dmp 8 15 7601 291,648 3/18/2014 2:29:34 PM
 
031414-27658-01.dmp 3/14/2014 2:39:17 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041201 fffff683`ff7f8840 79600001`9e5f1005 fffffa80`0cfee7f0 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\031414-27658-01.dmp 8 15 7601 291,624 3/14/2014 2:40:32 PM
031414-64709-01.dmp 3/14/2014 1:17:38 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00000403 fffff680`00012158 d3300001`d4821847 fffff680`00002158 SynTP.sys SynTP.sys+4ec4d x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\031414-64709-01.dmp 8 15 7601 291,600 3/14/2014 1:20:21 AM

Edited by PCLoadLetter, 04 May 2014 - 11:28 PM.


BC AdBot (Login to Remove)

 


#2 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 04 May 2014 - 02:40 PM

Hello! Very impressive! Seems to me you have it figured out. I didn't see any place that you memtioned a clean boot. You might have a driver conflict.

http://support.microsoft.com/kb/929135



#3 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 04 May 2014 - 11:08 PM

Hello! Very impressive! Seems to me you have it figured out. I didn't see any place that you memtioned a clean boot. You might have a driver conflict.

http://support.microsoft.com/kb/929135

 

Well, thanks. I tried to cover as many bases as I could before seeking help to make this as quick and painless for you all.  I wouldn't say I've figured it out, but I think I've narrowed it down as best I could.  I did not get a chance to run Memtest today as planned. I'll try to run it overnight if you think it's necessary. I took your advise and I'm currently in a clean boot right now; I had not tried that before, thanks for the tip! I've only just clean booted a minute ago so I'm going to see if I can do a bunch of my normal activities over the next hour or so and see if it crashes. It never makes it more than 30mins of use before crashing, so we should have a result rather quickly. 

 

I do agree the problem is likely a driver issue, though I hadn't installed or updated any programs within 3 weeks of when the BSODs began occurring, which is why it's alluded me. I would have uninstalled whatever was last installed, but the last program was a google drive update 3 weeks before which I'd really, really rather not uninstall and if it were the cause I'd think the issue would have occurred much sooner.  It's possible the system or piece of software auto-updated their own driver without my knowledge and caused a conflict, I suppose. This laptop is only about a year old, so the chances the RAM is bad are pretty slim, though certainly not out of the question. 

 

If the clean boot I'm in leaves me BSOD free, how might I go about tracking down the specific culprit?

 

Thank you for taking the time to help out.



#4 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 04 May 2014 - 11:23 PM

I did forget to mention the other errors I was receiving. Sometimes they occur shortly before a BSOD, sometimes the BSOD occurs without any errors occurring prior. 

 

Each of these throw a popup error notification on the screen.

-I've had "Windows Manger" stop working a few times which changes the theme of my windows. 

-I've had my Synaptics touchpad stop working which typically results in the touchpad still working, but multi-touch gestures such as two-finger scrolling won't work.

-Can't recall others but these two happen often.

 

Not to muddy the waters here, but I've also noticed my monitor doing strange things such as when I change a tab in Chrome, my display goes slightly dimmer and then immediately and quickly fades up to the previous brightness. Does not happen often though. I suspect it has something to do with the windows manger shutting down and changing my theme, so probably a secondary issue.



#5 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 04 May 2014 - 11:42 PM

Hello! I'm a newbie to the computer world, but try to pass forward things I have learned. Type "Reliability in search" This just might give you a clue to what's going on.

http://support.microsoft.com/kb/929135

 

http://windows.microsoft.com/en-us/windows7/how-to-use-reliability-monitor

 

http://support.microsoft.com/kb/331796


Edited by donetao, 04 May 2014 - 11:52 PM.


#6 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 04 May 2014 - 11:46 PM

Here's my Reliability monitor!

Attached Files



#7 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 05 May 2014 - 12:03 AM

2i6o2t4.png

 

Mine is....worse, to say the least. Haha. Interesting thing I noticed by viewing it though.... There was a Window 7 update the day everything started going downhill. Hmmm.



#8 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 05 May 2014 - 12:15 AM

Nearly an hour since clean boot.... no BSOD. Looking good so far but I'll give it another hour before being 100% confident it's a driver and not a RAM issue. 

 

So, Any idea how I go about finding the exact driver causing the conflict?



#9 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 05 May 2014 - 12:23 AM

I searched on BC for this software. I could not find it here. You might give it a try. It claims to to do a lot??

http://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html

Have you tried finding the conflict??

http://support.microsoft.com/kb/331796

Please read the link above. I think you are about there.


Edited by donetao, 05 May 2014 - 12:26 AM.


#10 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 05 May 2014 - 12:33 AM

I searched on BC for this software. I could not find it here. You might give it a try. It claims to to do a lot??

http://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html

Have you tried finding the conflict??

http://support.microsoft.com/kb/331796

Please read the link above. I think you are about there.

 

Ahhh, I see now. Had a lapse in logic there. I'll start going through the clean boot process enabling some of the services at a time until the BSOD rears it's head.

 

Also, WhoCrashed log is already included in my first post. It's a useful tool, but I'm not sure I can trust it's results because it's given rather broad range of causes. IT doesn't really help to definitively pinpoint the issue. I'll get started of enabling some services and see what happens



#11 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 05 May 2014 - 12:38 AM

Hello! Ok Good for you. I'm curious about reliability monitor. Did you chack it to see if it might have a clue about the BSOD?? I agree about WhoCrashed. It's just another tool I use. There are a lot of things that cause BSOD. It's tough to find the cause, but I think your're about there!!


Edited by donetao, 05 May 2014 - 12:44 AM.


#12 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 05 May 2014 - 01:01 AM

Once again the program I use is not listed here at BC. Not sure if the forum approves, but I use Slimdrivers. You need to be careful up dating drivers. My opinion is if it isn't broke, don't fix it :bananas:

http://www.majorgeeks.com/files/details/slimdrivers.html

 

Trying to be careful with posting down loads.


Edited by donetao, 05 May 2014 - 01:03 AM.


#13 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 05 May 2014 - 01:39 AM

Well, I decided to run MemTest anyway ( didn't realize It came with an exe and I didn't have to burn it and boot with it)  and to my surprise it immediately started listing errors. It's up to 104 errors now. Apparently I've got a bad RAM module afterall. I guess I'll be tearing this thing apart to replace RAM. Time to check my warranty. Bad RAM after 1 year is crazy. 



#14 donetao

donetao

  • Members
  • 270 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:01 AM

Posted 05 May 2014 - 09:41 AM

Well, I decided to run MemTest anyway ( didn't realize It came with an exe and I didn't have to burn it and boot with it)  and to my surprise it immediately started listing errors. It's up to 104 errors now. Apparently I've got a bad RAM module afterall. I guess I'll be tearing this thing apart to replace RAM. Time to check my warranty. Bad RAM after 1 year is crazy. 

Wow! That's a real bummer. You can also type Memeory test in search, and it will run a test on your RAM. I am not aware of memtest86 exe. Can you provide a link??

Good luck!!



#15 PCLoadLetter

PCLoadLetter
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Local time:04:01 AM

Posted 05 May 2014 - 11:56 AM

 

Well, I decided to run MemTest anyway ( didn't realize It came with an exe and I didn't have to burn it and boot with it)  and to my surprise it immediately started listing errors. It's up to 104 errors now. Apparently I've got a bad RAM module afterall. I guess I'll be tearing this thing apart to replace RAM. Time to check my warranty. Bad RAM after 1 year is crazy. 

Wow! That's a real bummer. You can also type Memeory test in search, and it will run a test on your RAM. I am not aware of memtest86 exe. Can you provide a link??

Good luck!!

 

My mistake, it was not Memtest86 as an exe that I ran. Indeed that is only via bootable as I had previously thought. Apparently I had another memory test software in my repertoire of tools which is an exe. I don't know anything about it but it's located here. I will run Memtest86 just to be sure before I actually order new RAM.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users