Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue screen of death for windows 7


  • Please log in to reply

#31
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Explanation of error:

Error Message:

STOP: 0x0000003B (parameter, parameter, parameter, parameter) SYSTEM_SERVICE_EXCEPTION
Explanation:

This is a Windows 2000 Executive character-mode STOP message. It indicates an exception was raised in a system service which was not handled by the system service.
User Action:

If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.


  • 0

Advertisements


#32
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The one thing I see that is the same in all the errors is a faulty driver or hardware compatibility.
Did you recently update a driver or change some hardware in the system?
Updating via the manufacturers website or via a Microsoft update?
  • 0

#33
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
Your other way is not working for me. It keeps saying that C:\VEW.txt doesn't exist. and when I did create a VEW.txt in the C folder, it comes out empty after I press run.
  • 0

#34
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts

The one thing I see that is the same in all the errors is a faulty driver or hardware compatibility.
Did you recently update a driver or change some hardware in the system?
Updating via the manufacturers website or via a Microsoft update?


Well the only thing I can think of is my portable CD/DVD drive. The error usually comes after I've burned something or used the drive in any way. After I unplug it and restart my computer the next day, the crash happens. I haven't updated a driver or anything. I haven't updated using Microsoft Update either.

Edited by moofasa, 25 December 2010 - 10:51 AM.

  • 0

#35
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
It's a Portable Super Multi Drive by LG GP08. I just bought it in september with the laptop, so I don't see why it wouldn't be compatible with windows 7.
  • 0

#36
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Did you ever run the memtest86 on your memory?
I don't see any results form that yet. :D
  • 0

#37
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
Sorry, I'll run memtest now. I wanted to post my log from BlueScreenView just so you can see what it is. I'll post the results from the mem test soon.

==================================================
Dump File : 122810-67704-01.dmp
Crash Time : 28/12/2010 9:43:27 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffffa80`03e705f6
Parameter 3 : fffff880`0726da68
Parameter 4 : fffff880`0726d2c0
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\122810-67704-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
Dump File Size : 274,728
==================================================

==================================================
Dump File : 122710-60216-01.dmp
Crash Time : 27/12/2010 10:56:45 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffff8a0`0b3c7b20
Parameter 3 : fffff8a0`0b3c7b60
Parameter 4 : 00000000`05040405
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+37c10
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\122710-60216-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
Dump File Size : 274,672
==================================================

==================================================
Dump File : 122510-63414-01.dmp
Crash Time : 25/12/2010 11:27:54 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`030c34d8
Parameter 3 : fffff880`077b09a0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\122510-63414-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
Dump File Size : 274,672
==================================================
  • 0

#38
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Error messages in order from above.

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.



0x00000019: BAD_POOL_HEADER
(Click to consult the online MSDN article.)
A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues, but I haven’t been able to confirm this as a cause.)



Error Message:

STOP: 0x0000003B (parameter, parameter, parameter, parameter) SYSTEM_SERVICE_EXCEPTION
Explanation:

This is a Windows 2000 Executive character-mode STOP message. It indicates an exception was raised in a system service which was not handled by the system service.
User Action:

If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.


  • 0

#39
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK this is time for drastic steps.

Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything and restart.
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
  • 0

#40
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
alright, I'll do that and let you know. I wanted you to know that I ran memtest and there were no errors in the memory. So the RAM is good I guess.
  • 0

Advertisements


#41
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
I can't do what you've asked of me. I don't want to uncheck something and then my computer doesn't run. I don't know enough to use msconfig :D

Also the error isn't something that comes everytime I turn on the laptop right away. It comes at different times, and not just when I restart. So if I uncheck something, and the problem doesn't come, it doesn't mean that it won't come within the next 30 minutes. You get what I mean?
  • 0

#42
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK your memory test took less then 2 hours to do more then 6 passes.
Something is not right here. :D

So far we have done:
  • SFC Windows Resource Protection did not find any integrity violations.
  • HD Diagnostics Short Test PASSED....Long Test PASSED
  • Chkdsk ran and said Volume is clean"
  • Memtest86 ran with no results
  • Msconfig startup suggested and you don't want to do that
  • Msconfig services next step


Lets see what you have in your startup services area

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
  • 0

#43
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
Oh sorry, I didn't do 6 passes. I was in the middle of my third pass when I had to use my computer for something so I had to quit the memtest program.

So I went to msconfig -> Services -> Hide All Microsoft Services -> Uncheck everything that is there -> Restart. And as it restarted, the error came. So everything other than microsoft services was unchecked, and the error still came. What do you think?

Also the errors that showed up were:

==================================================
Dump File : 122910-53913-01.dmp
Crash Time : 29/12/2010 6:58:30 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000040
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`030d94d8
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\122910-53913-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
Dump File Size : 274,672
==================================================

==================================================
Dump File : 122910-66050-01.dmp
Crash Time : 29/12/2010 6:52:02 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`03068591
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\windows\Minidump\122910-66050-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
Dump File Size : 274,672
==================================================

Edited by moofasa, 29 December 2010 - 06:11 PM.

  • 0

#44
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK after going through all the error messages you have had the one thing in common is a faulty driver.
This is either a OS driver or something that has been updated prior to the issue starting.
Is the error coming up before windows starts or after windows loads?
  • 0

#45
moofasa

moofasa

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
It's definitely after windows loads. The desktop appears and most of the icons become visible. I can even open some programs. Then it comes :D

I also just ran Toshiba Diagnostics Tool that came with the laptop, and everything passed :S

Edited by moofasa, 29 December 2010 - 06:43 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP