Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD ERRORS [REFERENCE_BY_POINTER ntoskrnl.exe] & [SYSTEM_SERVICE_E...

13 Apr 2013   #1
Ghassen

Windows 7 Ultimate x64
 
 
BSOD ERRORS [REFERENCE_BY_POINTER ntoskrnl.exe] & [SYSTEM_SERVICE_E...

Hi,
Am getting différents BSOD errors plz help.

WhoCrashed (some)

Quote:
computer name: GASTON-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17126387712 total
VM: 2147352576, free: 1911566336

On Sat 13/04/2013 20:36:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041313-18002-01.dmp
uptime: 00:24:05
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800333F3C8, 0xFFFFF8800333EC20, 0xFFFFF8000309CA01)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 13/04/2013 20:36:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:24:05
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800333F3C8, 0xFFFFF8800333EC20, 0xFFFFF8000309CA01)
Error: CACHE_MANAGER
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 13/04/2013 20:11:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041313-15334-01.dmp
uptime: 02:48:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003074750, 0xFFFFF8800A4BCD10, 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 which cannot be identified at this time.


On Sat 13/04/2013 07:56:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041313-22729-01.dmp
uptime: 00:28:53
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x18 (0x0, 0xFFFFF8A0025767C0, 0x2, 0xFFFFF8A008B67DD7)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/04/2013 18:03:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041213-17706-01.dmp
uptime: 00:03:54
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800333F3C8, 0xFFFFF8800333EC20, 0xFFFFF8000309F9F9)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/04/2013 02:39:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041213-24788-01.dmp
uptime: 05:36:00
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x109 (0xA3A039D8A686C524, 0x0, 0x5FA405743DFB901, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 09/04/2013 23:51:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041013-12012-01.dmp
uptime: 00:04:07
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800999FC88, 0xFFFFF8800999F4E0, 0xFFFFF800030F6AE9)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 which cannot be identified at this time.


On Sun 07/04/2013 20:41:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040713-16458-01.dmp
uptime: 00:59:38
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006DADCEE, 0xFFFFF880023CE568, 0xFFFFF880023CDDC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.


On Sat 06/04/2013 23:38:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040713-17284-01.dmp
uptime: 00:06:00
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x109 (0xA3A039D89E4FF6FF, 0x0, 0x454E50D4D4BE4989, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 06/04/2013 17:35:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040613-13962-01.dmp
uptime: 00:03:32
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CEE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003DC2CEE, 0xFFFFF88005FFE568, 0xFFFFF88005FFDDC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 which cannot be identified at this time.




My System SpecsSystem Spec
.
13 Apr 2013   #2
VistaKing

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Hi Ghassen

Might want to upgrade your Video driver

Description:Version:Date :Operating System :Download
NVIDIA GeForce GTX 480 314.22 2013.03.25 Windows 7 64-bit, Windows Vista 64-bit, Windows 8 64-bit download
My System SpecsSystem Spec
13 Apr 2013   #3
Ghassen

Windows 7 Ultimate x64
 
 

...
My System SpecsSystem Spec
.

14 Apr 2013   #4
Ghassen

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by VistaKing View Post
Hi Ghassen

Might want to upgrade your Video driver

Description:Version:Date :Operating System :Download
NVIDIA GeForce GTX 480 314.22 2013.03.25 Windows 7 64-bit, Windows Vista 64-bit, Windows 8 64-bit download

updated but still having Bsod's
My System SpecsSystem Spec
Reply

 BSOD ERRORS [REFERENCE_BY_POINTER ntoskrnl.exe] & [SYSTEM_SERVICE_E...




Thread Tools




Similar help and support threads
Thread Forum
BSOD - ntoskrnl.exe errors
My computer has been getting the BSOD frequently over the past couple of weeks. It happens most of the time when I am playing league of legends, but that isn't always the case. I have already tried to run a memtest, but it would get stuck in a loop on test 8 that would say I have between 0-32767...
BSOD Help and Support
BSOD REFERENCE_BY_POINTER, Others - No Cause Jumping Out
Been having random BSOD crashes over the last week or so, unable to isolate the problem. Nothing has been changed that the user can remember, though it's not my machine so I am unsure. Have run the usual disk checks and scans, registry repairs, rebooted with individual sticks of RAM in, no...
BSOD Help and Support
BSOD ntoskrnl.exe errors
Hi I'm new to this forum. I have a DELL Studio XPS 8000 I7 (x64), which I've had for just a year. It worked fine for about 9 months, then 3 months ago started crashing randomly. This seemed to become more and more frequent. I tried several things. - Windows Update - chkdsk /r - Registry...
BSOD Help and Support
BSOD reference_by_pointer
win 7 64 bit keep getting BSOD ...reference_by_pointer dump file attached please help or advised!! thanks!
BSOD Help and Support
BSOD's with ntoskrnl errors
Hello everyone, I'm wondering if someone can help me with persistent and annoying ntoskrnl errors that I seem to be getting lately. The dumps are attached. They happen when I'm doing anything, firefox web browsing, email, talking on trillian, typing an email in outlook 2007, etc. I can't seem...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 04:24.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App