Just upload the .dmp file here. It is quite hard to explain it

Hi Bro,

Million thanks to you. But I unable to upload the .dmp file in this forum. I uploaded it at http://www.megaupload.com/?d=DXG28WE9

Is this ok?

Thanks

i thought it should be in zip format?

U mean make this file to zip? but unable to attach into lyn forum too.

Usually, this cause caused by driver:

1) If you plug anything in usb, plug out and see if the problem solve.

2) Get latest updates for ur drivers

3) Get latest updates for ur windows

If the problem still happened:

4) run the diagnostic to ur hardware

5) maybe your processor overheating. Check the psu and maybe the cooler stuck .

Anyone could help me regarding my BSOD?

I suspect is cause by faulty RAM, but I'm noob at this kind of problem..

here's my minidump files.

http://www.mediafire.com/?09huvjt452px9ol

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

This post has been edited by JohnDiew0107: Dec 26 2010, 11:36 PM

Both BSOD caused by ntoskrnl.exe

1. Possible Keyboard issue. Try swapping out the keyboard and see if that fixes the problem. (9 times out of 10 it does not but it could be something as simple as a keyboard issue)

2. Could be a miscellaneous corruption. Boot into safe mode and boot to the last known configuration.

3. Could be a corrupted or missing ntoskrnl.exe file. That could be virus work usually. If you have the Windows CD you will need to boot from it. If not, if you have Recovery Console in a partition you can boot from that should be F11 to boot to recovery partition could be different on your computer.

-Once you boot from the disk or recovery partition select "R" for repair.
-You will be asked what Windows installation you want to log into (in most cases it will be 1. C:\Windows)
-If you have an Administrator password put it in or just hit enter
-This will bring you to the C:\Windows prompt.
-type in cd system32 then hit enter
-You should now see C:\Windows\System32
-Depending on what drive your Windows Recovery partition or CD is you will use that. For the sake of discussion we will use the "D" drive
-Type in: expand d:\i386\ntoskrnl.ex_ then hit enter
-You will be prompted if you want to overwrite this file click "Y"
-Reboot into Windows and see if this helps. Hopefully if you went through steps 1 and 2 with no avail, this will fix the corrupted ntoskrnl.exe file.

4. Faulty ram. If you suspect your ram is faulty, run memtest+86 first.

This post has been edited by badminto: Dec 27 2010, 01:33 AM

thanks for the explanation, gonna fix it soon.

before that here's the 3rd minidump, yea, once again.

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

your help is appreciated. =)

I got 8 Crash Minidump files, all are completely different from one another. Can I attach all 8 at once or am I gonna be warned for spamming?

That's it, I've been having one BSOD too many. I'm uploading all the BSOD's I've encountered since 2 weeks ago, and I hope all of them can be solved.

This post has been edited by RigerZ: Dec 29 2010, 10:50 PM


Attached File(s)
 Mini010106_02.zip ( 20.14k ) Number of downloads: 7
 Mini010106_04.zip ( 20.88k ) Number of downloads: 7
 Mini112310_01.zip ( 21.08k ) Number of downloads: 7
 Mini120910_01.zip ( 21.41k ) Number of downloads: 7
 Mini121910_01.zip ( 21.91k ) Number of downloads: 7
 Mini122910_01.zip ( 21.16k ) Number of downloads: 7
 Mini122910_02.zip ( 24.3k ) Number of downloads: 7
 Mini122910_03.zip ( 21.62k ) Number of downloads: 7
 Mini010106_03.zip ( 20.79k ) Number of downloads: 7

i hav blue screen continuously.. this is 1 of it.. the other are, non_page, memory_management.. need help.. can't fix it..

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1086

Additional information about the problem:
BCCode: a
BCP1: F886960F
BCP2: 00000002
BCP3: 00000000
BCP4: 828DD963
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\123010-14554-01.dmp
C:\Windows\Temp\WER-18080-0.sysdata.xml

This post has been edited by mao2: Dec 30 2010, 06:02 PM

Your bsod caused by avira and sis ethernet...(Network Card) and Netio.sys

My suggestions:
1) Try uninstall avira

2) Uninstall your Sis ethernet card and make sure your driver downloaded from manufacturer site. Update it.

3) Try to unplug ur sis ethernet card and reboot. Check the adapter if it is damaged or not.

4) Install latest updates from microsoft

5) Make sure all your driver is up to date.

Your feedback is appreciated

---

Added on December 30, 2010, 10:06 pmAttach your minidump

This post has been edited by badminto: Dec 30 2010, 10:06 PM

Hey could you take a look at my problem.. It is iqrl not less or equal type of BSOD.. Any reply would be appriciated



This post has been edited by Fallensya14: Dec 31 2010, 03:51 PM

Update your wireless adapter. If not fix, try update your chipset. If not fix, try unplug your wireless and reboot.

Your feedback is appreciated

Yeah I have updated these two driver up to date. How to check that this BSOD will not occur again? Is there some kind of ways to do it?

- Intel® 82577LC based Network Controller(OEM)
- Intel® WiFi Link 5300

How to check you ask? Just wait desperately for it to happen . Don't worry. Just enjoy with your pc

LOL Thanks for your help neway bro!

can someone help me with this BSOD problem? I've attached the minidump along.

So far what I did was change the RAM to a new one and formatted the system. The problem still persist. Help me...


Attached File(s)
 Minidump.zip ( 22.01k ) Number of downloads: 15

Your wireless card, PRISM 802.11 Wireless LAN (hopefully I'm correct) may cause this bsod.

Download latest driver for ur wireless card from manufacturer. If not fix, try unplug the wireless adapter and reboot.

Your feedback is appreciated

ok now it's getting wierder. I left my pc off last night. since this morning, i can boot into bios, but not into my drive or even cd-rom! could my mobo gone bad?

edit: both my drive and cd-rom are detected in the bios

This post has been edited by fruxano: Jan 1 2011, 01:02 PM

No more BSOD? I think you should create new thread about this in technical support coz people there may have many possible solutions

My opinion is you can try update your bios