Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSODs while playing games


  • Please log in to reply

#1
szpula

szpula

    Member

  • Member
  • PipPip
  • 17 posts
Hello.

I have been issuing blue screens, specially during games.
Here are some reports:

Fragment of report from AIDA64:
Computer:
Computer Type ACPI x64-based PC
Operating System Microsoft Windows 7 Ultimate
OS Service Pack Service Pack 1
Internet Explorer 10.0.9200.16686
DirectX DirectX 11.0

Motherboard:
CPU Type QuadCore Intel Core i7-4770K, 3700 MHz (37 x 100)
Motherboard Name ASRock Z87 Extreme4 (2 PCI, 2 PCI-E x1, 3 PCI-E x16, 4 DDR3 DIMM, Audio, Video, Gigabit LAN)
Motherboard Chipset Intel Lynx Point Z87, Intel Haswell
System Memory 4023 MB (DDR3-1333 DDR3 SDRAM)
DIMM2: OCZ XTC Platinum OCZ3P13332G 2 GB DDR3-1333 DDR3 SDRAM (9-7-7-20 @ 666 MHz) (8-7-7-20 @ 666 MHz) (7-7-7-20 @ 666 MHz) (6-6-6-18 @ 571 MHz) (5-5-5-15 @ 476 MHz)
DIMM4: OCZ XTC Platinum OCZ3P13332G 2 GB DDR3-1333 DDR3 SDRAM (9-7-7-20 @ 666 MHz) (8-7-7-20 @ 666 MHz) (7-7-7-20 @ 666 MHz) (6-6-6-18 @ 571 MHz) (5-5-5-15 @ 476 MHz)
BIOS Type AMI (07/03/2013)

