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

Multiples different BSOD while gaming or cpu stress testing


  • Please log in to reply
7 replies to this topic

#1 zorus195

zorus195

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:34 PM

Posted 25 March 2015 - 11:17 PM

Hello everyone,
 
I had recently installed a new HDD, CPU + heat sink and graphic card on my computer and since I experience multiple BSODs while playing games or doing CPU stress tests. The BSOD error code are almost always different has you can see in the attached minidump files (most recent ones). I get BSODs Only while I am gaming or stress testing my cpu. The errors happens generally  when I open my computer and start playing. Then, when I get a BSOD I restart my computer and don't get any BSOD for the rest of my playing session. Then the next day it comes back.
.
The problem doesn't seems to be heat related because my cpu temperatures stays bellow 65 C while stress testing which I think is normal for my processor.
 
SPECS:
- Alienware Aurora R1
- MOBO: Dell Alienware Aurora ALX LGA1366  MS-7591
- OS: Windows 7 64bit
- RAM: 12GB (3x4gb) DDR3 1333Mhz
- GPU: 1.5 GB asus Dcuii GTX 580
- CPU: i7 920 @2.66 Ghz 1.1v (40C idle, 66 C Max) (not overclocked)
- HEATSINK: cooler master hyper vortex plus
- PSU: Alienware stock PSU ( Dell W299G 875W)
- HDD: Seagate Barracuda 1TB 7200RPM (ST1000DM003)
 
Here's a list of the steps I went through since my problem begin:
- Clean re-installing windows 7 OS
- Clean installation of the most recent nvidia drivers (347.52) using driver sweeper
- 7 passes of memtest on each of my memory sticks (no errors)
- Prime95 and OCC stress test (I quickly get BSODs when opening my computer but after the first BSOD prime95 can run for more than 8 hours without any BSOD)
- I tried seatools for windows to look for HDD errors (no errors)
- I have updated to the newest drivers available on dell website (including BIOS).
- Unfortunately I don't have any spare working GPU, CPU or PSU to swap with the current ones to see if it is a hardware related issue :(.
 
I have attached the information coming out from minitoolbox to this post.
 
I am beginning to be out of ideas on how I could find a solution to my problem so any advice would be really appreciated.
 
Thank you very much,
 
ps : Please apologize for my English since I am a french speaker.

Attached Files


Edited by hamluis, 11 April 2015 - 03:10 PM.
Moved from Win 7 to Internal Hardware - Hamluis.


BC AdBot (Login to Remove)

 


m

#2 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:34 PM

Posted 26 March 2015 - 12:21 AM

Hi,

Do you still have Avast Antivirus still installed? 3 of the 4 BSOD logs I checked (most recent ones) reported driver from Avast as the culprit. Uninstall it if you haven't already. Also run the Avast uninstall tool found here It must be run from Safe Mode.

 

 

Unable to load image \SystemRoot\system32\drivers\aswMonFlt.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : aswMonFlt.sys ( aswMonFlt+2351 )
 

 

Highlighted in red belong to Avast.

 

 

STACK_TEXT:  

fffff880`0b2b4658 fffff800`02ed3469 : 00000000`0000000a fffff800`53065a80 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b2b4660 fffff800`02ed20e0 : fffffa80`0a91a010 fffffa80`0a50d7f0 fffffa80`0a50d7f0 fffffa80`0b330000 : nt!KiBugCheckDispatch+0x69
fffff880`0b2b47a0 fffff800`03009783 : 00000000`00000000 00000000`00000000 00000000`0e876500 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0b2b4930 fffff800`02ee5be1 : 00000000`00000000 00000000`00000000 fffff880`0b2b4ae0 00000000`00000000 : nt!ExAllocatePoolWithTag+0x693
fffff880`0b2b4a20 fffff800`031d56cf : 00000000`00000006 00000000`00000006 fffffa80`0a52f548 fffff880`0b2b4be8 : nt!IopAllocateIrpPrivate+0x241
fffff880`0b2b4a80 fffff800`031d1738 : fffffa80`0acf5cd0 fffff800`00000000 fffffa80`0a52f390 fffff8a0`00000000 : nt!IopParseDevice+0xde6
fffff880`0b2b4be0 fffff800`031d2956 : 00000000`00000000 fffffa80`0a52f390 fffffa80`0d588b28 fffffa80`09db93f0 : nt!ObpLookupObjectName+0x588
fffff880`0b2b4cd0 fffff800`031d425c : fffffa80`0af67730 00000000`00000000 fffffa80`0a50d700 fffffa80`0cd4f2c0 : nt!ObOpenObjectByName+0x306
fffff880`0b2b4da0 fffff800`0317c49b : fffffa80`0f9aca98 fffffa80`00100001 fffff880`0b2b4f90 fffff880`0b2b4f60 : nt!IopCreateFile+0x2bc
fffff880`0b2b4e40 fffff880`010f0180 : fffffa80`0f9ac9c0 00000000`00000017 fffffa80`0d06d8b8 00000000`00000000 : nt!IoCreateFileEx+0xfb
fffff880`0b2b4ee0 fffff880`010efbe9 : fffffa80`0d06d8b8 00000000`00000000 00000000`00000017 00000000`000007ff : fltmgr!FltpNormalizeNameFromCache+0x190
fffff880`0b2b5000 fffff880`010f0f81 : fffffa80`00000032 00000000`00000032 00000000`00000029 00000000`00000000 : fltmgr!FltpExpandShortNames+0x239
fffff880`0b2b5060 fffff880`010f0e1e : fffffa80`0f9ac9c0 fffffa80`0aea0000 00000000`00000000 00000000`000007ff : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`0b2b50a0 fffff880`010d24fb : fffffa80`0aeab800 fffffa80`0c7c1d30 fffffa80`0ab89180 fffff880`0b2b6000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`0b2b5100 fffff880`010ddb44 : fffffa80`0d068000 fffffa80`0c7c1d30 fffffa80`0bb34a40 00000000`00000101 : fltmgr!FltpGetFileNameInformation+0x26b
fffff880`0b2b5180 fffff880`02423351 : fffffa80`0f9ac9c0 fffffa80`0b3483f8 00000000`00000000 fffff880`0b2b5408 : fltmgr!FltGetFileNameInformation+0x184
fffff880`0b2b5210 fffffa80`0f9ac9c0 : fffffa80`0b3483f8 00000000`00000000 fffff880`0b2b5408 00000000`0b2b5301 : aswMonFlt+0x2351
fffff880`0b2b5218 fffffa80`0b3483f8 : 00000000`00000000 fffff880`0b2b5408 00000000`0b2b5301 fffffa80`0aeab800 : 0xfffffa80`0f9ac9c0
fffff880`0b2b5220 00000000`00000000 : fffff880`0b2b5408 00000000`0b2b5301 fffffa80`0aeab800 00000000`00000000 : 0xfffffa80`0b3483f8
 
STACK_TEXT:  
fffff880`09cb5008 fffff800`02f4a8a4 : 00000000`00000050 fffff8a0`11870c42 00000000`00000000 fffff880`09cb5170 : nt!KeBugCheckEx
fffff880`09cb5010 fffff800`02ecafee : 00000000`00000000 fffff8a0`11870c42 fffff880`09cb5700 00000000`00000410 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`09cb5170 fffff800`02ee79f5 : fffff880`09cb5848 fffff8a0`0a989a30 fffff800`0339b7c0 fffff8a0`0a989e28 : nt!KiPageFault+0x16e
fffff880`09cb5300 fffff800`02edf68b : 00000000`00000410 00000000`00000000 fffff8a0`0a989a30 fffffa80`0cca4290 : nt!SepMandatoryIntegrityCheck+0x75
fffff880`09cb5370 fffff800`02ee7e12 : fffff880`09cb5920 00000000`00000000 00000000`00000001 fffff800`02fff71e : nt!SeAccessCheckWithHint+0x3fb
fffff880`09cb5470 fffff800`031e8525 : fffffa80`09ce1860 fffff880`09cb5920 00000000`00000001 00000000`00000000 : nt!SeAccessCheck+0x62
fffff880`09cb54e0 fffff800`031c8c23 : 00000000`00000000 00000000`00000000 fffff8a0`00010f00 00000000`00000000 : nt!ObCheckObjectAccess+0xe5
fffff880`09cb5580 fffff800`031bb329 : 00000000`00000001 fffffa80`0c783060 00000000`00000000 fffffa80`0d1dbe00 : nt!ObpCreateHandle+0x523
fffff880`09cb5690 fffff800`031a1984 : 00000000`00000000 fffff880`09cb5ca0 00000000`01dcd128 00000000`00000000 : nt!ObOpenObjectByPointerWithTag+0x109
fffff880`09cb58b0 fffff800`031a1b93 : 00000000`007c0000 00000000`007c0fff 00000000`00000000 fffffa80`0a365b50 : nt!PsOpenProcess+0x1a2
fffff880`09cb5ad0 fffff880`040ef918 : 00000000`00000850 fffff880`09cb5ca0 fffffa80`20646156 fffffa80`00000000 : nt!NtOpenProcess+0x23
fffff880`09cb5b10 00000000`00000850 : fffff880`09cb5ca0 fffffa80`20646156 fffffa80`00000000 fffffa80`00000000 : aswSnx+0x29918
fffff880`09cb5b18 fffff880`09cb5ca0 : fffffa80`20646156 fffffa80`00000000 fffffa80`00000000 fffff800`031c60b4 : 0x850
fffff880`09cb5b20 fffffa80`20646156 : fffffa80`00000000 fffffa80`00000000 fffff800`031c60b4 00000000`00000000 : 0xfffff880`09cb5ca0
fffff880`09cb5b28 fffffa80`00000000 : fffffa80`00000000 fffff800`031c60b4 00000000`00000000 00000000`00040000 : 0xfffffa80`20646156
fffff880`09cb5b30 fffffa80`00000000 : fffff800`031c60b4 00000000`00000000 00000000`00040000 fffffa80`0d15bca0 : 0xfffffa80`00000000
fffff880`09cb5b38 fffff800`031c60b4 : 00000000`00000000 00000000`00040000 fffffa80`0d15bca0 fffffa80`0d5694f0 : 0xfffffa80`00000000
fffff880`09cb5b40 fffff800`031e91bf : fffff880`09cb5ca0 00000000`00000000 00000000`007c0000 00000000`00000301 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`09cb5bd0 fffff800`02ecc153 : fffffa80`0a365b50 fffff880`00000410 00000000`01dcd0d0 00000000`00000001 : nt!NtUnmapViewOfSection+0x6b
fffff880`09cb5c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

 

 

 

 

 

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

