3 Blue Screen of Death Errors. PLEASE HELP

jediarron

Honorable
May 7, 2012
218
0
10,680
0
Hello guys

My PC Specs are:

Gigabyte GA-D3H-Z77 Motherboard
Gigabyte 2GB GTX 670 Graphics Card
Corsair 8GB (2x4GB) RAM
Intel i7 3770k processor
Noctua NH-D14 fan
Corsair 650W PSU
Lexa S Case

It turns out, I have had 3 Blue Screen of Death error messages.

I downloaded BlueScreenViewer, to find out what they were.

Here is a screenshot of the 3 error messages (which have occurred recently), and it tells you what driver/address it is being caused by. (click to zoom)



So they are:

MEMORY_MANAGEMENT
BAD_POOL_HEADER
SYSTEM_SERVICE EXCEPTION


Could anyone tell me what to do in order to resolve this issue?

I really appreciate your time for even reading this, and would be very greatful for your help.

P.S, I custom built my PC, it's about 3 months old at the most.
 

morbious81

Honorable
Sep 11, 2012
124
0
10,690
3
Go in bios and set everything to optimized settings (usually F5), save settings and exit(usually F10). If it boots go back into bios and set your RAM to what ever you have it set at now. If it doesn't boot after changing the RAM, there's your issue.

You can always try reseating your mem sticks first. remember to ground yourself first.
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


I have used my PC for months, I haven't changed any of the settings, so I'm assuming they're at the right settings, also, a note to make is that the crashes happen 1 hour after my PC is on
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


I restored the DEFAULTS in my BIOS, it was apparent that nothing really changed.
I have no previous recollection of changing any settings anyway.
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


Downloading it onto a disk soon!
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0
Okay guys, I'm really struggling to install memtest, I can't unzip the file or anything, because my winZIP free trial has expired, what do I do?
I saw in another video, a guy opened it and extrated it via Windows Explorer, but I can't seem to get that option :l
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0
On Wed 26/09/2012 21:24:10 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-18907-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80050A8790, 0xFFFF, 0x0)
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 Wed 26/09/2012 21:24:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x16D8)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80050A8790, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 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 Wed 26/09/2012 18:55:15 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-18907-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x41284, 0xFFFFF704401FC001, 0x5D14E80, 0xFFFFF70001080000)
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 Wed 26/09/2012 18:24:30 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-26769-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x21, 0xFFFFF900C2225000, 0x1B60, 0x581B60)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Wed 26/09/2012 17:12:57 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-21684-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80050A8700, 0xFFFF, 0x0)
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 Wed 26/09/2012 16:23:21 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-15927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FFE90D, 0xFFFFF880074D0FA0, 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 Wed 26/09/2012 11:05:01 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-14492-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003167CC2, 0xFFFFF88003D83B30, 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 Wed 26/09/2012 11:03:30 GMT your computer crashed
crash dump file: C:\Windows\minidump\092612-16395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80050A8790, 0xFFFF, 0x0)
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 Thu 21/06/2012 14:53:31 GMT your computer crashed
crash dump file: C:\Windows\minidump\062112-15459-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003010EF0, 0xFFFFF80003010AF0, 0xFFFFF80003010AF0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Thu 21/06/2012 14:49:03 GMT your computer crashed
crash dump file: C:\Windows\minidump\062112-17877-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008147028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Thu 21/06/2012 14:35:53 GMT your computer crashed
crash dump file: C:\Windows\minidump\062112-18595-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x44 (0xFFFFFA8009CEA820, 0xEAE, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
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 driver has tried to requested an IRP be completed that is already complete.
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 Sun 17/06/2012 22:22:34 GMT your computer crashed
crash dump file: C:\Windows\minidump\061712-15475-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x1A (0x411, 0xFFFFF680000F2038, 0x8800, 0xFFFFF68000000003)
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.
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


Secondly, I have downloaded memtest (the link you provided) but I am in the same situation again. It says it's a winZIP file, and when I open it, it says that my trial has expired.. what do I do after I downloaded memtest in my scenario?
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


Well I got hold of WinZIP again, BUT I can't open the file and it's really ... *****

Really annoying I don't know how to make this file run omg.. please help It's really.. I can't express how annoyed I am I've ... been trying to get this ... program working for 3 hours and still....... I'm really annoyed.. lol

Even on WinZIP I can't open it when I press extract, or double click it, What am I supposed to do? ?!?!?!?!? :(
 

RussK1

Splendid


It's a pre-built .iso... I don't have winzip, 7-zip, etc and it works fine on my machine. Just click on the .zip file and extract it... Windows will do it for you. Once extracted you'll be prompted to burn to a disk image.

Here I put it in my MediaFire for you:

http://www.mediafire.com/?tpx2tc4w21wogxv
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


Will do, thanks for the heads up!
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0


Thank you good sir, I spent 4-5 hours last night trying to open it and install it first, THEN put it on the CD -_-

I will be running this later on and uploading the results at (4PM GMT) (11 EST)
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0
So I put Memtest onto a CD, and directed my PC to boot from the CD, it never does -.-
I just downloaded Prime95, will Youtube how to use the test and upload it later (this evening)
 

johhny-marshal

Honorable
Aug 27, 2012
92
0
10,630
0



Well, you must know the reason of BSOD. Blue screen appears when some file or the whole Windows crashes. If it is running fine after BSOD, I would suggest you to repair the Windows. If it has been crashed completely, you will have to put a fresh install of Windows. In fact, the fresh installation would be a great option. After that, put Avast! pro or MSE antivirus program on your computer.
 

Hawkeye22

Champion
Moderator



It's an ISO file, you can't just burn it to disk as a data file. An ISO file is an image of a disk. Most disk burning software has an option to burn ISO which recreates an original disk. If you put the disk in the drive and open it with explorer and see the ISO file on it, then you burned the disc incorrectly.
 

morbious81

Honorable
Sep 11, 2012
124
0
10,690
3
I've gotta ask, because I haven't seen it asked yet. (If I missed it I apologize for my bad eyes.)
Have you installed any new hardware or software lately, like right before the BSOD's started?
Also I have to agree with an above poster, once this is ironed out put Avast on the machine. It’ll block out the nasty’s, and doesn't eat RAM like some other big name AV software.
If the RAM tests ok it sounds like you are in need of the dreaded re-install. It happens to the best.
Do you wave a Win7 system repair disk? In most cases that can save you from having to start from scratch. (It never hurts to do a fresh OS install when these things happen if you have your data backed up)
 

nao1120

Distinguished
Mar 27, 2009
184
0
18,710
7
Nothing like trying something simple.... Sometimes dust and stuff can really get into the ram slots/slots causing some weird issue.

Remove the ram sticks - Blow out any dust as needed, and re-seat/place your ram sticks back in. Test.

Try one stick (4gb only) See what happens. If it happens again, Remove that stick and use the other stick. See if it repeats. If it does not, You know one stick is bad. (it can happen)
 

jediarron

Honorable
May 7, 2012
218
0
10,680
0
So I downloaded ISO Burner, and I still can't get it working.

But I will have some Prime95 Results up shortly :)

Wait hang on a second, Prime 95 doesn't end. How long should I leave Prime95 running for? o_O
 

Similar threads