Display:
Video Adapter NVIDIA GeForce GTX 280 (1 GB)
Video Adapter NVIDIA GeForce GTX 280 (1 GB)
3D Accelerator nVIDIA GeForce GTX 280
Monitor Iiyama ProLite 2201W [22" LCD] (05881M7802248)

Multimedia:
Audio Adapter Realtek ALC1150 @ Intel Lynx Point PCH - High Definition Audio Controller [C-1]

Storage:
IDE Controller Asmedia 106x SATA Controller
IDE Controller Intel® 8 Series/C220 Series SATA AHCI Controller - 8C02
Disk Drive ST3500410AS ATA Device (500 GB, 7200 RPM, SATA-II)
Disk Drive WDC WD1500HLFS-01G6U0 ATA Device (150 GB, 10000 RPM, SATA-II)
Disk Drive WDC WD20EARX-00PASB0 ATA Device (2000 GB, SATA-III)
Optical Drive DTSOFT Virtual CdRom Device
Optical Drive PIONEER DVD-RW DVR-216 ATA Device (DVD+R9:12x, DVD-R9:12x, DVD+RW:20x/8x, DVD-RW:20x/6x, DVD-RAM:12x, DVD-ROM:16x, CD:40x/32x/40x DVD+RW/DVD-RW/DVD-RAM)
SMART Hard Disks Status OK

Partitions:
C: (NTFS) 139.6 GB (65.7 GB free)
D: (NTFS) 1863.0 GB (179.6 GB free)
E: (NTFS) 465.8 GB (242.8 GB free)
Total Size 2468.4 GB (488.1 GB free)


BlueScreenView Report:
==================================================
Dump File : 092113-32042-01.dmp
Crash Time : 2013-09-21 10:08:47
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`02d38348
Parameter 3 : fffff880`09edd8a0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092113-32042-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 512
Dump File Time : 2013-09-21 10:09:51
==================================================

==================================================
Dump File : 092013-28251-01.dmp
Crash Time : 2013-09-20 00:25:00
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff880`e9a00002
Parameter 2 : 00000000`00000008
Parameter 3 : fffff880`e9a00002
Parameter 4 : 00000000`00000005
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+7e767
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092013-28251-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 286 920
Dump File Time : 2013-09-20 00:26:20
==================================================

==================================================
Dump File : 091913-27409-01.dmp
Crash Time : 2013-09-19 20:31:55
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff680`40039fa8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`02c6b52b
Parameter 4 : 00000000`00000005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091913-27409-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 664
Dump File Time : 2013-09-19 20:36:09
==================================================

==================================================
Dump File : 091913-28906-01.dmp
Crash Time : 2013-09-19 18:30:59
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`001f23e9
Parameter 3 : fffff880`0678baf0
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1e23e9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091913-28906-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 648
Dump File Time : 2013-09-19 18:32:13
==================================================

==================================================
Dump File : 091913-27830-01.dmp
Crash Time : 2013-09-19 00:46:48
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091913-27830-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 640
Dump File Time : 2013-09-19 00:48:26
==================================================

==================================================
Dump File : 091813-27190-01.dmp
Crash Time : 2013-09-18 23:27:08
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : 00000000`0d16e7f0
Parameter 3 : fffff880`0cfcafb0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75b80
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18229 (win7sp1_gdr.130801-1533)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091813-27190-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 648
Dump File Time : 2013-09-18 23:28:18
==================================================

==================================================
Dump File : 091813-28828-01.dmp
Crash Time : 2013-09-18 22:20:57
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff800`02ce089b
Parameter 3 : fffff880`0c48c9f0
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+a3780
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091813-28828-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 664
Dump File Time : 2013-09-18 22:22:07
==================================================

==================================================
Dump File : 091813-28875-01.dmp
Crash Time : 2013-09-18 20:03:49
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff960`00096227
Parameter 3 : fffff880`0bfdaf30
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091813-28875-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262 144
Dump File Time : 2013-09-18 20:04:47
==================================================

==================================================
Dump File : 091713-32027-01.dmp
Crash Time : 2013-09-17 17:21:15
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`4800000d
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`01a5781c
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5781c
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091713-32027-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 664
Dump File Time : 2013-09-17 17:23:28
==================================================


WhoCrashed Report:
On Sat 2013-09-21 08:08:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092113-32042-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D38348, 0xFFFFF88009EDD8A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2013-09-21 08:08:47 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D38348, 0xFFFFF88009EDD8A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2013-09-19 22:25:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092013-28251-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFF880E9A00002, 0x8, 0xFFFFF880E9A00002, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2013-09-19 18:31:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091913-27409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFF68040039FA8, 0x0, 0xFFFFF80002C6B52B, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2013-09-19 16:30:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091913-28906-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1E23E9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001F23E9, 0xFFFFF8800678BAF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
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 Wed 2013-09-18 22:46:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091913-27830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2013-09-18 21:27:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-27190-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xD16E7F0, 0xFFFFF8800CFCAFB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2013-09-18 20:20:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-28828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002CE089B, 0xFFFFF8800C48C9F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2013-09-18 18:03:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091813-28875-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002CCCB80)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF96000096227, 0xFFFFF8800BFDAF30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
Google query: SYSTEM_SERVICE_EXCEPTION



On Tue 2013-09-17 15:21:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091713-32027-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001A5781C)
Bugcheck code: 0xD1 (0x4800000D, 0x2, 0x0, 0xFFFFF88001A5781C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik TCP/IP
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.
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.



Thank you very much for your help.
  • 0

Advertisements


#2
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
Sometimes BSOD happens also during normal usage of PC, like browsing sites or watching movies.

SFC /SCANNOW result:
Windows Resource Protection did not find any integrity violations.
  • 0

#3
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,902 posts
:welcome: szpula

Have you checked the Device Manager for any yellow ! or red Xs and in particular against the network devices.

Has the HDD been making any unusual noises at all.

What anti virus software do you have installed.

What are the brand and model name or number details of the PSU.

To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2

1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

2. Run the Driver Verifier -
Code:
START | type verifier | make these selections -

1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot*** IMPORTANT - PLEASE READ:

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to the next post.
  • 1

#4
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
Hello.

Thank you for some advices.
Before you responded I run some HDD tests. Here are results:

Western Digital Data LifeGuard Diagnostic
Test Option: EXTENDED TEST
Model Number: WDC WD1500HLFS-01G6U0
Unit Serial Number: WD-WXL708030627
Firmware Number: 04.04V01
Capacity: 150.04 GB
SMART Status: PASS
Test Result: PASS
Test Time: 00:53:48, September 22, 2013

Test Option: EXTENDED TEST
Model Number: WDC WD20EARX-00PASB0
Unit Serial Number: WD-WCAZAF616992
Firmware Number: 51.0AB51
Capacity: 2000.40 GB
SMART Status: PASS
Test Result: PASS
Test Time: 07:36:35, September 22, 2013


SeaTools
2013-09-22 08:47:48
Model: ST3500410AS
Serial Number: 5VM0AJLL
Firmware Revision: CC33
Fix All Fast - Pass 2013-09-22 08:47:48
Fix All Long - Pass 2013-09-22 10:08:55
SMART - Pass 2013-09-22 10:10:44
Short DST - Started 2013-09-22 10:10:54
Short DST - Pass 2013-09-22 10:11:55
Identify - Started 2013-09-22 10:12:14
Short Generic - Started 2013-09-22 10:12:30
Short Generic - Pass 2013-09-22 10:13:48


It seems that all three HDDs are OK. I use WD1500HLFS for system and programs/games.


Answers to your questions:
- not even a single yellow or red mark near any device,
- HDDs are pretty quiet and for sure not making any unusual noises,
- AV: AGV Internet Security 2014,
- PSU: be quiet! Dark Power Pro 750W (P7 - version from year 2008: http://www.bequiet.c.../powersupply/73 )
I'm aware that this PSU is not fully compatible with Haswell CPU, but I disabled all sleep states in BIOS and don't use sleep/hibernate in Windows. I hope to change this PSU ASAP to newer one.

Driver Verifier:
I run it twice and it twice crashed on RTCore64.sys which is part of MSI Afterburner. Unfortunately I forgot to copy these dumps before I restored system and now they've gone.
But after reinstalling MSI Afterburner, verifier has been running for at least 30 minutes and no BSOD till now.

I will try to stress PC today and leave it for whole night and day. I'll let you know when I have some BSODs (or when I don't have ;) ).
  • 0

#5
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,902 posts
Thanks for the comprehensive update and you are most welcome szpula :thumbsup:

Was the reinstall of a Afterburner an updated version as that does apparently resolve RTCore64.sys issues sometimes.
  • 0

#6
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
I had the newest version, I can try install it one more time. I like this app, since I can reduce my fan speed for lower temperatures...

But since my last update, PC froze once - no BSOD, but no resposnse from mouse, keyboard. It had happened before (more or less: half time were BSODs and half time freezes).

And one BSOD appeared:

BlueScreenView:
==================================================
Dump File : 092213-43664-01.dmp
Crash Time : 2013-09-22 19:02:19
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000028
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01a8813d
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+8813d
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092213-43664-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 291 512
Dump File Time : 2013-09-22 19:03:34
==================================================



WhoCrashed:
On Sun 2013-09-22 17:02:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-43664-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8813D)
Bugcheck code: 0xD1 (0x28, 0x2, 0x1, 0xFFFFF88001A8813D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik TCP/IP
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.
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 2013-09-22 17:02:19 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8813D)
Bugcheck code: 0xD1 (0x28, 0x2, 0x1, 0xFFFFF88001A8813D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik TCP/IP
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.
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.
  • 0

#7
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,902 posts
Network drivers and/or AVG I suggest be checked first.

Is AVG the free or paid for version as I would suggest uninstalling it if only temporarily for testing purposes, you can always reinstall it later if it turns out not to be the culprit (make a note of the product key if it is the paid for version) use Avast or MSE free in the meantime.
AVG uninstaller tool

Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop...pit/default.asp
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Thanks to rshaffer61 for the PCPitstop information :thumbsup:

NB: An example of the url that we require and the information that it leads to http://www.pcpitstop.com/betapit/sec.asp?conid=25271813
  • 1

#8
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
I appreciate your help.

I uninstalled AVG using AVG uninstaller tool and installed MSE.

URL to PCPitstop: http://www.pcpitstop...?conid=25433429
  • 0

#9
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,902 posts
Thanks for the update szpula :thumbsup:

While I go over the test results please return to the PCPitstop results and address the items that have a red X against them, if you hover the cursor over the item you will be given a description of the issue and if you click on it you will be instructed how to correct the problem, post back when you have done this please.

You are welcome BTW :)
  • 1

#10
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
Hello.

New test: http://www.pcpitstop...?conid=25433429

There are still few red crosess, but I don't think that they need to be fixed:
- Increase Free Space (Drive D:) 8% Free (147582 MB) - I think that that amount of free space should be enough for 2TB partition.
- Clear IE Cache 99 MB - I cleared cache for every user, I think that that site needs a lot of cache to be involved.
- Defragment Drive C: 24% - Before defragmentation Windows told be that fragmentation level is 7%. Defragmentation had been done and on thtat site it has been changed from 24% to... 24%? I believe they seem some problem with "Data Fragmentation".
- Disable Firefox Saved Passwords - really? :)

Since uninstall of AVG, PC has been turned on all night, my wife did some AutoCAD stuff and not single freeze or BSOD happened. I will try to stress it with Witcher2 or something after work.
  • 0

Advertisements


#11
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
OK.

Another BSOD appeared:

On Mon 2013-09-23 16:58:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092313-20935-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001A7D036)
Bugcheck code: 0xD1 (0x2F9, 0x2, 0x0, 0xFFFFF88001A7D036)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Sterownik TCP/IP
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.
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 Mon 2013-09-23 16:58:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e1d62x64.sys (e1d62x64+0x265C3)
Bugcheck code: 0xD1 (0x2F9, 0x2, 0x0, 0xFFFFF88001A7D036)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1d62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® Gigabit Adapter NDIS 6.x 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: e1d62x64.sys (Intel® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


e1d62x64.sys is my LAN driver. I checked that it was the newest version, but I reinstalled it anyway.

I opened MEMORY.DMP in WinDbg and it is a result of calling 'kpn 1000':

# Child-SP RetAddr Call Site
00 fffff880`0c45e588 fffff800`02cd6129 nt!KeBugCheckEx
01 fffff880`0c45e590 fffff800`02cd4da0 nt!KeSynchronizeExecution+0x3d39
02 fffff880`0c45e6d0 fffff880`01a7d036 nt!KeSynchronizeExecution+0x29b0
03 fffff880`0c45e860 fffff880`01a5e8cc tcpip+0x7d036
04 fffff880`0c45eb00 fffff880`01a83093 tcpip+0x5e8cc
05 fffff880`0c45ebc0 fffff880`01a83445 tcpip+0x83093
06 fffff880`0c45ed10 fffff880`01a7da9d tcpip+0x83445
07 fffff880`0c45eea0 fffff880`01a44cf3 tcpip+0x7da9d
08 fffff880`0c45efb0 fffff880`01a554a2 tcpip+0x44cf3
09 fffff880`0c45f110 fffff800`02ce2878 tcpip+0x554a2
0a fffff880`0c45f160 fffff880`01a55bd2 nt!KeExpandKernelStackAndCalloutEx+0xd8
0b fffff880`0c45f240 fffff880`019390eb tcpip+0x55bd2
0c fffff880`0c45f2b0 fffff880`01902ad6 ndis!NdisIMInitializeDeviceInstance+0x1b9b
0d fffff880`0c45f320 fffff880`0187cac1 ndis!NdisIMNotifyPnPEvent+0x1436
0e fffff880`0c45f7a0 fffff880`072265c3 ndis!NdisMIndicateReceiveNetBufferLists+0xc1
0f fffff880`0c45f7f0 fffff880`07226791 e1d62x64+0x265c3
10 fffff880`0c45f830 fffff880`07218a74 e1d62x64+0x26791
11 fffff880`0c45f8b0 fffff880`07216c36 e1d62x64+0x18a74
12 fffff880`0c45f9b0 fffff880`07218cf8 e1d62x64+0x16c36
13 fffff880`0c45fa20 fffff880`01906542 e1d62x64+0x18cf8
14 fffff880`0c45fa60 fffff880`0188f56d ndis!NdisMPauseComplete+0x992
15 fffff880`0c45fad0 fffff880`018b5b7d ndis!NdisOpenConfigurationEx+0xd1d
16 fffff880`0c45fb70 fffff800`02f74bae ndis!NetDmaAllocateChannel+0x5fd
17 fffff880`0c45fc00 fffff800`02cc78c6 nt!PsCreateSystemThread+0x1da
18 fffff880`0c45fc40 00000000`00000000 nt!KeInitializeSemaphore+0x24a
  • 0

#12
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,902 posts
Looks like a conflict between the Intel and the Microsoft network drivers so you have done the right thing by reinstalling the Lan driver, trying an earlier one than the problematic one can also resolve such issues.

Please note that you must always have a minimum of between 15 and 20% of a HDDs overall storage capacity available as free space or you risk the data on the drive becoming corrupt or in a worst case scenario mechanical failure of the HDD itself.
The above can render a computer inoperable if the HDD concerned has the OS on it due to the MBR (Master Boot Record) becoming damaged/corrupt, please see information @ http://pcsupport.abo...sterbootrec.htm

Go to Start then to Run/Search
Type in compmgmt.msc and click Enter
On the left side click on Disk Management
On the right side you will see your hard drive.
Now I need you to take an expanded screenshot and attach it to your next reply.

To capture and post a screenshot;

Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... then after typing in any response you have... click on browse...desktop...find the screenshot..select it and click on the upload button...then on the lower left...after it says upload successful...click on add reply like you normally would.

Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.

  • 1

#13
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
I have been doing some memory tests (using memtest86), so can not take screenshot right now.

But are you sure that my 2TB HDD should have minimum 300GB-400GB of free space? I can understand this 15-20% limit for smaller discs on which OS is installed, but this HDD is used only as storage - nothing is installed there.
Moreover, if I unplug this HDD, BSODs still occur (I have tested this before I wrote here).
  • 0

#14
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,902 posts
Memtest :thumbsup:

It is an often asked question the amount of free storage space, please see the exampleHere

Moreover, if I unplug this HDD, BSODs still occur (I have tested this before I wrote here).

I wasn`t aware of this :thumbsup:
  • 0

#15
szpula

szpula

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
In best answer in this example, there is nice conclusion: So you want to have 10% plus free on your main HDD ;)