I think the AV here means Antivirus but it's just a hunch. 

 

Basically I think Avast works with your Internet driver to filter incoming traffic. Something is going wrong in the process is my guess. Anyways, uninstalling Avast is where I would start.


Edited by thisisu, 26 March 2015 - 12:32 AM.


#3 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:34 PM

Posted 26 March 2015 - 12:23 AM

 

- Clean installation of the most recent nvidia drivers (347.52) using driver sweeper

 

 

Not something I'd recommend. Get the latest drivers, yes, but don't use 3rd party tools to do so. Just go directly to the manufacturer's website


Edited by thisisu, 26 March 2015 - 12:48 AM.


#4 zorus195

zorus195
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:34 PM

Posted 26 March 2015 - 08:58 AM

Thank you for your replies,

 

- I had already uninstall avast when I saw the error that you mention in your reply but I will try with the tool to see if there are parts of Avast that are still hidden in my system. ( The problem is that I already had multiple BSOD before installing Avast. I had installed this software last week to look for virus in my system)

 

- I did get the driver from Nvidia website,  driver sweeper was used only to remove completely the previous graphic driver.



#5 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:34 PM

Posted 26 March 2015 - 02:49 PM

Ok. Leave Avast uninstalled for a while, or until your next crash. When and if a new blue screen occurs, attach the new minidump file for analysis.



#6 zorus195

zorus195
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:34 PM

Posted 26 March 2015 - 03:39 PM

Here are the new minidumps I have had this morning.

 

This morning I tried to run memtest on all my memory sticks just after getting one bsod and there was two errors in the second pass. With this in mind I think the problem could still be related to one of my ram memory sticks. I will try to run memtest again on each of my memory sticks in the tonight and tomorrow.

 

Can you tell me if running prime 95 with only one stick of ram could help me identifying which memory stick is bad if I get a bsod with a particular one ?

 

Thank you,

Attached Files



#7 thisisu

thisisu

  • Malware Response Team
  • 2,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:02:34 PM

Posted 27 March 2015 - 03:44 AM

Can you tell me if running prime 95 with only one stick of ram could help me identifying which memory stick is bad if I get a bsod with a particular one ?

 

Sorry but I'm very familiar with prime 95. :(

 

Memtest86+ with one stick of RAM at a time should isolate which stick(s) of RAM are bad. The system might not even boot up to begin memtest if the stick is very defective.

 

Your latest BSOD logs don't show any traces of Avast but also don't mention any other faulty driver. I think you're on the right track regarding it being memory..

 

BUGCHECK_STR:  0xA

 

 

https://msdn.microsoft.com/en-us/library/windows/hardware/ff560129%28v=vs.85%29.aspx

 

Good luck let us know if it was memory



#8 zorus195

zorus195
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:04:34 PM

Posted 11 April 2015 - 02:32 PM

Hello !

 

Please apologize for my late answer, I had been doing multiples tests to find out my problem and I finally find the culprit. I waited some days to confirm that no bsod would come back before replying.

 

So the problem was related to a memory issue (RAM). One of my DIMM on my mobo was faulty on cold boot. So as a solution I just had to remove the ram stick from this DIMM Slot and my computer is working fine!

 

Thank you for your help thisisu !






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users