SYSTEM_SERVICE_EXCEPTION & MEMORY MANAGEMENT ERRORS ON WIN 7 64 BIT

AoE

New Member
#1
Hi guys, I found another thread on what might be the same problem on this board but not sure yet.

Basically I installed Windows 7 64bit from a 32 bit system, i did this by inserting disk on bootup. After install things were working ok for a bit until i downloaded Norton AV and tryed to do an MS update.

Then I get both BSOD errors, with restarts. I then uninstalled norton AV in safe mode, but still occurring.

If it helps my ram is PNY 1x2gb 1333mhz and Mushkin 1x4gb 1600mhz, but I installed the 1600 stick as I was told it would automatically downgrade to 1333 as default so not sure if thats the issue?


EDIT: I ran a windows memory diagnostic scan and there was NO problems found!
Any help is much thankful. I've also took out the higher ram stick and replaced it with another 1333. Problem has not occured yet, but my CPU (AMD Phenom II x 4 840 3.2GHZ) usage looks to be a bit high on internet and idle between 5-25%


Reports from whocrashed:

Crash dump directory: C:\Windows\Minidump

On Sun 13/11/2011 11:44:37 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-20202-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880093E1B28, 0xFFFFF880093E1380, 0xFFFFF80002CDC4D4)
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 which cannot be identified at this time

On Sun 13/11/2011 11:44:37 GMT your computer crashedcrash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880093E1B28, 0xFFFFF880093E1380, 0xFFFFF80002CDC4D4)
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 which cannot be identified at this time.

On Sun 13/11/2011 10:57:00 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-19812-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x74B10)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000084B10, 0xFFFFF880086915E0, 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 which cannot be identified at this time.


On Sun 13/11/2011 10:51:05 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-19921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC5000B6B8, 0x92800001250AB882, 0xFFFFF8A000108FC1)
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 which cannot be identified at this time.

On Sun 13/11/2011 10:45:36 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-49779-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xE6CC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880011476CC, 0xFFFFF880033C48D8, 0xFFFFF880033C4130)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Sun 13/11/2011 10:22:51 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-16785-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA65BE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001265BE, 0xFFFFF88006D72FB0, 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 which cannot be identified at this time.


On Sun 13/11/2011 08:31:17 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-16957-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0xA2E3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002ABABF4, 0xFFFFF880031B6578, 0xFFFFF880031B5DD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 Sun 13/11/2011 08:19:22 GMT your computer crashedcrash dump file: C:\Windows\Minidump\111311-26052-01.dmp
This was probably caused by the following module: hal.dll (hal+0xF768)
Bugcheck code: 0xBE (0xFFFFF8A00664D068, 0xA360000109D2E121, 0xFFFFF88003BC4650, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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
 


Last edited:

Elmer

Extraordinary Member
#2
Hi AoE and Welcome to the Forum,

We really need the actual dmp files to help you, a lot more information is contained within them than the summaries above.

To ensure minidumps are enabled:
Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

The .dmp files are located at C:\Windows\Minidump. Until a .dmp file is generated, the Minidump folder may not exist.

Go to your C:\Windows\Minidump folder. Copy the .dmp files to a new folder on your desktop. Zip up that folder and attach to a post.
You also say you removed Norton (a wise move). Did you run the Norton Removal Tool afterwards to clean up the remnants it inevitably leaves behind?

B.T.W. Many varied bugcheck codes (or Stop errors) can indicate hardware issues.
 


AoE

New Member
#4
View attachment Mini dumps.zip Heres the minidump files attached: thanks

I also got a SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
 


Last edited:

Elmer

Extraordinary Member
#5
Hi AoE,

Well the good/bad news is that your drivers look pretty good to me. That's the easy option out the window!

Your getting a lot of random stop errors as mentioned, this can indicate hardware problems.

Can you run ChkDsk on all your hdd's/partitions. If it finds and repairs problems it might be a good idea to run the hdd mfrs. disk check utility. A list of downloads can be found here.

Next (or before!) download and run CPU-Z. Take screenshots**/snips of the Mainboard tab, Memory tab and all the slot #'s under the SPD tab.
Go to Post Reply, click on the Go Advanced button and attach the screenshots**/snips to your post for all the RAM experts to see by using the paper clip you will find on the top toolbar. Do not zip them up.
**If screenshots, please crop.

Also, Can you tell us what security / AV software you are running?
 


AoE

New Member
#6
all sorted thanks to
Elmer
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.