About this LAN driver:
I had PROSet (version 18.2.63.0) with e1d62x64 (version 12.6.47.0). This was the newest version on Asrock site. Intel Update application told me that this the newest one too.

But here I found PROSet 18.6.111.0 (e1d62x64 version 12.8.33.0). I installed this, we will see what happens... BTW, my LAN device is: Intel Ethernet Connection I217-V

About memtest86:
I don't now if I did well, but I used Memtest86 Version 5.0 Experimental UEFI Beta.
My settings: 6 passes and CPU in parallel mode (8 logical CPUs works concurrently).

Setup:
I have 2 RAM stick, one has "1" at the end of s/n, second one has "2" - I will use these numbers.
Tests in the order of execution:

1 2 3 4 RESULT
0 2 0 1 FAIL (freeze - no results)
2 0 0 0 PASS
0 2 0 0 PASS
0 0 2 0 PASS
0 0 0 2 PASS
1 0 0 0 PASS
0 1 0 0 PASS
0 0 1 0 FAIL
0 0 0 1 FAIL
1 0 2 0 FAIL (freeze - no results)
0 1 0 2 FAIL (freeze - no results)
2 0 1 0 FAIL

It took a while to perform these tests - each of non-freeze lasts > 1h40m

Right now I have "2" in first slot only.
But what do you think about these results?
(I hope that this is RAM fault, because these sticks have 5 years and I want to buy new ones anyway in few days...)


Here are 2 fail results:
http://pastehtml.com.../dh39oiram.html
http://pastehtml.com.../dh39qd79q.html
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP