Blue Screen Problems back

Status
Not open for further replies.
L

LightningSeed

Posts: 9   +0
Ok i recently had problems installing a new CPU see thread:
https://www.techspot.com/vb/topic101535.html

Now it loads and windows in "fine"but i get blue screened randomly with

IRQL NOT EQUAL OR LESS

0x0000000A

The computer also seems to freeze when my gf is using Internet Explorer for Myspace and youtube etc, help would be appreciated guys.
 
I spoke to gigabyte and the tech guy told me that F3 bios version would be ok.

I ran WinDBG and opened my last crash dump file and this is what came up,

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini032908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Mar 29 21:58:21.484 2008 (GMT+0)
System Uptime: 0 days 0:25:08.180
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {100008, 2, 0, 804e8178}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+11178 )

Followup: MachineOwner
---------

I cant seem to get the symbols from microsoft as when i download the pack it says the archive is corrupt

What can i do ?
 
The errors don't matter (just ignore them)

Here's the result:
BugCheck 1000000A
Probably caused by : ntoskrnl.exe
Click to expand...

I spoke to gigabyte and the tech guy told me that F3 bios version would be ok
Click to expand...
Ok is that the latest?

Also Memtest (7 Passes) doesn't always mean Ram is perfecly good.
This may still be a Ram fault
 
OK
Also please use attach (either in Notepad txt, or the Mindump itself)
This thread will get too big otherwise

Also how did you get the symbols right ? (I've always wanted to know that)
 
Yeh its the latest for my board, found this with the crash dump tool

See files lower

What memory is corrupt, ram, mobo, hdd ?
 
ok I'll look at that in a moment. You do the memtest thingo again !

And inside a new reply press this icon
attach.gif
(next to the white smily face)
 
Right now i have taken out all my old RAM and put 2 new ones i got today. Will see what happens on that front. Just dont see what would of been wrong with old ones when they worked fine before. Guess i will wait and see if that cures the problem, what else could it be ?

Also if it is the old ram could that of been the reason for the computer freezing up while on websites that load alot like myspace and youtube even though games like Dawn of War Soul Storm ran fine?

Just hoping its that simple, though it never is
 
I ran memtest on my old ram for about 7 times and nothing came up errored.

Kim press Ctrl+S and put the path there, also make sure you create the file first lol, like i did maybe put it in the WinDBG program file itself. just replace my file location with yours, click ok and it should work, well thats how mine did.

Could it be related to the problem i had before getting the CPU to work.

Im leaving Windows Repair last incase it was ram or is something else fixable rather than having to download all the updates agen.

Could it also be a driver? My graphics card driver is fine as i just updated it and the problem was still there before and has happened since that update. Could there be a problem with another driver somewhere?

This problem has really got me.
 
Thanks

I suggested to a member once to download ALL their drivers (into one folder)
And then go to Device Manager and remove the entire PCI bus !
This was met with another support member, saying it was too extreme. But at least you will be positive that you have all your drivers installed correctly :)

By the way, I'd do it in Safe mode, and also check (view-show hidden devices) in Device Manager

Try that (unless another support member says no !) Maybe be quick !
 
kimsland said:
Thanks

I suggested to a member once to download ALL their drivers (into one folder)
And then go to Device Manager and remove the entire PCI bus !
This was met with another support member, saying it was too extreme. But at least you will be positive that you have all your drivers installed correctly :)

By the way, I'd do it in Safe mode, and also check (view-show hidden devices) in Device Manager

Try that (unless another support member says no !) Maybe be quick !
Click to expand...

I dont think ill try that yet, i will post all my WinDBG files first.

Did you get WinDBG to work with symbol thing?
 
Ive just opened more information from the latest dump file in WinDBG and came up with this[/ATTACH]

could the problem just be as simple as my F-Secure internet security ?

also looking under windows task manager the fssm32.exe is running at CPU 48 and Mem Usage from 52,000k to 82,000k could this be the reason for my pc freezing when internet explorer is on high usage sites such as myspace and youtube? and could this factor into why my computer blue screens ?

Only from time to time does it do this like now it is at CPU 00 and Mem Usage 52,000k
 
Still seems like a memory issue
Even though Memtest recorded no fault, I would suggest either remounting them, or taking one out to test again (if you have two cards)

Also instead of all the replies to yourself, please use Edit instead. That way I don't receive multiple emails from you.
 
I doubt it as it happened before i put brand new RAM in and is still happening after. I changed RAM yesturday.

Would it be worth just doing a Windows Repair anyway just to see if that fixes the problem ?
 
Even a clean install ! (ie remove the partition)
I suppose you got the network thingo fixed (as it's now removed)

Also I must logoff for a while
 
Status
Not open for further replies.

Similar threads

T
Windows 10 screen goes black for a second before returning to normal
Replies
13
Views
3K
Kshipper
Kshipper
N
Windows 11 review round-up: Better than Windows 10, but still a work in progress
2
Replies
30
Views
6K
loki1944
L
ToshiCG
Blue screens and random restarts
Replies
3
Views
2K
Cycloid Torus
Cycloid Torus

Latest posts

Back