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 ntoskrnl.exe (nt+0x75C00)

20 Apr 2013   #1
rambocpu

Windows 7 Ultimate 64Bit
 
 
BSOD ntoskrnl.exe (nt+0x75C00)

Hello

My computer was fine untill today when all of a sudden I heard it restarting from the kitchen. I went in and I had no idea why it restarted so I just let it boot up again. Then I got an BSOD and I have gotten several since using WhoCrashed I have managed to get them all because I had log saving on.

It appears that all BSODs have had different causes.

Code:
On Sat 2013-04-20 17:57:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-8907-01.dmp
uptime: 00:03:40
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) 
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0xEE86, 0xEE842001DD0C)
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 Sat 2013-04-20 17:57:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:03:40
This was probably caused by the following module: ntfs.sys (Ntfs+0x9AA6F) 
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0xEE86, 0xEE842001DD0C)
Error: MEMORY_MANAGEMENT
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 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 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 2013-04-20 17:19:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-6068-01.dmp
uptime: 00:00:35
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800037B3CD0, 0x0, 0x20000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 


On Sat 2013-04-20 07:50:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-6692-01.dmp
uptime: 00:00:08
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) 
Bugcheck code: 0x1A (0x31, 0xFFFFFA800AFF0B50, 0xFFFFF88003E57000, 0xFFFFF8A001F6F98D)
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 Sat 2013-04-20 07:12:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042013-9562-01.dmp
uptime: 00:04:39
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) 
Bugcheck code: 0xA (0xFFFFF6800000CD40, 0x0, 0x0, 0xFFFFF80003598545)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.
If there is anything that you want me to do then please don't hesitate to ask. I found this link thread from this very same forum but it did not help me.

"ntoskrnl.exe" BSOD

I have tried checking for RAM errors in windows, that screen just rebooted my PC without telling me anything... I have tried resetting boot.ini

What to do? D:

I am reading the posting instructions now, I just wanted to get this thread up before a new BSOD shows up.


My System SpecsSystem Spec
20 Apr 2013   #2
VistaKing

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

Hi rambocpu

Welcome to Se7enForums. Please take a look at the link below

Blue Screen of Death (BSOD) Posting Instructions

Looking at your post the BSOD point to a memory issue . Run the Memtest . Link to get the software is below. You will need a USB flash drive. If you get any errors test each memory on every slot. You want to run the test over night cause it could error out on the last Pass. You want at least 8-10 passes.

RAM - Test with Memtest86+
My System SpecsSystem Spec
20 Apr 2013   #3
rambocpu

Windows 7 Ultimate 64Bit
 
 

Quote   Quote: Originally Posted by VistaKing View Post
Hi rambocpu

Welcome to Se7enForums. Please take a look at the link below

Blue Screen of Death (BSOD) Posting Instructions

Looking at your post the BSOD point to a memory issue . Run the Memtest . Link to get the software is below. You will need a USB flash drive. If you get any errors test each memory on every slot. You want to run the test over night cause it could error out on the last Pass. You want at least 8-10 passes.

RAM - Test with Memtest86+
Fixed the posting instructions, working on memtest now. Will get back with the results.
My System SpecsSystem Spec
20 Apr 2013   #4
VistaKing

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

Code:
******************************************************************************
*                                                                                                                                         *
*                        Bugcheck Analysis                                                                                         *
*                                                                                                                                          *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff780c0000000
Arg3: 000000000000ee86
Arg4: 0000ee842001dd0c

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mbam.exe

CURRENT_IRQL:  0
Caused by MalwareBytes

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff6800000cd40, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003598545, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c8100
GetUlongFromAddress: unable to read from fffff800036c81c0
 fffff6800000cd40 Nonpaged pool

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiEmptyWorkingSet+1c5
fffff800`03598545 488b02          mov     rax,qword ptr [rdx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  CurseClient.ex
Uninstall CurseClient or Reinstall

Code:
*******************************************************************************
*                                                                                                                                           *
*                        Bugcheck Analysis                                                                                           *
*                                                                                                                                           *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa800aff0b50
Arg3: fffff88003e57000
Arg4: fffff8a001f6f98d

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  0x1a_31

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  hola_updater.e
Update or reinstall your Hola Network software

I advise you to open up a new thread in Security Systems to check if you have any rootkits or viruses on your PC
My System SpecsSystem Spec
20 Apr 2013   #5
rambocpu

Windows 7 Ultimate 64Bit
 
 

Incredible support, running memtest as im writing this on my phone, getting a bunch of red stuff. Does this mean that I HAVE to replace my ram? Will return with more info when its done. What leads you to think that i have a virus/trojan? I ran malware bytes to be sure but i never had the time to finish it before a BSOD showed up
My System SpecsSystem Spec
20 Apr 2013   #6
VistaKing

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

If you are getting a bunch of red stuff on the memtest. Stop the test and test each RAM on every slot. One RAM Stick at a time . But the memory is what is causing your BSODs.

The virus scan is just a precaution .
My System SpecsSystem Spec
20 Apr 2013   #7
rambocpu

Windows 7 Ultimate 64Bit
 
 

So I have to buy new RAM then, well that sucks.

But I ran the memtest and I will test each stick, I'll soon get money and I'll guess I'll buy more. I stopped the CurseClient and Malwarebytes and I watched the avatar movie to pass time.

3 hours have gone and no BSOD since. I will test each stick tommorrow in all different slots.
My System SpecsSystem Spec
20 Apr 2013   #8
VistaKing

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

Yes test the ram in different slots . One stick at a time . If the ram passes in one slot but fails on another slot test another slot if the new slot passes the memory you have a bad DIMM slot and that would be replacing the motherboard .
My System SpecsSystem Spec
20 Apr 2013   #9
rambocpu

Windows 7 Ultimate 64Bit
 
 

I have purchased an Asus P8Z77-V LX.

Do you think that they will replace it for free assuming it is the motherboard that causes it?
My System SpecsSystem Spec
20 Apr 2013   #10
VistaKing

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

Test the memory first . If the memory passes on one slot but fails on another and passes on another you have a bad slot . If you still have warranty on the motherboard then Asus should replace it .
My System SpecsSystem Spec
Reply

 BSOD ntoskrnl.exe (nt+0x75C00)




Thread Tools




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 11:23 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App