locked
BSOD event 1001, bug check RRS feed

  • Question

  • <can someone help me what is the cause of it? it just happened a while ago and i got feared it will damage my pc..

    n

    - System
    - Provider
    [ Name] Microsoft-Windows-WER-SystemErrorReporting
    [ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
    [ EventSourceName] BugCheck
    - EventID 1001
    [ Qualifiers] 16384
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2014-04-20T23:40:42.000000000Z
    EventRecordID 10197
    Correlation
    - Execution
    [ ProcessID] 0
    [ ThreadID] 0
    Channel System
    Computer rustyevangelista
    Security
    - EventData
    param1 0x0000007e (0xffffffffc0000005, 0x0000000000000000, 0xfffff880031fbb08, 0xfffff880031fb370)
    param2 C:\Windows\MEMORY.DMP
    param3 042114-53539-01

    Monday, April 21, 2014 5:14 AM

Answers

  • Hi,

    0x0000007E bug check indicates that a system thread generated an exception that the error handler did not catch.

    Check your below settings:

    •Make sure you have enough disk space.

    •If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

    •Try changing video adapters.

    •Check with your hardware vendor for any BIOS updates.

    •Disable BIOS memory options such as caching or shadowing.

    For more detailed information, please read this article:

    Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff559239(v=vs.85).aspx

    If this issue can't be resolved, please follow Patrick's suggestion to collect minidump file, upload to OneDrive, and then post the shared link in next reply.


    Karen Hu
    TechNet Community Support

    • Marked as answer by Michael_LS Monday, May 5, 2014 7:05 AM
    Tuesday, April 22, 2014 7:02 AM

All replies

  • Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Monday, April 21, 2014 5:15 AM
  • i see my minidump folder but no files.. and im still using kernel dump. id just switch to it when after i read your rply.. so where will i see the kernel dump folder?

    now i see the memory.dmp but its unreadable... i cant even open it... how can i open it just to upload it in here

    • Edited by ronz18 Monday, April 21, 2014 5:54 AM
    Monday, April 21, 2014 5:23 AM
  • You don't want to open it.

    Zip up the MEMORY.DMP and upload it to Onedrive, Mediafire, etc... whatever works for you, and then paste the link here.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Monday, April 21, 2014 6:09 AM
  • For this type of error follow this article

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff559239(v=vs.85).aspx

    HTH

    Milos

    PS: It is useful to mention what happened before this error appeared.

    Monday, April 21, 2014 6:24 AM
  • i just restart my laptop before installing my realtek driver it actually boot up.. then i see installing driver software my realtek wlan driver then suddenly crashed... that goes the BSOD.. then it restart my pc.
    Monday, April 21, 2014 7:12 AM
  • As I said, we'll need to see a crash dump to make any recommendations.

    Regards,

    Patrick


    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Monday, April 21, 2014 4:49 PM
  • Hi,

    0x0000007E bug check indicates that a system thread generated an exception that the error handler did not catch.

    Check your below settings:

    •Make sure you have enough disk space.

    •If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

    •Try changing video adapters.

    •Check with your hardware vendor for any BIOS updates.

    •Disable BIOS memory options such as caching or shadowing.

    For more detailed information, please read this article:

    Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff559239(v=vs.85).aspx

    If this issue can't be resolved, please follow Patrick's suggestion to collect minidump file, upload to OneDrive, and then post the shared link in next reply.


    Karen Hu
    TechNet Community Support

    • Marked as answer by Michael_LS Monday, May 5, 2014 7:05 AM
    Tuesday, April 22, 2014 7:02 AM